From 2a90aa2a7ab205787b0c3f57a4edcb12e3233f99 Mon Sep 17 00:00:00 2001 From: Levi Neuwirth Date: Tue, 1 Sep 2026 21:10:32 +0200 Subject: [PATCH] docs(lane): stop the checkpoint from certifying itself Name f441d3d as the latest verified code head, not the lane's current head. The documentation commit carrying that old wording made it false on arrival. Keep the authoritative remote ref as the recovery source so later documentation-only commits need no self-referential SHA update. --- docs/active-work.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/docs/active-work.md b/docs/active-work.md index e0350f9..84625e6 100644 --- a/docs/active-work.md +++ b/docs/active-work.md @@ -347,9 +347,12 @@ At `175cc7b` — B5's own checkpoint, not the lane's current one — all fmt and `git diff --check` are clean. Four mutations were executed and each fires its named row: omit accepted-frame reflow, omit epoch-invalidation reflow, reshape content-only frames, and retain -divider hover on `Absent`. **The lane's current head is `f441d3d` at -312 GPU rows**; recover from the authoritative remote ref above, not -from this commit. +divider hover on `Absent`. **The latest verified code head is `f441d3d` +at 312 GPU rows**; the authoritative remote ref above may be ahead with +documentation-only commits and remains the recovery source. Calling +`f441d3d` the lane's "current head" here would become false in the +commit carrying the sentence — the self-certifying checkpoint defect +this ledger has already recorded elsewhere. **Landed but NOT yet witnessed** — recovery needs this split, because "L1–L8 owed" reads as though none of the mechanism exists: