Evidence map clause
2.5 Approval, protection and refs
This clause and its evidence summary follow the authored EVIDENCE-MAP.md section.
Evidence map clause · EVIDENCE-MAP.md
Map clause: Approval, journal, cache, and status state.
Source heading anchors: spec/02-formats.md#25-approval-protection-and-refs; spec/02-formats.md#251-approval-commit-on-refskogenintents-origin; spec/02-formats.md#252-protected-manifest; spec/02-formats.md#253-refs-origin; spec/02-formats.md#254-landing-commit; spec/02-formats.md#26-strict-yaml-subset; spec/02-formats.md#27-kogen; spec/02-formats.md#28-run-dir-and-journal; spec/02-formats.md#29-setup-cache; spec/02-formats.md#210-build-report-status---json; spec/02-formats.md#211-status-derivation
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 approvals, hashes, journal transitions, and state reporting; normative product for the chosen formats and workflow.
Evidence and status: NO EMPIRICAL EVIDENCE for comparative Build benefit. The
intent-lifecycle,merging-v2, andisolationentries in `research/README.md` are study-index records. Existing state and approval conformance cases are parity checks, not outcome studies. Related hypotheses: H16, H17, H65, H145.Unresolved measurement: Fault-injection and recovery tests for state integrity, plus a separate comparative test only where the product claims a success, reliability, or throughput benefit.