docs(docs): R5.6 rehearsal gates, export alias gap stated, audits

This commit is contained in:
bchanot committed 2026-10-25 01:13:14 +02:00
1 parent 6ade9176d9
commit 65fa30893d
4 files changed
+176 -4

No files matched your search

+20 -3
View File
@@ -3539,9 +3539,11 @@ scratchpad; the branch's own state stays inactive (seed `27c7…`, nothing activ
the registered historical value of the same sheet, exported against the canonical value, archives a
snapshot carrying the report's own stamp; a new report keeps the canonical value. The equivalence is one
way (`equivalence(sheet, stamped, current)`: an old stamp against the canonical value, never the
reverse) and needs the loaded sheet's `fingerprint_verified` (set only when a `v1` block was checked
against the registry and its value recomputed from the document at load, `loaded.rs`
`check_reference`; hashing is no longer feature-gated, the wasm module carries `sha2`). `archive/read.rs`
reverse). The rebase and `report-compare` also need the loaded sheet's `fingerprint_verified` (set only
when a `v1` block was checked against the registry and its value recomputed from the document at load,
`loaded.rs` `check_reference`; hashing is no longer feature-gated, the wasm module carries `sha2`). The
export does NOT: `input.rs` sees only the snapshot, so it grants the pair on the snapshot's claimed value
(gate finding below). `archive/read.rs`
stays strictly equal: the M1 envelope holds one value, so no archive check is loosened.
**v0 and v1.** No block: a historical reference, loaded as before, unverified, no alias privilege, never
@@ -3573,3 +3575,18 @@ generator (`import:equine:legacy`) still writes the pre-switch files (`seed.gold
Not done: the patch is not applied to the branch; `pnpm format` must never run over `.claude/` (it
rewrote the append-only audits in the worktree, reverted there).
Gates on the rehearsal (patch at 82e2e43): security PASS, 1 MEDIUM, 6 LOW
(`.claude/audits/2026-10-25-rust-r5-6-rehearsal-security.md`); fresh verifier ECARTS(3)
(`.claude/audits/2026-10-25-rust-r5-6-rehearsal-verify.md`), one root cause: the export path has no loaded
sheet, so `assert_exportable` and `keep_the_report_stamp` grant the registered pair on the snapshot's
claimed value. Probe: a v0 sheet (no block, unverified) with the canonical value, the old demo report and the
core's own `build_sheet_snapshot` export with `27c7/27c7` where the pre-patch code answered `sheet_mismatch`.
The application cannot reach it (every stored report is rebased first, and the rebase checks the flag), the
core's export API can. The fix needs the snapshot builder, outside the approved files: decide the stamp in
`domain/archive/snapshot_rules.rs` `build_sheet_snapshot` (it holds the loaded sheet and its flag; called by
`ops.rs` `archive.snapshot`) and put `assert_exportable` back to strict equality, so the export never grants
an alias. Not applied: awaiting the owner. LOW kept: `"fingerprint": null` and a misspelt block read as v0
(no privilege), public mutable `reference`/`fingerprint_verified` fields, a draft-allowed validation warning
would make a `v1` bundle unloadable, `canonical_json` recursion unbounded (trusted input today), stale
comments on `pnpm import:equine` in `scripts/import-equine.sh` and CLAUDE.md.