CURRENT IMPLEMENTATION · REVIEWED 2026-09-27
Encode its structure. Run its program. Change its representation. Observe what it writes, then test what changes when you intervene. Each capability carries its own boundary.
These facts come from the LARQL checkout linked below. The published CLI and the candidate format keep their own versions; neither promises every capability in this checkout.
01
Admit local checkpoints or Hugging Face sources, build the system graph, encode and inspect a container. Admission and operand closure determine support.
Scope. A recognized model family is not a guarantee that every checkpoint is admissible.
Read the implementation contract →02
Execute the canonical component program on CPU or scoped Metal backends, maintain sessions and serve HTTP. CPU dense FFN workers and stateless softmax-prefix layer workers are implemented.
Scope. Remote KV, grid placement and remote Metal/KDA/MLA workers remain outside that scope. Multimodal embedding handoff is still refused.
Read the implementation contract →03
Compile NVFP4, K-quants or plugin encodings with role policies and protected projections. Keep canonical bytes in an archival container or emit a derived deployment image. Measure a candidate against a reference over a sealed token bank.
Scope. A smaller pack is not behavioral approval. Receipts establish measurement admissibility; a separate declared decision governs acceptance.
Read the implementation contract →04
Record carrier writes from the canonical decode traversal with provenance and receipts. Optional logit lenses and per-head capture expose declared views. The Observatory validates and replays recordings.
Scope. Replaying a recording does not execute a model. A projection or additive head decomposition is descriptive evidence, not a causal result.
Read the implementation contract →05
Use observe --intervene for declared carrier changes and in-kernel head counterfactuals. Record the manipulation, vector provenance and intervention firings alongside the run.
Scope. Head intervention currently covers CPU softmax decode. MLA, conv-QKV, batch prefill and Metal head intervention remain outside it. There is no separate intervene command.
Read the implementation contract →06
Unix plugins can register codecs, encoders, lowering providers and continuation providers. LQL retains extraction, query, patch and compilation surfaces across the supported generations.
Scope. Plugins must be explicitly named and match the host compiler and larql-vindex commit. Generation selection remains deliberate; automatic extraction still chooses VINDEX2.
Read the implementation contract →The accepted decision makes the graph container the only normative top-level shape at 3.0 Final. LYRW v2 remains an import/interchange codec outside that normative contract. The decision's full execution is still pending.
Logical objects, representations and tensor-table segments. Routed models can use this shape without any .lyrw files.
Recognize the legacy bank shape, then open it or refuse it by name with a migration path. It is not a conforming VINDEX3 3.0 model.
The inventory found no surviving bank artifact in the searched scope. A graph conformance fixture and specification changes remain closure criteria. Bank-layout evidence does not automatically certify the graph shape.
Named legacy recognition, the single production bank producer and the scoped artifact inventory are complete. The ADR still marks overall execution pending; the site does not promote it to a passed gate.
describe · diff · encode · export · inspect · layers · plan · precision · represent · representations · update · verify
auto-rep · consequence · encode · exec · inspect · measure · observe · ops · plan · references · represent · sensitivity · token-bank · verify
Use each command’s --help for its supported arguments. These are source-checkout commands, not a transcript of the released binary.
larql vindex3 auto-rep init produces a characterization-only plan record. auto-rep run connects the search loop to the measurement arms, but refuses a record without an armed gate before compiling anything. MEASURE-PLAN-3 freezes the first Granite campaign; the protocol is not a reported result.
Implementation record → · Frozen campaign →
larql run --continuation window/v1 selects the bounded KV provider. It retains rows required by the plan’s declared attention horizon and drops expired rows. It supports KV regions only; recurrent and latent-KV plans are refused. Existing defaults remain unchanged.
The August and September measurements retain their original dates and scope. The current implementation adds capabilities; it does not retroactively strengthen an older experiment.