erik/acdream
1
0
Fork 0
Code Issues Pull requests Projects Releases 6 Packages Wiki Activity Actions

docs(overhaul): correct S4 c3b gate provenance

Browse source 
Disclose that both official c3b artifact sets were captured pre-commit on the restored uncommitted implementation tree at parent a0523e605 with WorktreeDirty=true. Reconcile the transcript status entry as transient mutation-worktree dirtiness rather than an active gate mutation.

Narrow verification: both summary identities match; both 30-entry SHA256SUMS manifests verify with zero mismatches; base, implementation tip, contract HEAD, and worktree transcript blobs are c755c1379f; the hermetic TRX source-truth pin passed; diff-check and packet-only scope passed.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
This commit is contained in:
Erik 2026-09-04 15:14:48 +02:00
parent 5110bf6760
commit 3f2f00c9fa
1 changed files with 21 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

21
docs/research/2026-09-01-overhaul/s4-depth-alpha-packet.md
View file

@ -2048,6 +2048,27 @@ Automated return:
No new failure appeared; evidence
`artifacts/s4-c3b-installed-inclusive-20260904`.
Artifact provenance: both official artifact sets above ran before the
implementation commit, on the restored but still uncommitted c3b tree whose
HEAD was parent `a0523e6057af206126a09874bf8664206ff7d9a1`. Accordingly,
both embedded summaries truthfully record that parent and
`WorktreeDirty=true`, rather than implementation tip `4eca2a4f`. The two
`SHA256SUMS.txt` manifests each verify all 30 entries with zero missing or
mismatched files.
Both artifact environments list
`WalkTraceConformanceTests.AlphaDepthTranscript.cs` as dirty. That entry was
transient mutation-worktree dirtiness left by applying and restoring mutation
5, not an active prose mutation during either official gate: the hermetic TRX
records
`AlphaFlushCountKnownFailure_StatesOnlyTheThreeExactReasons` as `Passed`, and
the transcript has the identical Git blob
`c755c1379feeba5fe5382fa0b0db243e7169b4e9` at parent `a0523e605`,
implementation tip `4eca2a4f`, current contract HEAD, and the current
worktree. The final implementation diff therefore correctly excludes that
file while the pre-commit artifacts continue to describe their actual capture
state.
Mutation ledger (each mutation was applied alone and restored by patch before
the next; the restored pin set passed 4/4):