Two stale self-description claims: a nonexistent planner rung, a retracted rationale #233

New issue

Closed

opened 2026-08-22 19:12:58 +00:00 by john · 0 comments

john commented

2026-08-22 19:12:58 +00:00

Owner

Two stale self-description claims, verified against the current tree on
2026-08-22. Low severity; grouped so they are not three separate tickets.

1. `DESIGN.md:373` names a rung that does not exist

The line reads:

*escalation* uses a small set of **variant agent files** (`planner-high`/`planner-low`, etc.)

cad-planner's actual ladder is high / xhigh / max
(lib/rung-agent.mjs:37-40), and the only files on disk are cad-planner.md,
cad-planner-xhigh.md and cad-planner-max.md. There is no low rung for any
role, and no planner-high file either.

2. `self-verify.test.mjs:1453-1455` carries a rationale the implementation retracted

The test still reads "skills, agents and templates carry no dispatch instructions
of their own, and references/ is in scope only because no other check reaches it
at all". self-verify.mjs:262-265 replaced that rationale with an accurate one
some time ago. The stale copy survives in the test that pins it, so the check's
stated reason for its own scope is wrong in the file a reader would consult to
confirm it.

Two stale self-description claims, verified against the current tree on 2026-08-22. Low severity; grouped so they are not three separate tickets. ### 1. `DESIGN.md:373` names a rung that does not exist The line reads: *escalation* uses a small set of **variant agent files** (`planner-high`/`planner-low`, etc.) `cad-planner`'s actual ladder is `high` / `xhigh` / `max` (`lib/rung-agent.mjs:37-40`), and the only files on disk are `cad-planner.md`, `cad-planner-xhigh.md` and `cad-planner-max.md`. There is no `low` rung for any role, and no `planner-high` file either. ### 2. `self-verify.test.mjs:1453-1455` carries a rationale the implementation retracted The test still reads "skills, agents and templates carry no dispatch instructions of their own, and references/ is in scope only because no other check reaches it at all". `self-verify.mjs:262-265` replaced that rationale with an accurate one some time ago. The stale copy survives in the test that pins it, so the check's stated reason for its own scope is wrong in the file a reader would consult to confirm it.