From 6b0ad8e5dddccca2202077b360255e42e95aa12f Mon Sep 17 00:00:00 2001 From: Levi Neuwirth Date: Wed, 19 Aug 2026 10:07:50 +0200 Subject: [PATCH] docs(lane): stop naming a stale ledger tip, and point at revision 8 Two state pointers were wrong. It named ledger tip fb40d88 while the branch was four commits past it, and identified the teardown framing as revision 5 on one line and revision 8 on the next. The tip pointer is removed rather than corrected. A literal SHA naming this branch's own head is stale the moment the next commit lands --- which is precisely how it came to say fb40d88 --- so the ledger now points at the branch head itself and says why. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_016bqGA6s9tTUFzYpbeW3tai --- docs/active-work.md | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/docs/active-work.md b/docs/active-work.md index 8bd3c61..494f06b 100644 --- a/docs/active-work.md +++ b/docs/active-work.md @@ -281,8 +281,12 @@ from #171 and #215. **`githubsucks/panel-mapping-generation` is the authoritative tip.** Recover with `git fetch githubsucks && git checkout panel-mapping-generation`. -- **No PR yet. Code-complete at `5174f73`; ledger tip `fb40d88`; the - slice-completion gate is RED.** Framing revision 16 (§5b) +- **No PR yet. Code-complete at `5174f73`; the slice-completion gate is + RED.** The ledger tip is **the branch head itself** + (`githubsucks/panel-mapping-generation`) — a literal SHA here goes + stale the moment the next commit lands, which is exactly how this + line came to name `fb40d88` while the branch was four commits past + it. Framing revision 16 (§5b) APPROVED 2026-08-15 at `7e85a6f`, then eleven implementation commits: wire shapes and pins (G0), the authoritative key with its terminal half (G1–G4), outbound family selection, inbound family gating, the @@ -496,8 +500,8 @@ from #171 and #215. enumerated with its own log digest in the teardown lane's `docs/probe-sigint-evidence.md`. - **The defect now has its own lane: - `gpu-probe-sigint-teardown`** (pushed; framing revision 5 at - `docs/gpu-probe-sigint-framing.md` (revision 7, `e2084fb`+), run provenance at + `gpu-probe-sigint-teardown`** (pushed; framing revision 8 at + `docs/gpu-probe-sigint-framing.md` (revision 8), run provenance at `docs/probe-sigint-evidence.md`). **§5b is held behind it.** That lane's framing supersedes every diagnostic claim below; the entries here are kept only as the record of how it was found.