From afc3973ebd3341ae88099bcfa87d395aec57f0c7 Mon Sep 17 00:00:00 2001 From: wshallwshall Date: Mon, 24 Aug 2026 09:54:15 -0500 Subject: [PATCH] docs(backlog): #1293's body still says the requirement is unmet, three lines under a banner saying it landed PR 568 landed the recreation doctrine into docs/LEDGER-GATE.md at 937e83da. The row's banner records that correctly. Its body, written before the fix, still reads "THAT REQUIREMENT IS NOT YET MET" and "the word appears in none of docs/LEDGER-GATE.md, docs/WORKTREES.md or CLAUDE.md", so a reader gets opposite answers from one item. Re-measured on origin/main with positive controls firing on all three files: LEDGER-GATE.md 3, WORKTREES.md 0, CLAUDE.md 0. The banner is NOT overstated and is left alone. It names LEDGER-GATE.md specifically rather than claiming all three, and the word is there. Only the body is stale. A report reaching me described the banner as overstating, which would have sent someone to weaken an accurate line. The pre-fix measurement is kept rather than deleted, marked as the state the ruling was answering. Whether the other two files need the doctrine is left explicitly unsettled -- one file of three is a fact, and whether that satisfies the ruling is the owner's call, not this edit's. Verified: 363 rows before and after, 253 open before and after, zero status changes, zero occurrences of the stale claim remaining. Co-Authored-By: Claude Opus 5 --- docs/BACKLOG.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/BACKLOG.md b/docs/BACKLOG.md index ae2562db..39b8218b 100644 --- a/docs/BACKLOG.md +++ b/docs/BACKLOG.md @@ -13506,7 +13506,7 @@ point, which are the parts that must survive it.** ***LANDED 2026-08-23 IN PR 556 AT `06ef8ec8`.*** *A removal that would strand a ledger number is now refused.* **195 tests pass.** -***OWNER RULING 2026-08-23: "Document recreation as the remedy." THAT REQUIREMENT IS NOT YET MET.*** *Recreating a worktree at the recorded path is the **written** remedy for a stranded ledger number, and **the REASON must be written with it: it RESTORES THE CONDITION THE GATE TESTS rather than bypassing the test.*** **Measured 2026-08-23: the word appears in none of `docs/LEDGER-GATE.md`, `docs/WORKTREES.md` or `CLAUDE.md`, against a control that fires.** ***An undocumented precedent gets copied without its justification, which is the specific failure the ruling names.*** +***OWNER RULING 2026-08-23: "Document recreation as the remedy." MET IN ONE FILE OF THE THREE NAMED BELOW; the banner above records which.*** *Recreating a worktree at the recorded path is the **written** remedy for a stranded ledger number, and **the REASON must be written with it: it RESTORES THE CONDITION THE GATE TESTS rather than bypassing the test.*** **Measured 2026-08-23, BEFORE `937e83da` landed: the word appeared in none of `docs/LEDGER-GATE.md`, `docs/WORKTREES.md` or `CLAUDE.md`, against a control that fires. That reading is kept because it is the state the ruling was answering, NOT because it still holds. RE-MEASURED 2026-08-24 on `origin/main`, positive controls firing on all three files: `docs/LEDGER-GATE.md` 3, `docs/WORKTREES.md` 0, `CLAUDE.md` 0. Whether the other two need it is UNSETTLED and deliberately not ruled here.** ***An undocumented precedent gets copied without its justification, which is the specific failure the ruling names.*** *NOT taken by the owner, recorded so neither is re-proposed:* **an `alloc.ps1 -Reassign`** -- *a deliberate hole in the non-transferable rule the gate rests on* -- *and* **letting a missing owner directory fall through**, *which would skip ownership entirely and fail OPEN once per number with nothing making "missing" unforgeable.*