Pre-Alpha, but substantially further along than this file previously claimed. Everything below was measured on 2026-07-21 rather than asserted.
|
Note
|
The previous version of this file said "Parser work not yet started" and
planned an Idris2 parser. Both statements were false. A parser exists, is
written in Rust, and has 36 green tests; it is gated in CI by
|
What exists, measured:
| Component | State |
|---|---|
Idris2 proof corpus ( |
~12.4k LOC, |
Rust parser ( |
Lexer, parser, wire codec, decider, |
Root workspace |
Re-export facade over |
|
9 + 3 tests green. Both had silently stopped compiling before 2026-07-21
and are now gated by |
|
Producer side implemented; Contract v1 frozen (docs/vclt-gate-contract.adoc). Not yet wired on the VeriSimDB consumer side — see "Nearest Work" below. |
Test total |
150 across all workspace roots. |
The single most important qualification: eleven levels are specified and
proved; six are expressible. parse_statement fixes proof_clause,
effect_decl, version_const, linear_annot and epistemic_clause at
None, and infer_requested_level awards L7-L10 on exactly those fields, so
the highest level reachable from VCL source text is L6 CardinalitySafe.
The gap is fail-closed and disclosed (unsupported clauses are rejected with an
explicit message, never silently ignored) — but it is the gap that matters
most.
These are ordered by value, not by version number.
-
Surface syntax for L7-L10. Close the gap above. Without it the upper ladder — including the entire consonance level — is reachable only by constructing a
Statementprogrammatically or decoding one off the wire. Tracked in #25. -
Wire
vclt-gateinto VeriSimDB. Contract v1 is frozen and the producer works; the consumer (rust-core/verisim-api/src/vcl.rs) does not invoke it. Until it does, VCL-UT proves things about statements VeriSimDB never asks about. -
Discharge the two disclosed L10 residuals. Transitive
ENTAILS-cycle detection and proposition well-typedness, both recorded as owed inverification/proofs/VERIFICATION-STANCE.adoc. -
Retire the
HEXADkeyword once VeriSimDB’s default modality context carries all eight witnesses. The parser accepts bothOCTADandHEXADtoday for compatibility.
-
✓ VCL-UT grammar specification (
src/core/Grammar.idr) -
✓ Total parser with panic-freedom gated in CI (Rust, not Idris2 as originally planned — the Idris corpus proves, the Rust port re-establishes independently)
-
✓ Schema representation as dependent types (
src/core/Schema.idr,OctadSchema) -
✓ Type-compatible operation checker
-
❏ Zig FFI for transition-plan emission
-
✓ Test suite (150 tests)
-
✓ Null-tracking through join algebra
-
✓ Injection-proof parameterisation (type-level enforcement)
-
✓ Result-type inference with compile-time guarantees
-
✓ Property-based tests (
tests/property_test.rs,tests/fuzz_test.rs)
-
✓ Cardinality annotations and inference (reachable:
LIMIT⇒ L6) -
❏ Effect system (Read/Write/DDL) — proved; no surface syntax
-
❏ Temporal type annotations — proved; no surface syntax
-
❏ Linear types via Idris2 QTT — proved; no surface syntax
-
❏ Integrate TypeQL-Experimental mechanisms
-
✓
L10_EpistemicSafecertificate and shared decider -
✓ S2 transitions MERGE / SPLIT / NORMALISE, with NORMALISE fail-closed without an explicit justification
-
❏ Surface syntax for epistemic clauses
-
❏ Transitive
ENTAILS-cycle detection -
❏ Proposition well-typedness against the schema
-
❏ All 6 VCL-DT PROOF types expressible in VCL-UT
-
❏ Migration guide from VCL-DT to VCL-UT
-
❏ Benchmark: VCL-UT overhead vs VCL-DT overhead
-
TypeLL type theory must stabilise for L6-L9. Note that L10 does not depend on TypeLL:
EpistemicSafeoriginates here, in the shift from querying a store to addressing a consonance engine. -
VeriSimDB statement router must support VCL-UT as a third path alongside Slipstream (VCL) and VCL-DT.
-
ReScript evangeliser must prove concept first — VCL-UT and AffineScript are the two showcase languages that follow.
Once v1.0.0 ships:
-
Federation support (VCL-UT statements across federated VeriSimDB instances)
-
VCL-UT LSP language server for IDE integration
-
Formal security audit of the injection-proof guarantee (L4)
-
Academic publication — reframed around consonance languages as a class rather than a decalogue of query safety. The eleventh level is the reason:
EpistemicSafeis not a query-safety property, and a paper titled after ten of them cannot house it.