Evidence map clause
C.1 Definition
This clause and its evidence summary follow the authored EVIDENCE-MAP.md section.
Evidence map clause · EVIDENCE-MAP.md
Map clause: Conformance cases and Quint classification.
Source heading anchors: spec/CONFORMANCE.md#c1-definition; spec/CONFORMANCE.md#c2-freeze-rule; spec/CONFORMANCE.md#c3-harness; spec/CONFORMANCE.md#case-file; spec/CONFORMANCE.md#c4-profiles; spec/CONFORMANCE.md#c5-cases; spec/CONFORMANCE.md#cli-1; spec/CONFORMANCE.md#state-2; spec/CONFORMANCE.md#approval-172-25-33; spec/CONFORMANCE.md#shape-32; spec/CONFORMANCE.md#build-34311; spec/CONFORMANCE.md#ladder-31-38; spec/CONFORMANCE.md#provider-4; spec/CONFORMANCE.md#custody-55; spec/CONFORMANCE.md#format-data-files; spec/CONFORMANCE.md#exunit-243; spec/CONFORMANCE.md#c6-comparing-implementations; spec/CONFORMANCE.md#appendix-a-the-kt-fixture; spec/CONFORMANCE-v1.2-CASES.md#p1-conversation-key-is-present-and-stable; spec/CONFORMANCE-v1.2-CASES.md#p2-thread-identity-changes-with-the-rung-build-cache-affinity-does-not; spec/CONFORMANCE-v1.2-CASES.md#p3-prompt-prefix-is-byte-identical-from-turn-2; spec/CONFORMANCE-v1.2-CASES.md#p4-completion-is-finish-not-text; spec/CONFORMANCE-v1.2-CASES.md#p5-tool-result-budget; spec/CONFORMANCE-v1.2-CASES.md#p6-responses-and-lite-shapes; spec/CONFORMANCE-v1.2-CASES.md#p7-upstream-cut-continues-the-turn; spec/CONFORMANCE-v1.2-CASES.md#p8-deadlines-and-retries; spec/CONFORMANCE-v1.2-CASES.md#p9-usage; spec/CONFORMANCE-v1.2-CASES.md#p10-grok-wire; spec/CONFORMANCE-v1.2-CASES.md#p11-scheduling-and-status; spec/CONFORMANCE-v1.2-CASES.md#p12-rails-detection; spec/CONFORMANCE-v1.2-CASES.md#p13-checkpoint-epoch; spec/quint/CLASSIFICATION.md#prose-sections; spec/quint/CLASSIFICATION.md#quint-slices; spec/quint/CLASSIFICATION.md#deferred-work-and-promotion-evidence
Spec revision / decision reference: v1.2 (pinned fragment locally verified); section-level D references are listed in the source classification. Last reviewed: 2026-10-07.
Type: Safety/correctness for implementation parity; implementation freedom for the placement of untested or optional behavior.
Evidence and status:
executable-specs,kogen-core-spec, and Quint entries are listed in `research/README.md`; the census is an index, not a verification receipt. R70, R70 rerun, and R70 extension concern language implementation cohorts and are not conformance evidence. No public record establishes semantic equivalence of the Quint translation or a task-success benefit from conformance. Related hypotheses: H91–H99.Unresolved measurement: Publish the exact frozen suite revision and cases, verify spec-to-implementation semantics and the Quint translation, and keep parity results separate from any live agent-success comparison.