Repository navigation
docs(vclt-gate): freeze the VCL-total ↔ VeriSimDB admissibility gate contract - #58
Merged
Merged
Conversation
…e contract The single shared artifact that lets the vcl-ut and verisimdb workstreams proceed in separate threads against a fixed seam. Specifies the vclt-gate boundary: a pure CLI subprocess (JSON request -> JSON verdict) wrapping vcltotal-parse's lexer/parser + decider::certified_level. - Transport rationale (subprocess over FFI/lib/network: decouples the two toolchains with no shared build). - Request/response schemas (schema_version 1), grounded in the real primitives: SafetyLevel tags 0-10 (ast.rs) and certified_level (decider.rs). - Authoritative level table (all 10 predicates are statically decidable today; the echidna proof tier is a SEPARATE downstream check, not a blocker on this gate). - Exit-code verdict (0 admit / 1 reject / 2 gate-error) + purity guarantee. - Consumer integration: VERISIM_VCLT_GATE env gate, pre-mutation invocation point, fail-closed default with an advisory override. - Per-side build checklists + two worked fixtures (admit, injection-reject). Enables Week-3 item 'vclt-gate' to be split cleanly: producer half here, consumer half in verisimdb, meeting only at this wire shape. https://claude.ai/code/session_01E8BpV19yxhf67UrCrvkfTr
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Freezes the vclt-gate contract — the single shared artifact that lets the vcl-ut and verisimdb workstreams proceed in separate threads against a fixed seam, with no further coordination.
docs/vclt-gate-contract.adocspecifies the VCL-total ↔ VeriSimDB admissibility gate: a pure CLI subprocess (JSON request → JSON verdict) wrappingvcltotal-parse's lexer/parser +decider::certified_level.Grounded in the real primitives I read in this repo, not invented:
SafetyLeveltags 0–10 (ast.rs) andcertified_level(stmt, schema) -> i64(decider.rs) — the authoritative level vocabulary and verdict function.PROOFclauses — a separate downstream check, not a blocker on this gate. So the gate is far stronger than "L1–L4 static tier."The spec covers: transport rationale (subprocess decouples the two toolchains with no shared build), request/response schemas (
schema_version: 1), the authoritative level table, exit-code verdict (0 admit / 1 reject / 2 gate-error), a purity guarantee (safe to call on the write path), the consumer-side integration (VERISIM_VCLT_GATEenv gate, pre-mutation invocation point, fail-closed default with an advisory override), versioning, two worked fixtures (an admit and an injection-reject), and a per-side build checklist.With this frozen, Week-3's
vclt-gatesplits cleanly: the producer half (the binary) builds here, the consumer half (execute-path invocation) builds in verisimdb, and they meet only at this wire shape.https://claude.ai/code/session_01E8BpV19yxhf67UrCrvkfTr
Generated by Claude Code