Registration 2: the anchor context report (forecast ledger entry 10)

[MaxGhenis]

Identical to registration 1 (#317) in every term — class, output, frozen configuration (master 9f3ac695 implementation; anchors adc782a1…; estimates 719604ca…; the nine specs; the fixture-only law; the §5.3 fail-closed resolution) — except the reference. Lineage: #317 was consumed by incident 1, a pre-import guard refusal on a launcher that did not mirror the registered sealed invocation; no input was opened, no value computed. The checklist now verifies the launcher invocation against the registered invocation byte for byte (item 7).

[MaxGhenis]

Incident 2 — preparation_implementation_commit_drift; this registration is consumed, and the diagnosis is an implementation defect in the ceremony law. The coordinator requires HEAD == implementation_commit exactly (anchor_context_coordinator.py:2635-2638) plus an entirely clean tree plus the registered document readable in that tree. Those three conditions are jointly unsatisfiable: the document embeds the implementation commit's sha, and no commit can contain its own hash — so the document can never be committed at the commit it names. The fixture-only rehearsal faked git identity, which is why five review rounds never executed this path. Incident record runs/anchor_context_report_incident_2.json commits with the next records PR. Fix before registration 3: the drift check must verify the registered commit's code-tree identity against HEAD (or ancestry with unchanged code paths) rather than HEAD equality — mirroring how the first-estimates ceremony solved the same circularity with stable-identity documents plus records-merge execution. The fix is a code PR through the standing referee round; no input was opened and no value computed in either incident.

[vahid-ahmadi]

Superseded. Registration 5 (#328) is the live registration for the entry-10 anchor-context ceremony and states verbatim: "Registrations 1–4 were consumed (#317, #319, #322, #324 — incidents 1–5 all committed, latest records merge 809eeeb)."

Closing as bookkeeping, not as a decision about the ceremony. See #387. Reopen if any of these is still live.