THE VERSION · 3.0 CANDIDATE · GRAPH SCHEMA 6 · 2026-08-30
VINDEX3 3.0
One page, one answer: what 3.0 claims, what already holds each claim up, and exactly what remains before Candidate becomes Final. When the named gates pass, this page flips — same URL, same six claims.
What is VINDEX3 3.0, and what is its current status?
VINDEX3 3.0 is a Candidate Specification for a self-describing, executable, queryable model container, promoted from draft on 2026-08-30 and carrying graph schema 6. The container model is settled: one canonical graph shape, a contract stack, compatibility rules, and a per-layer operator program that surfaces and state follow. Schema 6 has now executed both a pure SSM and a mixed Mamba2 / conv-QKV-attention model through the generic runtime with no family lookup and no further schema change — the hybrid matches its fp32 oracle across 468 positions and reproduces source-hidden LQL generation token-for-token. Lift 2 closed on 2026-08-31 inside the same schema: a 48-billion-parameter hybrid was re-encoded to carry the state facts it had been missing, and all five of its representation payload hashes came back byte-identical — meaning corrected without touching a single stored representation. Candidate means the model is settled, not that the bytes are frozen — the gates that remain before Final are named below, each with its status.
derived from the Record — /ladder
The destination sentence, and the bar this page answers to: the model is the authority.
THE SIX CLAIMS — EACH HELD BY EVIDENCE, OR HONESTLY NOT YET
Statuses move with the Record, not with this page's copy. Two claims say BUILDING because they are building — that is what makes the other four worth believing.
SELF-DESCRIBING (passed) → PROGRAMMABLE (passed) → STATE-COMPLETE (passed) → REPRESENTATION-INDEPENDENT (passed) → FAIL-CLOSED (passed) → VERIFIABLE (building) — each rung closed only by its own gate, in order.
WHAT REMAINS BEFORE FINAL
The ontology lift is closed on both halves — schema 6 on 2026-08-30, the typed continuation-state schema on 2026-08-31, the second additive within the first. Six named gates remain, none of them drift: the shape convergence executed; the required/optional RFC-2119 freeze; the independent reader (vindex-core) with a conformance harness; the held-out architecture test (E8), run after the freeze under a rule of zero format changes; the default flip (M4); and the remaining pre-registered bank-ABI rows. What remains is standards, conformance and release closure rather than architecture. Each gate's current status lives on the Record.
WHAT IS NOT A 3.0 GATE — KIMI REAL-SCALE EXECUTION
Execution semantics close for Kimi-Linear-48B: every operand accounted, every continuation region declared, the plan built from the container alone. CPU reference execution of that model is nonetheless constrained by residency, not by meaning — the backend expands the 94 GB BF16 routed-expert bank to F32, which would need roughly 188 GB resident on a 137 GB machine. Device and streaming execution are the appropriate path. This is an execution-placement axis, and it is deliberately not counted against STATE-COMPLETE: model meaning, physical representation and residency are three separate things, and this is the third one refusing.
PUBLISHED 30 AUG 2026 · REVISED 31 AUG 2026 · VERSION 3.0 Candidate
CITEsite build 43a1b6b · built 2026-09-02 · graph schema 6 · specification vindex3-format-spec.md · reference implementation github.com/chrishayuk/larql
CITE THE SPECIFICATION
Specification · 3.0 Candidate
Hay, C. (2026). VINDEX3 Specification (Version 3.0 Candidate). VINDEX3. https://vindex3.org/3.0
Cite the version, not the website: this URL is durable, and 3.1 will be a different object rather than a silent edit of this one. No DOI appears above because none has been registered — a reference carrying an author, a date, a version and a canonical URL is complete without one.