Files
claude-config/todo.md
T

83 KiB

todo

Scoring

Score = 100 * V / (2**S + 32)

Bar = 0.1

Next ID = 369

Items

ID Release Blocked by Exempt Item L E I R S Moves Score
348 0.11.0 Read each project's credentials from the env file its config names, fail naming each missing key, and keep every value out of prompts, transcripts, logs and the archive. 2 2 4 6 3 1.6 by 2, 4 by 5 6.9
354 0.11.0 Read and write the decisions, score anchors, comprehension history, reading cost and changelog each through the backend its project's config names, with markdown files as one backend. 3 2 3 6 6 1.6 by 4, code health by 1 1.2
364 0.11.0 354 Read a client repo's own CLAUDE.md and AGENTS.md, propose to its team each change that aligns them with this setup, and record each conflict left as a decision in the project's records. 2 2 2 4 2 1.6 by 4, 1.2 by 2 2.2
360 0.11.0 Make chunk-pr merge wait for the human approvals a project's config requires, as part of the gate, before it merges. 2 2 3 5 3 1.6 by 5 1.6
357 0.11.0 Write prose in the language a project's config names, and title its commits, pull requests and branches by the templates it names. 3 2 3 6 4 1.6 by 5 1.4
350 0.11.0 Route every read and write of the plan, by tools and by agents, through one plan-store interface and todo-item, with the markdown file as one backend. 4 2 3 7 7 1.6 by 4, code health by 2 1.1
349 0.11.0 Convert markdown to ADF and back with @larvit/adf-codec's portable calls, through a pinned Node shim run in a container with a memory limit. 2 1 2 3 2 1.6 by 3 1.1
351 0.11.0 348, 349, 350 Read a project's plan from the child issues of a Jira Cloud epic its config names, ranked in Jira's backlog order. 3 2 3 6 5 1.6 by 6 1.2
353 0.11.0 351 Let a project's config take its goals and audience from a Jira epic's description, under the same two headings. 2 2 3 5 3 1.6 by 4 1.3
358 0.11.0 Let a project's config allow its runtime and tests on the host, and set the comprehension score under which code health is very important. 2 2 3 5 3 1.6 by 4 1.3
362 0.11.0 348 Send loop-claude's notices through the notifier a project's config names, with Mattermost as the first backend. 2 1 2 3 3 1.6 by 3 1.0
363 0.11.0 362 Add a Slack backend to the notifier, sending each notice as a DM from a bot. 2 1 2 3 3 1.6 by 4 1.3
352 0.11.0 351 Write a project's plan to its Jira epic: file items as child issues, edit those the loop filed, score unscored issues with a comment, and move a finished item to the status its config names. 3 2 3 6 5 1.6 by 6 1.2
355 0.11.0 348, 349, 354 Store a record on the Confluence Cloud page its config names, as markdown converted through the adf-codec shim, and interrupt the human when a teammate saved the page since the loop read it. 3 2 3 6 5 1.6 by 6 1.2
356 0.11.0 Hand reviewers the review standards from the folder a project's config names, in place of ~/.claude/skills/larv-review/standards/. 2 2 3 5 2 1.6 by 3 1.1
359 0.11.0 350 Tie a project's releases to what its config names: semver tags, Jira Fix Versions, sprints, or none. 3 2 3 6 4 1.6 by 3 0.8
361 0.11.0 360 Start the next item that doesn't touch a waiting pull request's files, in its own worktree and session, while that pull request waits for a human approval, and answer review comments on waiting pull requests as they arrive. 4 2 3 7 7 1.6 by 4, 1.5 by 5 0.7
319 0.12.0 Start a fresh session with a brief of the chunk when a rung step changes the worker's model, in place of resuming the old session. 3 2 3 6 4 1.1 by 2, 1.4 by 2 1.2
309 0.12.0 Run a scoring run's second pass on one head with two seats in place of four, once larv-review agreement shows the seats agree with each other more than a run agrees with its rerun. 2 2 2 4 2 1.4 by 3 1.2
299 0.12.0 Replay the archived judge verdicts through code rules and a classifier trained locally on the archive, and file an item for each verdict kind one of them decides with no missed interrupt. 2 2 2 4 3 1.4 by 3 1.0
311 0.12.0 Hand each worker's claude a Bash output ceiling that saves longer output to a file, and refuse a Read of a session transcript under ~/.claude/projects. 2 2 3 5 3 1.4 by 3 1.0
316 0.12.0 Launch comprehension seats as an agent type of their own under agents/, without CLAUDE.md and the skill and agent listings a general-purpose subagent carries. 2 2 2 4 3 1.4 by 3 1.0
339 0.12.0 Lower the reading cost of the files a chunk reads most before its first commit. 2 2 1 3 3 1.4 by 3 1.0
341 0.12.0 Hand each worker's claude a lower Read limit through CLAUDE_CODE_FILE_READ_MAX_OUTPUT_TOKENS, kept only where replays of the archived review rounds find what two unchanged replays find. 2 2 3 5 3 1.4 by 3 1.0
310 0.12.0 Compact a waiting worker's session shortly before its prompt cache expires, only when the human has not answered an interrupt by then. 3 2 3 6 4 1.4 by 3 0.9
298 0.12.0 Send the judge only the decision entries and the transcript tail a verdict needs, and keep the cut only where judge-replay changes no verdict kind. 3 3 3 7 4 1.4 by 2, 1.5 by 1 0.9
331 0.12.0 Reword four decisions to expire when the rungs their replays tested change, not whenever a model joins the ladder. 1 1 1 1 2 1.4 by 2 0.8
327 0.12.0 Have larv-review print a round commit's title prefix, counted from the round's report, and have rule-hook refuse a round title whose counts differ from it. 3 2 3 6 4 1.1 by 1, 1.4 by 1 0.6
365 0.13.0 352 Have score-outcomes read the finished and dropped items of a plan outside the checkout, from the project repo's history or from Jira's issue changelogs. 3 2 2 5 4 1.6 by 2, 1.1 by 2 1.2
368 0.13.0 352 Call a release review due, call a release ready to cut, and tell whether a chunk owes a scoring run, for a plan outside the checkout, from the project repo's history or from Jira. 3 2 2 5 4 1.6 by 2, 1.1 by 2 1.2
366 0.13.0 352 Count the chunks of a project whose plan sits outside the checkout in the routing figures, from the project repo's history or from Jira. 3 2 2 5 4 1.6 by 2, 1.4 by 2 1.1
367 0.13.0 352 Check that every write to a Jira plan leaves it ranked, as rule-hook's todo-rank-check checks todo.md today. 2 2 3 5 3 1.6 by 2 0.7
303 0.14.0 defect Archive each judge run's prompt and json reply beside the verdict it gave, so judge cost, replays and backups cover the judge as they cover the worker. 2 2 3 5 3 1.4 by 3, 3 by 2 4.2
306 0.14.0 Set a strategy that keeps loop-claude's archive and larv-review's review folders backed up and small over the years, compressing older entries without losing any. 3 2 4 7 5 3 by 5 3.9
304 0.14.0 303 defect Archive each review-replay and judge-replay run's transcript beside its result, so a replay that decided a rung can be checked and re-priced later. 2 2 2 4 3 1.4 by 2, 3 by 2 3.8
287 0.14.0 Move the forge helpers Forge, forge_of, runner, open_pull, merged_pull, pull_at, gitea, checks_passed and required_checks into one module that chunk_preflight, chunk_pr, deploy_release and larv_review all import from, so no tool imports another tool's internals for them. 3 1 3 5 5 code health by 3 2.9
338 0.14.0 owner Script each step that 0.9.0's chunks repeated by hand and a program can compute, filing one item per step, and file this audit again for the next release. 1 2 1 2 2 1.4 by 3, 1.5 by 3 2.3
288 0.14.0 Point the two reading-cost decisions at code health and goal 1.4's counter-signal, in place of the goal 1.1 they cite. 1 2 1 2 1 code health by 1, 1.4 by 1 2.2
77 0.14.0 Teach bin/metric-bench Go and TypeScript, rerun it once two projects' comprehension histories name places, and bring into review only a metric that tracks the panel. 4 2 1 5 6 1.1 by 7, 1.4 by 7 2.1
196 0.14.0 decision Replay the architecture, principles, overrides and product-owner passes with review-replay on Opus 5.5 projects, record each run in the review-replay routing decision, and, where a run qualifies a rung, add back the code that lowers a pass to it. 2 2 3 5 2 1.4 by 3 1.2
321 0.14.0 196 decision Evaluate the review passes that run on a rung review-replay qualified, against the chunks before them, and revert any pass whose findings or later fixes worsened. 1 2 1 2 2 1.1 by 3, 1.4 by 2 2.0
273 0.14.0 decision Re-tune the E + I steps of REVIEW_STEPS for 6 to 8 once 10 finished chunks have scored an E + I of 6 or more, from how well E + I orders their review rounds and 🔴 findings. 1 2 2 3 2 1.1 by 2, 1.4 by 3 2.0
268 0.14.0 End a run whose release is ready to cut with a notice on loop-claude's terminal, in place of an interrupt that waits for an answer. 2 2 3 5 3 1 by 5 1.9
171 0.14.0 decision Group the routing figures' review rounds by the reviewers' rung as well as the worker's, so a call blames a rung only for rounds its own reviews raised. 3 2 2 5 4 1.2 by 3, 1.4 by 3 1.8
300 0.14.0 owner Reach the comprehension floor: restructure the places the comprehension seats found hardest to follow, so the project reads at 7.0 or above on every dimension, Locality and Self-sufficiency first; today the scoring run at 8f03747 scored Navigation 6.75, Locality 5.63, Shape 5.75, Self-sufficiency 5.63 and Overall 6.00. 4 2 3 7 8 code health by 8 1.7
264 0.14.0 Report the comprehension seats and the escalated subagents as subagent types of their own in routing-figures.md, with their dollars. 2 2 1 3 3 1.4 by 5 1.7
323 0.14.0 Count a release review as landed once its pull request has merged, whatever its commits are titled. 3 2 3 6 3 1.4 by 3, 1.5 by 2 1.7
342 0.14.0 Research the tooling agents read, search and run commands with once more, and file an item for each tool that cuts tokens a replay shows keep quality. 1 2 1 2 3 1.4 by 3, 1.5 by 2 1.7
149 0.14.0 decision Fill each release by priority up to a capacity it states, in place of the bar, and move what does not fit to a later release. 4 2 3 7 5 1.1 by 7 1.6
165 0.14.0 Make this repo's tests assert the facts a prompt or help text carries in place of its sentences, and drop the tests that scan source or assert a constant. 3 2 1 4 5 1.1 by 4, 1.4 by 3 1.6
151 0.14.0 decision Keep 10 to 20 settled decisions per project as its goals' test set, and rerun them after a goal changes. 3 2 2 5 5 1.2 by 7 1.6
68 0.14.0 principle Test workflow-bench/compare.py's blinding and bench.py's run plan. 2 1 1 2 4 1.1 by 5 1.5
102 0.14.0 Give loop-claude's retry delay, and the file it reads the machine's memory from, environment overrides, so the black-box test stops replacing time.sleep and machine_load.memory.MEMINFO through sitecustomize. 1 1 2 2 3 1.1 by 4 1.5
135 0.14.0 Fingerprint only the modules loop-claude imports, so editing another tool's code no longer reloads a running loop. 2 2 3 5 3 1.1 by 4 1.5
5 0.14.0 decision Key a project on its checkout's full path, and refuse to start while another session uses that key. 4 2 3 7 5 1.1 by 6 1.4
291 0.14.0 owner Let principles/technical-principles.md → "Sane defaults" allow a library whose README goals ask that it work with no config to default the clock and randomness in its public constructor, where a documented option overrides each. 1 2 3 4 1 1.2 by 3 1.3
156 0.14.0 decision Drop rank_todo.py's ranking of an old-shape table once no project under ~/code holds one. 2 1 3 4 4 1.1 by 4 1.2
260 0.14.0 decision Compare the first 20 chunks whose worker got the reading rule with the 20 before them, on review rounds past each pass's first, unfinished verdicts, 🔴, 🟡 and misread findings, dollars and hours per chunk, and drop the rule where any rose. 1 2 1 2 2 1.4 by 3 1.2
51 0.14.0 principle Hand loop-claude's terminal output to an injected effect, so no storage or retry function prints. 2 1 3 4 5 1.1 by 5 1.1
201 0.14.0 owner Save the human's tmux setups and restore them after a reboot, so work is up and running again quickly. 3 2 1 4 4 1.5 by 4 1.1
267 0.14.0 Keep waiting when an interrupt gets an empty answer, at the terminal or in the claude opened for it, in place of stopping the loop. 2 1 3 4 2 1.5 by 3 1.1
4 0.14.0 Name each chunk's archive folder by the chunk's start time, so <key>/ lists chunks in the order they ran. 3 2 3 6 3 1.1 by 3 1.1
324 0.14.0 Count in the routing figures the finished chunks whose worker wrote no Chunk items: line. 2 2 1 3 3 1.1 by 2, 1.4 by 1 1.1
187 0.14.0 Count the tokens a worker spends reading reviewers' reports, so goal 1.4's signal shows whether report files lowered what a review costs the worker's context. 2 2 1 3 3 1.4 by 3 1.0
266 0.14.0 Move the chunks archived under the key home/lilleman/.claude to the key claude-config, so the routing figures and score-outcomes count this repo's chunks as one project. 3 2 2 5 3 1.4 by 3 1.0
181 0.14.0 principle Have the test of a quoted answer's step-up assert the stepped rung's facts as literals, not through prompts.rungs_held. 1 1 1 1 1 1.1 by 2 0.9
193 0.14.0 Narrow readme_goals's mark to Mark by a typed lookup in place of typing.cast, so a mark added to the regex but not the lookup fails at run time, and one added to the lookup but not Mark fails mypy. 1 1 3 3 1 1.1 by 2 0.9
194 0.14.0 Make test_waits_out_a_usage_limit_which_ends_a_run_of_failures expect a usage-limit wait independent of the wall-clock time that passes during the run. 1 1 1 1 1 1.1 by 2 0.9
265 0.14.0 Archive each wait that costs a chunk wall time, for a usage limit, low memory, a failed worker start or a heavy slot, with its start and end stamps, so goal 1.5's hours split waiting from work. 3 2 2 5 4 1.5 by 3 0.8
169 0.14.0 Have rule-hook's todo-rank-check catch a todo.md that the same Bash call edits and then commits. 3 1 3 5 3 1.1 by 2 0.7
197 0.14.0 Let the human edit what they type at loop-claude's terminal questions with the arrow keys, so Left moves the cursor in place of printing ^[[D. 2 2 3 5 2 1.5 by 1 0.4
1 0.15.0 question Say in README → Install how the transcript archive is backed up, once bender-infra backs up ai-sandbox's data volume. 1 2 1 2 1 0.0

Details

348. Read each project's credentials from the env file its config names, fail naming each missing key, and keep every value out of prompts, transcripts, logs and the archive.

lilleman's call, 2026-11-12: credentials (Jira and Confluence API token, GitHub, Mattermost or Slack token) come from a per-project env file such as ~/.claude-projects/<key>.env, outside the project's repo and named in the config. Which account each service uses is a config setting: a bot account or lilleman's own. A test shows a value never reaches a worker or judge prompt, a log line or the transcript archive, which guards goal 4. Today ~/.claude/.env serves every project.

354. Read and write the decisions, score anchors, comprehension history, reading cost and changelog each through the backend its project's config names, with markdown files as one backend.

lilleman's call, 2026-11-12: each record has its own backend setting, so a client project can keep, say, decisions and changelog in Confluence and anchors and comprehension history as files. Which goes where is asked per client at setup. Every tool and agent that reads or writes a record goes through the interface: the judge's records, rank_todo.py's decision check, todo-item finish --changelog, larv-review's scoring and places, score-outcomes, rules/decisions.md. The plan store's contract suite has a twin for records, on fakes. R is above 5, so this item ships alone.

364. Read a client repo's own CLAUDE.md and AGENTS.md, propose to its team each change that aligns them with this setup, and record each conflict left as a decision in the project's records.

lilleman's call, 2026-11-12: the loop may change every file in a client repo, but in agreement with the team, so a change to their instruction files goes to them as a proposal in a pull request. Where a conflict stays, the loop records which rule it follows and why as a decision in the project's decision record, so it is never asked twice. This is a working rule in CLAUDE.md.

360. Make chunk-pr merge wait for the human approvals a project's config requires, as part of the gate, before it merges.

lilleman's call, 2026-11-12: this client requires another human's approval on every pull request, so the gate covers it, and the loop still merges once the gate passes. Until this ships, lilleman merges such pull requests by hand and restarts the loop. On GitHub, read the approvals the branch protection asks for; this client's forge is GitHub.

357. Write prose in the language a project's config names, and title its commits, pull requests and branches by the templates it names.

lilleman's call, 2026-11-12: a client may want docs and Jira text in another language than English, and may use a commit, PR or branch format other than CLAUDE.md's ABC-123 - ... and ABC-123. Everything reads the project's setting: CLAUDE.md → "Prose" and "Git, commits, and PRs", chunk-preflight's branch and worktree names, chunk-pr's titles, rule-hook's round-title checks and score-outcomes' Drop item titles. The prose reviewer judges prose in the configured language.

350. Route every read and write of the plan, by tools and by agents, through one plan-store interface and todo-item, with the markdown file as one backend.

After item 344 every reader finds todo.md by its configured path, but each still parses the markdown itself, and agents still Read and grep the file. After this item agents list, show, add, edit, move and finish items only through todo-item, which gains list, edit and move commands. rules/todo-items.md loads today only when a session touches a todo.md, so it must load another way for a plan with no file. The interface carries what ranking needs: ID, release, blocked by, exempt, tagline, L, E, I, S, moves, detail, and an order the backend supplies (score order for markdown, Jira rank for Jira). One contract suite runs against every backend, on fakes only, per lilleman's call of 2026-11-12. R is above 5, so this item ships alone.

349. Convert markdown to ADF and back with @larvit/adf-codec's portable calls, through a pinned Node shim run in a container with a memory limit.

lilleman's call, 2026-11-12: Jira Cloud descriptions and Confluence pages are ADF, and the loop keeps working in markdown. Write with portableMarkdownToAdf and read with adfToPortableMarkdown. The shim reads stdin and writes stdout, runs in a node:<patch> image with a pinned adf-codec version, and returns adf-codec's error codes as a Failure.

351. Read a project's plan from the child issues of a Jira Cloud epic its config names, ranked in Jira's backlog order.

lilleman's calls, 2026-11-12. One epic is one project's plan. An item is a child issue: its key is the item's ID, so branches, worktrees and commit and PR titles follow CLAUDE.md's ticket rules (ABC-123, ABC-123 - ...). Summary is the tagline, description the detail (ADF, read through the adf-codec shim). Release is the Fix Version, or what item 359 configures. Blocked by is the "is blocked by" link. L, E, I, S, Moves and Exempt are issue entity properties, so no Jira admin is needed; the computed score also shows as a label such as score-2.4. Jira's backlog rank decides the order, since the team sets it; the loop's score doesn't break ties, and the loop doesn't reorder anything others filed. Auth: email plus API token from the project's env file.

353. Let a project's config take its goals and audience from a Jira epic's description, under the same two headings.

lilleman's call, 2026-11-12: this client keeps its goals and audience in the plan epic's description. The source is a config setting, never hard-coded; item 346 builds the file source this one adds to. Read through the adf-codec shim.

358. Let a project's config allow its runtime and tests on the host, and set the comprehension score under which code health is very important.

lilleman's calls, 2026-11-12. Legacy products may have no container setup, so the config may allow host tooling; CLAUDE.md's container rule and rule-hook then follow it. In 0.10.0 a decision in the project's records can put tooling on the host instead. The comprehension panel will score legacy code low, and today code health under 7.0 is very important. The config sets that floor, 7.0 in the configs of the projects under ~/code; the signal stays that the score rises.

362. Send loop-claude's notices through the notifier a project's config names, with Mattermost as the first backend.

lilleman's call, 2026-11-12: each project names its notifier, server and recipient, so client notices can go to a client's workspace. Today bin/mattermost-dm reads one server from ~/.claude/.env for every project.

363. Add a Slack backend to the notifier, sending each notice as a DM from a bot.

lilleman asked for a Slack driver on 2026-11-12, for clients on Slack. The bot token comes from the project's env file.

352. Write a project's plan to its Jira epic: file items as child issues, edit those the loop filed, score unscored issues with a comment, and move a finished item to the status its config names.

lilleman's calls, 2026-11-12. Without asking, the loop may create child issues in the epic, edit the summary, description and scores of issues it created, and comment on and transition any issue in the epic. It never edits the summary or description of an issue a person filed. An issue a teammate files without scores gets scored like any item, with a short comment saying it was scored and why; its scope stays as written. A finished item moves by the transition and to the status the config names, since each Jira workflow differs. An issue the loop files goes into Jira rank by its score among the issues the loop filed. A security finding is filed in the epic like any item, labelled security and ranked first, never with a secret's value. R is above 5, so this item ships alone.

355. Store a record on the Confluence Cloud page its config names, as markdown converted through the adf-codec shim, and interrupt the human when a teammate saved the page since the loop read it.

lilleman's calls, 2026-11-12: one page per record, whose ID the config names. The loop reads the page's ADF as portable markdown and writes markdown back through adf-codec. It writes with the version number it read; where Confluence reports a newer version, the loop asks the human, and never overwrites a teammate's edit on its own. Auth: email plus API token from the project's env file.

356. Hand reviewers the review standards from the folder a project's config names, in place of ~/.claude/skills/larv-review/standards/.

lilleman's call, 2026-11-12: the folder replaces the default, as item 347's principles folder does. Readers: the reviewers under agents/, the judge's records, larv-review, and the repo check that keeps the standards present.

359. Tie a project's releases to what its config names: semver tags, Jira Fix Versions, sprints, or none.

lilleman's call, 2026-11-12: what a release is differs per client. With none, items name no release, and the architecture and principles passes the release review runs need another trigger, which this item settles and records. Readers: rank_todo.py's release order, chunk-preflight's next release, loop-claude's "release ready to cut", larv-review's release review, CLAUDE.md → "Working loop". Cutting a release stays the human's.

361. Start the next item that doesn't touch a waiting pull request's files, in its own worktree and session, while that pull request waits for a human approval, and answer review comments on waiting pull requests as they arrive.

lilleman's call, 2026-11-12. Today a project has one session and one chunk at a time; this changes that core, so archive keys, loop-inbox, routing, the session lock and item 345's commits to the project repo all learn more than one open chunk. A chunk whose pull request gets a review comment resumes in its own session. R is above 5, so this item ships alone.

319. Start a fresh session with a brief of the chunk when a rung step changes the worker's model, in place of resuming the old session.

On SWE-bench Verified with Haiku 4.5 and Opus 4.7, handing the strong model the weak model's transcript solved 69.2% at $1.61 a task; starting the strong model fresh solved 79.2% at $0.90 (arXiv 2608.24358, The Handoff Tax). A model switch also rereads the whole context uncached (Claude Code prompt caching docs). A worker that steps from Sonnet 5.5 to Opus 5.5 by --resume is the raw handoff; an effort-only step within one model keeps the cache and isn't. The escalated subagent, which starts fresh with the trigger's evidence, already follows the pattern that won.

Bench it first on workflow-bench: resume against a fresh start with a brief. The brief is the chunk's item, its branch and diff, open findings and the trigger. lilleman approved on 2026-11-11. Revise the decision routing: a worker whose run ends asking for a higher rung….

309. Run a scoring run's second pass on one head with two seats in place of four, once larv-review agreement shows the seats agree with each other more than a run agrees with its rerun.

Seats cost $1,143 of the $9,154 measured from 2026-09-30 to 2026-11-11 (12.5%), scoring runs $470 of that. A scoring run today is four seats, run twice on one head: eight seat runs. Two seats on the second pass make it six, and two on both passes four.

Why it should hold quality: the seats are one model with different personas, so their errors are correlated, and a correlated extra seat adds little. larv-review agreement showed on 2026-11-11 that Mid A and the inherited architect voted alike in 58 of 75 paired rulings, while their scores moved alike between two runs on one commit in only 1 of 4 pairs: seats agree with each other more than a run agrees with its rerun, so the rerun carries more new information than the third and fourth seat. Nine judges from seven model families carried about two independent votes (arXiv 2605.29800), and ten with error correlation 0.21 carried 3.5 (arXiv 2609.22512).

Decide once agreement has its 10 commits scored twice. Keep four seats on any pass that files a floor item, since its places come from seat reports. Revise the decision review: the comprehension check records how hard a project is to read…, which names the four-seat run.

299. Replay the archived judge verdicts through code rules and a classifier trained locally on the archive, and file an item for each verdict kind one of them decides with no missed interrupt.

The judge's LLM still decides three things: the verdict kind, the escalation it quotes, and whether a release is ready to cut (docs/decisions.md → routing: loop-claude reads the items a chunk takes …). This item replays the verdict kind. No single rule found so far separates interrupts: a "?" in the worker's final message appears in 48 interrupts and misses 66. A smaller LLM already failed the replay (docs/decisions.md → routing: on a model judge-replay covered, …: Sonnet returned another kind on 3 interrupts, Haiku missed 7). Untested are combined code rules, a decision table, and a small classifier trained and run on this machine on the archived verdicts (372 finished, 234 interrupt, 42 unfinished, 20 quoted). Run each offline, nothing sent to an outside service (goal 4), and count disagreements by kind; the bar is zero missed interrupts. A hosted decision model is out of scope, since it would send transcripts to an outside service.

311. Hand each worker's claude a Bash output ceiling that saves longer output to a file, and refuse a Read of a session transcript under ~/.claude/projects.

Workers took 7,870 Bash results over 3,000 characters, $305 of carried context, against the reading rule in their prompt; stability reviewers another $145. BASH_MAX_OUTPUT_LENGTH (or bashOutputMaxChars) makes Claude Code save a longer result to a file and hand the model its path and the first 2,000 characters. loop-claude can hand it as it hands CLAUDE_CODE_AUTO_COMPACT_WINDOW. A ceiling of 6,000 characters would have removed $228 of carried output, 10,000 characters $122. Reads of old session transcripts cost $46; a rule-hook rule can refuse them, but not a Read of the files Claude Code saves a long Bash result to: they sit under ~/.claude/projects/<project>/<session>/tool-results/, the archive holds 85 of them (item 312's round, 2026-11-12), and the saved-to-file ceiling hands the model their path to read.

Subagents inherit the variable, and the decision of 2026-10-27 found a 12k cap cost stability reviewers a finding (3 of 6 against 4 of 6). That cap left no file to read, and the difference is inside the noise that decision reports. So keep the ceiling only where a replay of the archived stability rounds finds what two baseline replays find, and join item 260's comparison.

316. Launch comprehension seats as an agent type of their own under agents/, without CLAUDE.md and the skill and agent listings a general-purpose subagent carries.

Seats run as general-purpose subagents, so each starts with the skill and agent listings, about 7,500 tokens, at $9.00 per 1,000 prefix tokens over the archive measured from 2026-09-30 to 2026-11-11: about 1.3% of spend. An agent under agents/ with Read, Grep, Glob and Bash, omitClaudeMd: true, and the seat's persona in its prompt drops both; a seat reads the project as a newcomer does, which is what it simulates. Keep each seat's prompt from skills/comprehension-panel/seat-prompts.md. Check that a scoring run's scores on one head stay within the spread two runs of today's seats show. lilleman approved on 2026-11-11.

339. Lower the reading cost of the files a chunk reads most before its first commit.

reading-cost printed Rising: on 2026-11-12: the last 5 chunks' median is 128,199 new input tokens before their first commit, the 5 before them 101,795. Read most over the last 5, as opens and searches: todo.md 34, docs/decisions.md 26, README.md 19, skills/larv-review/SKILL.md 13, bin/loop_claude/routing.py 8, CHANGELOG.md 6. The chunk that ships this runs reading-cost --reset.

341. Hand each worker's claude a lower Read limit through CLAUDE_CODE_FILE_READ_MAX_OUTPUT_TOKENS, kept only where replays of the archived review rounds find what two unchanged replays find.

Raised by item 312's research round, 2026-11-12. Over the 53 chunks archived since 2026-09-30, Read results held about 3.17M tokens (characters / 4) in 1,617 reads. Results over 20,000 characters, about 5,000 tokens, held 479k tokens beyond that size in 115 reads: prose reviewers 144k, stability reviewers 119k, product-owner reviewers 102k, general-purpose subagents 65k, principles auditors 28k, architects 21k. Workers had none, under the reading rule in their prompt. Measured with a script over loop-claude's archive that sums each Read tool_result's characters by the subagent's agentType. The decision of 2026-10-27 found Read results out of a PostToolUse hook's reach; this variable reaches them.

CLAUDE_CODE_FILE_READ_MAX_OUTPUT_TOKENS overrides the Read tool's default limit of 25,000 tokens (https://code.claude.com/docs/en/env-vars, read 2026-11-12: "Override the default token limit for file reads, which is 25,000 tokens."). Claude Code 2.1.322's binary holds the name. A read over the limit fails and asks for an offset and a limit, so an agent may page through the same file and save nothing; the replay measures that.

loop-claude can hand it as it hands CLAUDE_CODE_AUTO_COMPACT_WINDOW, and subagents inherit it, the principles auditors included. The choice of 2026-10-27 that the principles audit reads the project whole holds as long as it pages through what it reads.

The replay: give review-replay a way to set the variable, then replay the archived prose, stability, product-owner and principles rounds at 5,000 tokens, beside two unchanged replays of the same rounds. Keeps quality where each pass finds every finding the two unchanged replays both find, or misses no more than the most an unchanged replay misses, as review-replay --omit-claude-md counts it. Keep it only where the replays' Read characters also fall; item 311's stability replay can share the baseline runs.

310. Compact a waiting worker's session shortly before its prompt cache expires, only when the human has not answered an interrupt by then.

281 worker resumes after the 1-hour cache expired rewrote a whole context, $379 of the $9,154 measured from 2026-09-30 to 2026-11-11 (4.1%). A compaction while the cache is warm reads the context at a twentieth of the input price and leaves about 20k tokens to rewrite later.

lilleman, 2026-11-11: do it on a timer, so an answer that comes in time doesn't cost anything. When loop-claude interrupts, start a timer a margin short of the cache lifetime (about 50 minutes of a 1-hour cache; read the lifetime from the session's last cache_creation usage). If no answer has come when it fires, compact the session, then keep waiting. Skip it below about 60k tokens of context, where the rewrite costs less than the compaction. A wait for a usage limit can't be helped this way.

Probe first that claude -p "/compact" --resume <id> compacts a session: the Agent SDK documents /compact as a prompt, the CLI pages don't show it. Claude Code compacts idle interactive sessions itself ("Compacted while idle"), but not -p runs. Check: the cost entries of 20 chunks with an interrupt, before and after.

298. Send the judge only the decision entries and the transcript tail a verdict needs, and keep the cut only where judge-replay changes no verdict kind.

153 Judge cost: entries total $109.76, a median of about $0.76 a verdict at every rung, and the cost follows the size of the records, not the transcript: about 76k characters in log and 188k in claude-config. In 224 of 251 recent verdicts (89%) the evidence sits in the worker's final message. A missed interrupt is the costly error, so the bar is zero changed interrupts and zero new rejections across the replay. The judge is about 4.5% of dollars, so the saving is small; each cycle also gets faster.

331. Reword four decisions to expire when the rungs their replays tested change, not whenever a model joins the ladder.

The architect's 🔀 answer on PR #493 (item 292): four decisions expire "when a new model joins the ladder". Fable 5.2 joined above every project model's rung, and none of these replays tested a rung above the project's, so the event fired with nothing new to test. Every later ladder rebuild would fire all four again.

  • review: each pass keeps a reviewer of its own: the merge trials ran on Opus 5.5 at medium. Reword the "Valid" line to name that rung.
  • review: the principles audit runs only in the release review…: its trial ran on the project's rung. Reword the line to name that rung.
  • routing: a review pass runs below the project's rung only on a rung whose replay of its rounds finds a share of their 🔴 and 🟡 findings no more than a margin below the project's rung's own replay…: review-replay tests only rungs below the project's rung. Have the line expire when those rungs change, the event item 196 names ("until a cheaper model joins the ladder").
  • routing: on a model judge-replay covered, the judge runs…: the replays tested the project's rung and below, and each rung above it that a review climbs to. Have the line expire when those rungs change.

lilleman approved rewording all four as above on 2026-11-12.

327. Have larv-review print a round commit's title prefix, counted from the round's report, and have rule-hook refuse a round title whose counts differ from it.

The 0.8.0 audit (item 284) measured, over the 35 chunks that shipped 0.7.0: 72 commit calls in 33 chunks titled Answer <pass> round <n>: R 🔴, Y 🟡 (K misread); <what changed>, about 11k command tokens, most of them the summary. Each worker counts R, Y and K by hand. All three are in the round's report, <pass>-round-<n>.md in the review folder: R and Y are its finding headings, and K counts the findings the reviewer marked [misread], as bin/review_rules/round_titles.py says. That module parses the counts for score-outcomes, which reports them as goal 1.1's signal, and rule-hook's round_cap.py checks only the round number, so nothing checks today that the counts match the report. Of the 8 titles whose report the audit could match, none miscounted; one report wrote its markers at line start rather than in ### headings, so the reports' format varies by reviewer.

Add a larv-review subcommand that prints a round title's prefix, up to and including the ;, from the round's report, and have rule-hook refuse a round title whose counts differ from it. Pin the marker format in each reviewer's definition under agents/, or count every format the reports use today. Where the report is missing, say so and let the commit through.

Left with the model: the summary after the ;, and answering the findings.

365. Have score-outcomes read the finished and dropped items of a plan outside the checkout, from the project repo's history or from Jira's issue changelogs.

lilleman's call, 2026-11-12: 0.10.0 and 0.11.0 switch the history tools off for a plan outside the checkout, and 0.13.0 holds only their ports. In Jira a dropped item, which Drop item commit titles mark today, is an issue resolved by a resolution the config names.

368. Call a release review due, call a release ready to cut, and tell whether a chunk owes a scoring run, for a plan outside the checkout, from the project repo's history or from Jira.

One of 0.13.0's history ports, per lilleman's call of 2026-11-12. Filed from item 344's stability review, round 1.

Today a plan outside the checkout is read as it stands, since no commit holds it. So:

  • bin/release_plan/release_standing.py's todos_since holds one text. Once a release's last item ships, the plan no longer names the release, and next_release gives the release after it as next. chunk-preflight and loop-claude say UNSEEN_RELEASES on every run: the release reviews and the cuts are the human's to call.
  • bin/larv_review/owed.py's owed_scoring_run says it cannot tell whether the chunk owes a scoring run, and the merge goes on. needs-scoring-run and record-scoring refuse the ID of an item the plan no longer holds.

Read the plan's earlier texts from the project repo's commits, which item 345 writes, or the releases Jira's issues name. Then drop UNSEEN_RELEASES and both refusals, and the bullets that record them in docs/decisions.md → "project config: a tool that reads a file's commits …".

The comprehension seats found next_release hard to read: the tag cases, dated headings, renames and named_releases meet in one function. Make it easier to read while there.

366. Count the chunks of a project whose plan sits outside the checkout in the routing figures, from the project repo's history or from Jira.

One of 0.13.0's history ports, per lilleman's call of 2026-11-12.

367. Check that every write to a Jira plan leaves it ranked, as rule-hook's todo-rank-check checks todo.md today.

One of 0.13.0's history ports, per lilleman's call of 2026-11-12.

303. Archive each judge run's prompt and json reply beside the verdict it gave, so judge cost, replays and backups cover the judge as they cover the worker.

Today no judge transcript reaches loop-claude's archive. bin/claude_code/reply.py runs every headless reply, the judge's included, with --no-session-persistence, so its runs stay out of the session picker; Claude Code then writes no session file for the archive to copy. No decision chose to leave the judge out: loop-claude: the archive keeps the raw transcript was written for the worker's .jsonl. Goal 3 asks for the transcripts of unattended runs to be backed up, and the judge is one. The gap also leaves the judge's spend measurable only from the Judge cost: lines, which older verdicts lack ($136 recorded over 2026-09-30 to 2026-11-11), and leaves judge-replay rebuilding each prompt from today's records: of the 39 verdicts it replayed on 2026-10-15, 8 may rest on records that had changed since.

The judge runs with no tools and one turn (judge_args in bin/loop_claude/cycle/judge.py), so its whole transcript is the prompt it read and the json reply. Recommended: keep --no-session-persistence, and have the archive write the prompt and the reply beside the outcomes entry of the verdict, interrupt or rejected reply they produced, deduplicated by content hash as the worker's copies are. A failed write stops the loop, as that decision says. Persisting the session and copying its file would also work, but fills the picker and needs a cleanup. The prompt repeats the worker's transcript, which the archive already holds: measure the size per cycle first, and if it outgrows "small enough to copy whole", keep the prompt without the transcript part and name the worker copy and entry range it held. Then let judge-replay read the archived prompt where one exists, and price the judge from the archived reply's usage. Update that decision entry to say the judge's runs are archived too.

306. Set a strategy that keeps loop-claude's archive and larv-review's review folders backed up and small over the years, compressing older entries without losing any.

Measured on 2026-11-11: loop-claude's archive is 6.3 GB (12,721 files from October alone, 0.84 GB older than 30 days), and ~/.local/state/larv-review/ is 997 MB, 984 MB of it under code/, with no pruning: skills/larv-review/SKILL.md → "Reports" keeps every folder after the merge, because review-replay replays rounds from them. The largest archived worker transcript, 23.4 MB, gzips to 9.1 MB at level 6. The disk holds 65 GB free today.

Write the strategy as a decision, then build it:

  • Backup. Item 1 waits on ai-sandbox's data volume backup; check that both ~/.claude/loop-claude-transcripts and ~/.local/state/larv-review sit on that volume, since the review folders live outside ~/.claude.
  • Retention. Keep everything: the archive is the evidence every routing and replay decision rests on. Compress entries older than a threshold (such as 30 days, or once a chunk is finished and measured) with a format the tools read transparently, such as zstd. Compress, verify the round trip, then remove the original, never the reverse; a failure keeps the original and stops, as a failed archive does.
  • Readers. bin/transcript_archive, routing_figures, score-outcomes, review-replay, judge-replay and reading-cost must read compressed entries; test each on one.
  • Revise loop-claude: the archive keeps the raw transcript, whose validity is "while transcripts stay small enough to copy whole".

304. Archive each review-replay and judge-replay run's transcript beside its result, so a replay that decided a rung can be checked and re-priced later.

Today review-replay and judge-replay leave no transcript: both run claude through claude_reply in bin/claude_code/reply.py, whose --no-session-persistence makes Claude Code write no session file, as item 303 describes for the judge. A replay decides which rung a review pass or the judge may run on (routing: a review pass runs below the project's rung only on a rung that a replay of its rounds shows…, and the judge's rung on JUDGE_REPLAYED), so the runs behind a routing decision can't be read again, re-priced or re-scored once the decision is questioned. Goal 3 asks for the transcripts of unattended runs, the bench's included, to be backed up; workflow-bench/bench.py already keeps its claude stream in logs/.

Unlike the judge, a replayed reviewer uses tools over several turns, so its transcript is more than its prompt and reply. Recommended: have claude_reply take --output-format stream-json --verbose in place of json, keep --no-session-persistence, write the stream where the replay keeps its result, and read the reply from the stream's last result event. That also gives item 303 the judge's stream for free, so build on 303's archive layout and do both callers through the one runner.

287. Move the forge helpers Forge, forge_of, runner, open_pull, merged_pull, pull_at, gitea, checks_passed and required_checks into one module that chunk_preflight, chunk_pr, deploy_release and larv_review all import from, so no tool imports another tool's internals for them.

Today the helpers live in two tools. Forge is defined in bin/chunk_preflight/gathered.py and imported by bin/chunk_preflight/choices.py, bin/chunk_preflight/facts.py, bin/chunk_preflight/main.py and bin/chunk_pr/main.py, and again through choices by bin/deploy_release/forge.py. forge_of lives in choices.py, which bin/chunk_pr/main.py, bin/deploy_release/cut.py and bin/larv_review/reviewer_header.py import. open_pull, runner and gitea live in bin/deploy_release/forge.py, which bin/chunk_pr/main.py and bin/larv_review/reviewer_header.py import. So deploy_release imports chunk_preflight, and chunk_pr and larv_review import both.

Both comprehension seats of PR #453's paired ruling (2026-11-09) named this web as a place that cost them time, and neither saw a reason for it: a second forge would need edits in chunk_preflight, deploy_release, chunk_pr and larv_review.

Put the seven helpers in a folder named by what it holds, such as bin/forge/, and import them from there. Keep each helper's behaviour and its tests. chunk_preflight/choices.py keeps pulls_command, which is preflight's own. Check docs/decisions.md for a mention of where a helper lives, and update it.

338. Script each step that 0.9.0's chunks repeated by hand and a program can compute, filing one item per step, and file this audit again for the next release.

lilleman asked, on 2026-10-16, for a standing audit each release, so the loop keeps moving work a program does as well from the model to scripts (goals 1.4 and 1.5). This audit reads the archived transcripts of the chunks that shipped release 0.9.0 for every step that chunks repeated by hand, before, during or after review. It keeps the steps whose answer a program computes the same way each time, such as a lookup, a check, a prompt assembled for a reviewer, a cleanup. File one item per such step, with the time and tokens it cost, into the next release with items left. Leave a step that needs judgement with the model. Run command-patterns 0.9.0 first; its table names the patterns, and read_threads and calls in bin/command_patterns/tally.py open the calls of one pattern, or command-patterns 0.9.0 --calls <file> dumps them all as JSON lines. The 0.7.0 audit found that most steps its chunks repeated were already scripted by that release's own tools, so a step a shipped item already covers is not filed.

The 0.8.0 audit filed four steps, items 334, 335, 336 and 337, and found most other repeated steps already covered by items 295, 312, 325, 326 and 327.

The chunk that ships this item files a copy of this audit in release 0.15.0, the release after this item's own, to audit releases 0.10.0 to 0.14.0, rewording "0.9.0" to them, and marks the copy owner, so the audit recurs each release until lilleman drops it.

288. Point the two reading-cost decisions at code health and goal 1.4's counter-signal, in place of the goal 1.1 they cite.

Both docs/decisions.md entries under reading cost: a rise is … and reading cost: larv-review measures each finished chunk … open "Serves goal 1.1: comprehension …". No goal says that any more: code health (CLAUDE.md → "Shared goal") holds comprehension, and since PR #455 a rising reading cost is goal 1.4's first counter-signal. Raised by the stability review of PR #455 as a 🟢 outside that change.

77. Teach bin/metric-bench Go and TypeScript, rerun it once two projects' comprehension histories name places, and bring into review only a metric that tracks the panel.

2026-10-08, lilleman: no metric enters review until a rerun on more data shows it tracking the panel.

Before the rerun, set the AUC and top-k lift over chance that count as tracking, from a published threshold, so the rerun ends in a decision. The rerun needs places from a project in Go or TypeScript, the languages most other projects use, so the bench first measures those languages, run through each project's own tooling. Function and file length stay warnings to look into, never limits: a plain long function can be simple, and a hard one may need five-line pieces.

On 2026-10-08 only this repo's history named places: five scoring runs, all that day. The medians:

Metric AUC Top k
Cognitive complexity 0.66 0.26
Length 0.74 0.18
Shared state constant constant
Change spread 0.67 0.18

AUC is 0.5 for a coin toss, and top k scores 0.10 by chance. Shared state cannot be judged here: every unit in bin/ scores 0 on it. Every run's first place was a section of skills/larv-review/SKILL.md, which no code metric sees.

On 2026-10-09 a question bench asked a headless claude, allowed only Read, Grep and Glob, three questions a script answers from the syntax tree: which units call a unit, which units it calls, and which test files refer to it. It asked them about every unit the history names whose name is unique, plus as many units the history does not name. Five of the history's six scoring runs named such a unit. The tool is in commit 083cc78; it was deleted after the run.

Claude's misses ranked the named units at a coin toss. Top k scores 0.50 by chance on these units:

Metric AUC Top k
Question misses 0.49 0.50
Cognitive complexity 0.66 0.59
Length 0.75 0.69
Change spread 0.57 0.54

Claude's answers overlapped the truth by a median Jaccard index of 0.76. A run took in 62,643 new input tokens and cost $0.70; it did not record which model answered. Grep answers these questions whatever the code's shape, so no question enters review; a new question bench would need questions that take understanding the code, not finding it.

196. Replay the architecture, principles, overrides and product-owner passes with review-replay on Opus 5.5 projects, record each run in the review-replay routing decision, and, where a run qualifies a rung, add back the code that lowers a pass to it.

Item 159's chunk, PR #322, replayed only the prose and stability passes. Sonnet 5.5 at high missed 44 to 55% of what the project's rung found again in each, so the agent judged a replay of the other four unlikely to qualify a rung. The product-owner review of PR #322 asked that the plan keep them, so the ranking decides when they run. Each run costs hours of reviewer replays (goal 1.4), so the score keeps it low until a cheaper model joins the ladder. docs/decisions.md → routing: a review pass runs below the project's rung only on a rung whose replay of its rounds finds a share of their 🔴 and 🟡 findings no more than a margin below the project's rung's own replay… records the runs so far. The release review of 0.6.0 deleted the code that lowered a pass, since no rung had qualified; the decision says where it goes back.

321. Evaluate the review passes that run on a rung review-replay qualified, against the chunks before them, and revert any pass whose findings or later fixes worsened.

The prose pass's replay under item 318's new bar, on 2026-11-12, qualified no rung, so this item waits for item 196's replays of the other passes. lilleman, 2026-11-11: that bar is a risk, so check it closely a release later. Compare the first 20 chunks reviewed on each newly qualified rung with the 20 before: review rounds past the first, 🔴 and 🟡 per chunk, misread findings, and later fixes that score-outcomes counts (defects that escaped review). Revert a pass to the project's rung where any of those worsened beyond the spread of the 20 before.

273. Re-tune the E + I steps of REVIEW_STEPS for 6 to 8 once 10 finished chunks have scored an E + I of 6 or more, from how well E + I orders their review rounds and 🔴 findings.

docs/decisions.md → routing: one ladder… records why lilleman kept the steps on 2026-11-08. Of the 36 chunks it measured, 1 scored an E + I of 6 or more and none 7 or more, so the steps for 6 to 8 are untested. Start once score-outcomes shows 10 finished chunks with an E + I of 6 or more. Then read its rank correlation for E + I, and the routed-chunks table of routing-figures.md in loop-claude's archive ($LOOP_CLAUDE_TRANSCRIPTS, default ~/.claude/loop-claude-transcripts). Propose new steps to lilleman, whose call they are.

268. End a run whose release is ready to cut with a notice on loop-claude's terminal, in place of an interrupt that waits for an answer.

On 2026-11-08 the human answered notice only: the loop prints that the release is ready to cut and ends; no interrupt, and nothing waits in loop-inbox.

Releases are the human's, and CLAUDE.md → "Working loop" already ends the loop once a release is ready to cut, so the ask settles nothing. 15 interrupts in the archive ask whether the human will cut a release, and about 6 of the 45 interrupts from 2026-11-02 to 2026-11-10 said a release was ready to cut; log's 2.5.0 was asked twice within an hour on 2026-11-10. On 2026-11-08 one of the 4 questions waiting in ~/.local/state/loop-claude/ is such an ask, plainpages-plugin-fastjira's 0.3.0 since 2026-11-03. Today a release ready to cut opens claude's session at once (bin/loop_claude/cycle/run.py ask), and the loop stops if the human leaves it with nothing typed. The change also touches what an interrupt covers in CLAUDE.md → "Vocabulary". Where the change touches ask, make it easier to read, as the seats named it.

171. Group the routing figures' review rounds by the reviewers' rung as well as the worker's, so a call blames a rung only for rounds its own reviews raised.

Raised by the goals audit of PR #296. bin/routing_figures/calls.py groups a chunk's review rounds by the rung its worker started on, and calls for a routing change when a lower rung took more of them. Since PR #296 the reviewers may run above the worker's rung, on the one their item's E + I picks, and no figure groups rounds by it, though the archived worker line names the E + I it follows from. A cheap worker on an item of high E + I gets stronger reviewers, who may raise more rounds, and a call could then blame the worker's rung for them: an interrupt of lilleman that settles nothing (goal 1.2).

300. Reach the comprehension floor: restructure the places the comprehension seats found hardest to follow, so the project reads at 7.0 or above on every dimension, Locality and Self-sufficiency first; today the scoring run at 8f03747 scored Navigation 6.75, Locality 5.63, Shape 5.75, Self-sufficiency 5.63 and Overall 6.00.

Filed by the comprehension check of PR #473 at 13d1550 (larv-review record-scoring), which printed Floor: and Next:, and refreshed from the second run of PR #520 at 8f03747. The lowest means are Locality and Self-sufficiency, 5.63 each: the seats name state shared across modules, such as the route and the archive order, and reasons that sit in docs/decisions.md, CLAUDE.md or skills/larv-review/SKILL.md rather than beside the code. Refresh this item's places and aim from the newest run before the chunk starts; do not file a second floor item.

Aim: one ambitious refactor of the areas below, sized so every mean reaches 7.0 on the chunk's own scoring run. Where a place is already easier to read when the chunk starts, drop it.

Places the seats named, hardest first (larv-review places):

  • Locality, Self-sufficiency: bin/loop_claude/routing.py:93 unfinished_route, with escalated_route: the floor, the cap counted from item_rung, the escalation mark, the unfinished count and the E + I taken in are held at once across four files, and why they combine sits in the decision log. Every seat named it; three would least want to change it.
  • Shape, Self-sufficiency: bin/release_plan/release_standing.py:168 next_release, with standing: str | None | Failure fields in LastCut, the BEFORE_FIRST_RELEASE sentinel and nothing_cut meet in the is_earliest test, read as truth tables; four tools choose the next release through it.
  • Locality: bin/loop_claude/cycle/run.py:154 rule, with :67 run_cycle and :94 archived: archives twice in an order that matters and that nothing enforces, the archive helpers sit in the cycle runner though loop/close.py imports them, and run_cycle replaces cycle.route outside the state machine.
  • Shape: bin/release_plan/ranking.py:56 rank, :160 weigh, :304 score and :315 weight_of: every function forks on SHAPE versus OLD_SHAPE, and the constants' reasons are only "docs/decisions.md records the choice".
  • Shape: bin/rule_hook/todo_check.py:22 todo_breaches, with :42 folder_breaches: three paths, held() beside located(), the checkout's own script only under same_repo, and a blob hashed by hand.
  • Locality, Self-sufficiency: bin/larv_review/plan.py:66 plan_reasons and bin/larv_review/owed.py:46 shortfall: the rule for when a scoring run is due is split between the 155-line help and the code, and the number owed hangs on the wording EMPTIED_WORDS.
  • Self-sufficiency: bin/loop_claude/cycle/judge.py:21 INTERRUPT_RULES, with :196 quotes_checked: behaviour held in prompt text and schema descriptions the code can't explain, and prompts that quote CLAUDE.md wording.
  • Self-sufficiency: skills/larv-review/SKILL.md:82 "Round cap": dense rules that point at CLAUDE.md, review-findings.md and the rules files, read three times before the code matched.
  • Self-sufficiency: bin/rule_hook/round_cap.py:26 earlier_titles: fails open on the unattended path where git cannot list the branch's titles, and the cap's wording is spelt in SKILL.md, rules.py:61 and round_titles.py.
  • Locality, Shape: bin/chunk_preflight/choices.py:80 forge_of: forge identity and forge calls live in two tool packages, so a second forge lands in three.
  • Navigation, Shape: README.md:131 bin/: about 63 entries at one level, the shared libraries told apart only by README prose.
  • Navigation: bin/text_files/__init__.py:1 records: utility code named like the judge's records, and quote semantics in claude_code/transcript.py:85 verbatim.
  • Shape: bin/rule_hook/committed_files.py:14 committed_file_breaches: a double-reverse dedupe whose choice of copy no comment explains.
  • Shape: bin/model_routing/route.py:28 levels_fit, with route_of: two rules in one boolean, and type checks packed into one long line.
  • Shape: bin/loop_claude/loop/reload.py:220 decoded_route: one dense guard, and renaming a LoopRun field stops a running loop.
  • Shape: bin/rule_hook/main.py:116 bash_breaches: a 200-character return line joining four kinds of breach.
  • Shape: README.md:3 trial folders: four finished experiments at the root beside the working areas.
  • Self-sufficiency: the seats on this run name the decision-log titles that code cites for a constant's reason (routing: … in routing.py, ladder.py, judge.py) as the largest cost; state each reason beside its constant.

Scored L 4 because the refactor touches several components that hold known defects, E 2 because review and a manual check see a regression, I 3 because every session runs these tools. The chunk runs a scoring run, since it is a floor item.

264. Report the comprehension seats and the escalated subagents as subagent types of their own in routing-figures.md, with their dollars.

Seats launch as general-purpose, so they hide inside that type: $301.24 of the $962.17 the figures of 2026-11-04 count, from 221 subagents. By 2026-11-10 general-purpose was the second-largest spend, $585 of about $2,385, and by transcript size about two thirds of it were seats (291 launches), then 177 security passes. Escalations are counted by trigger only, never in dollars. bin/routing_figures/chunk.py groups subagents by their subagent_type; a seat is told apart by its prompt, and an escalated subagent by the escalation marker its prompt opens with.

323. Count a release review as landed once its pull request has merged, whatever its commits are titled.

release_reviewed in bin/release_plan/release_standing.py counts a release review only by a commit titled Release review of <release> on the default branch. In a replay of archived interrupts (judge-field-trials/), in two projects whose release review had merged, the default branch held no such commit, so chunk-preflight and routing read ReviewDue, and the next loop would run the release review again. skills/larv-review/SKILL.md opens the review's branch with an empty commit of that title, but a worker may skip it, and a rebase or squash merge, which chunk-pr uses where the forge allows no merge commit, may drop it. Detect the review by something every merge method keeps, and check the fix against both projects' histories. Until then the judge keeps release_ready (docs/decisions.md → routing: loop-claude reads the items a chunk takes …).

342. Research the tooling agents read, search and run commands with once more, and file an item for each tool that cuts tokens a replay shows keep quality.

The next round of item 312's research, filed when 312's round ran on 2026-11-12. lilleman, 2026-11-11: repeat the round once per claude-config release, not per project. When this item's chunk finishes, file the next round into the next claude-config release with items left.

Run it as 312's ran: a lead on the project's rung plans 6 to 10 searches where the archive's spend is, cheaper subagents with web access only return sourced findings, and the lead checks each claim against the archive's measured spend before filing.

Sources that proved useful in 312's round: Claude Code's environment variable reference (https://code.claude.com/docs/en/env-vars), its subagent reference (https://code.claude.com/docs/en/sub-agents), its CHANGELOG (https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md), the API's context editing and tool search pages (https://platform.claude.com/docs/en/build-with-claude/context-editing, https://platform.claude.com/docs/en/agents-and-tools/tool-search-tool), and Anthropic's post on code execution with MCP (https://www.anthropic.com/engineering/code-execution-with-mcp). Check a variable a source names with a grep of the installed Claude Code binary; issue mirrors and blogs gave leads but no figure to rely on. The archive counts that decided: command-patterns <version> --calls, and scripts in /tmp over loop-claude's archive summing tool results by agent type, cache writes by lifetime and request gaps, and each subagent's first request.

Dropped in 312's round, and why; look again only where the reason has changed:

  • Editing through Edit in place of python3 heredocs: Edit already accepts a file read with sed or cat on Claude Code 2.1.319 to 2.1.322, 27 such Edits in 0.7.0 and 0.8.0 and no "not read yet" refusal in the archive, and an Edit would have saved about 2,300 command tokens per chunk.
  • Forcing 5-minute caches on the worker or 1-hour ones on subagents (FORCE_PROMPT_CACHING_5M, ENABLE_PROMPT_CACHING_1H): over 53 chunks, the worker's 1-hour writes cost $217 at list prices against $233 for 5-minute ones, and subagents' 5-minute writes cost $226 against $289 for 1-hour ones.
  • A security-pass agent type with fewer tools: its 49 runs started at a median 30k tokens and cost $14 in all.
  • Deferred tool loading: already on, since ENABLE_TOOL_SEARCH defaults on and saves MCP tool definitions only.
  • Context editing and programmatic tool calling: API features that Claude Code doesn't expose as a setting.
  • LSP, repo maps and outline scripts: item 231's trial lost findings and agents didn't call them; the only figures found since are a vendor's and a blog's.
  • Compact test reporters and output filters such as rtk: this archive's test output is a few thousand tokens per release, and the filters' figures are their own; trimming read output is item 311's ceiling.

149. Fill each release by priority up to a capacity it states, in place of the bar, and move what does not fit to a later release.

A release's capacity is a sum of its items' cost, as the formula counts it. Each project states its own; the human sets the first value per project. Nothing is deleted by score.

165. Make this repo's tests assert the facts a prompt or help text carries in place of its sentences, and drop the tests that scan source or assert a constant.

A test audit across lilleman's projects on 2026-10-16 found 10 of 33 sampled tests in this repo pinning wording that is not the contract. Examples of these and other weak tests: many tests in bin/loop_claude/test_loop_claude.py pin whole sentences of the question, archive, prompt or help text, up to about 750 characters. test_every_exit_1_stop_has_its_clause_in_help and test_every_failed_judge_run_has_its_clause_in_help parse the source with ast and list each Stop(...) and Failure(...) call by function name. bin/model_routing/test_ladder.py asserts len(LADDER) == 6. Rewrite each to the technical principles' test bullet: assert the facts the text must carry, such as an item ID, a rung or a model argument, and delete a test no real bug could fail. Before and after rewriting a test, run the mutation tool on the code it covers: every mutant the old test killed, the new one kills.

151. Keep 10 to 20 settled decisions per project as its goals' test set, and rerun them after a goal changes.

Each case is a question the project settled and the answer it chose. A fresh-context agent given only the README's premises answers each case; a case it answers differently says the goals no longer decide it. Written guidance can fail to change behaviour, which is why the goals get a test.

68. Test workflow-bench/compare.py's blinding and bench.py's run plan.

"Most, if not all, code should have automated tests", in principles/technical-principles.md: compare.blind() keeps the comparison blind, and a version name it misses invalidates the bench silently.

The tests also cover workflow-bench/bench.py's permission_flags, with a probe of a headless claude given its flags. It is denied a read outside the granted trees, a bare git status, and wrapper calls with --output, --no-index, a glued -aF/abs, --fil=/abs or a path outside the clone. A cd <elsewhere> && python3 <wrapper> … acts on the clone only. It is allowed the wrapper's log, diff, show, status, ls-files, add and commit -m. workflow-bench/test_review_git.py tests the wrapper's refusals directly.

102. Give loop-claude's retry delay, and the file it reads the machine's memory from, environment overrides, so the black-box test stops replacing time.sleep and machine_load.memory.MEMINFO through sitecustomize.

Found by the principles audit of PR #242. The SITECUSTOMIZE block in bin/loop_claude/test_black_box.py swaps the global time.sleep, the shape "Functional core, imperative shell" bans, and the audit of PR #376 found the same block swapping machine_load.memory.MEMINFO, the constant in bin/machine_load/memory.py. An override of each lets the test run the code as production runs it.

135. Fingerprint only the modules loop-claude imports, so editing another tool's code no longer reloads a running loop.

The maintainability senior and the inherited architect of PR #257's scoring run named fingerprint and exec_if_edited in bin/loop_claude/loop/reload.py: the fingerprint covers every bin/**/*.py, so editing statusline.py or rank_todo.py re-execs a running loop. Make fingerprint easier to read.

5. Key a project on its checkout's full path, and refuse to start while another session uses that key.

The key names the project's session, archive folder and models entry. project_key, in bin/transcript_archive/project_key.py, strips ~/code/ and then any leading /, so ~/code/a and /a share all three, and one loop can resume or delete the other's session.

bin/reading-cost keys the archive by the main checkout, the parent of git's common dir, since it runs in a chunk's worktree; loop-claude keys it by --show-toplevel, so a loop started inside a worktree archives where reading-cost never looks. Derive both keys one way.

291. Let principles/technical-principles.md → "Sane defaults" allow a library whose README goals ask that it work with no config to default the clock and randomness in its public constructor, where a documented option overrides each.

"Sane defaults" has a library ask for every input that can change between runs, the clock and randomness included, and leaves defaulting them to the code that wires a program together. A logging library's principles audit found that its constructor defaults both, as its first goal, useful with no config, asks. Its decision log records the defaults as a departure from the principle, and names this item as what ends it. Until then, each principles audit there may raise the defaults again.

2026-11-10, the human: keep the library's defaults, and give the principle an exception for this case, worded about as the tagline says. The exception has to square with "Functional core, imperative shell", which the same bullet cites and no other principle overrides.

156. Drop rank_todo.py's ranking of an old-shape table once no project under ~/code holds one.

While rank_todo.py ranks two shapes, projects follow two sets of scoring rules, against goal 1.3. Once every project has reshaped, drop OLD_SHAPE's weighing from bin/release_plan/ranking.py, RESHAPE, and the old shape's lines in rank_todo.py --help and rules/todo-items.md. Keep todo_table reading old tables: score_outcomes reads every past merge's todo.md. PR #283's paired ruling found the old-shape path made ranking.py's score, Scoring.weights, unknown_columns and todo_table.py's Moves harder to read; leave each easier, with one shape and moves that are always moves, and the Moves cell's rules in one place. Release 0.3.0's seats named ranking.py's score, weigh and rank and todo_table.py's OLD_SHAPE for the same fork: "every rule exists twice for the old table shape" (Mid A). Make weigh and rank easier to read too.

260. Compare the first 20 chunks whose worker got the reading rule with the 20 before them, on review rounds past each pass's first, unfinished verdicts, 🔴, 🟡 and misread findings, dollars and hours per chunk, and drop the rule where any rose.

Start once 20 chunks have run under the rule. The rule is READING_RULE in bin/loop_claude/cycle/prompts.py, which every fresh worker prompt holds; git log --first-parent -S READING_RULE on the default branch finds the merge that added it. A chunk got it when its first worker started after that merge. Measure as docs/decisions.md → loop-claude: the worker's claude compacts its context before it fills a 200k window… measured the window: rounds past each pass's first and the 🔴, 🟡 and misread counts from the round commit titles, unfinished verdicts from the outcomes files, hours from the worker's first message to its last, and dollars from the chunk's cost-state entry. Compare means, since the decision weighs the rule by all spend.

51. Hand loop-claude's terminal output to an injected effect, so no storage or retry function prints.

"Functional core, imperative shell", in principles/technical-principles.md: say and input_or in bin/loop_effects/effects.py take the effects but print to stderr or stdout themselves, and retried and the rest print through say. Two bare print(file=sys.stderr) calls remain outside them, in bin/loop_claude/cycle/interrupt.py and bin/loop_claude/project/model_choice.py. The tests swap the global stream.

201. Save the human's tmux setups and restore them after a reboot, so work is up and running again quickly.

The human asked on 2026-10-21 for tmux support, above all for saving tmux setups. Don't build anything until the human has said exactly what they need. Ask them at least:

  • What a setup holds, such as sessions, windows, panes, each pane's working directory and the command running in it, like one loop-claude per project.
  • When a setup is saved: on demand or on its own.
  • How a setup comes back after a reboot.
  • Whether the code that saves and restores setups must work on every machine that takes this checkout (goal 2), which decides whether that code lives in this repo.
  • What else tmux support should cover.

Weigh the widely used tmux-resurrect and tmux-continuum plugins against a script of our own. Then re-score this item from the answers and that choice, and split it into items where it is more than one chunk.

267. Keep waiting when an interrupt gets an empty answer, at the terminal or in the claude opened for it, in place of stopping the loop.

11 runs in the archive ended with "Stopped: the human is needed to answer the question above, but the interrupt ended without anything typed", each leaving its chunk open until the human restarted the loop. That stop comes from human_typed in bin/loop_claude/cycle/interrupt.py, after the claude opened for /talk or for a release ready to cut ends with no human turn. An empty line at the terminal stops the loop the same way, in first_answer. Item 268 removes one of the cases that opens claude.

4. Name each chunk's archive folder by the chunk's start time, so <key>/ lists chunks in the order they ran.

Today the folder is the SHA-256 of the transcript's first timestamped line, which tells the human nothing; that line carries the start time. Drop the fallback to the first line, which every chunk of a project shares, and give the tests' fake transcripts ISO timestamps. bin/reading-cost takes a chunk's id from the folder's first 12 characters and skips a chunk whose id docs/reading-cost.md holds, so give it a way to match a figure written under the old name.

324. Count in the routing figures the finished chunks whose worker wrote no Chunk items: line.

docs/decisions.md → routing: loop-claude reads the items a chunk takes … holds only while workers write the line when asked, and nothing counts a chunk whose worker skipped it. There loop-claude scores no item beyond the one the chunk was routed on, so the route holds, and loop-inbox lists only that item. Count in bin/routing_figures/, beside the chunks counted, those whose worker's transcript holds no such line, so the human sees when the decision's premise stops holding.

187. Count the tokens a worker spends reading reviewers' reports, so goal 1.4's signal shows whether report files lowered what a review costs the worker's context.

Before PR #310, reports reached the worker as the Agent call's result, a median 19k tokens per chunk (2026-10-08, 68 archived transcripts). Now a reviewer returns its verdict and one line per finding, and the worker reads a 🔴 or 🟡 finding's entry from the report file. reading-cost counts only tracked files (bin/reading_cost/measure.py), and routing-figures counts only the Agent call's result (bin/routing_figures/chunk.py), so neither sees the report reads. Found by the architecture review of PR #310.

266. Move the chunks archived under the key home/lilleman/.claude to the key claude-config, so the routing figures and score-outcomes count this repo's chunks as one project.

The archive holds 277 chunk folders under home/lilleman/.claude, from 2026-09-24 on, and 39 under claude-config (2026-11-10). The routing figures of 2026-11-04 list no project home/lilleman/.claude. They find a chunk's later fixes on the default branch of the checkout its key names (bin/routing_figures/archive.py measure_project), and /home/lilleman/.claude is a release checkout on a detached HEAD. Item 5 fixes how keys are derived, not the chunks already archived. ~/.claude/loop-claude-models.json still holds a home/lilleman/.claude entry; it is machine state outside the repo, so removing it is a one-off step on each machine, not part of the change.

181. Have the test of a quoted answer's step-up assert the stepped rung's facts as literals, not through prompts.rungs_held.

bin/loop_claude/test_loop_claude.py's test_a_quoted_answer_that_cites_an_escalation_trigger_steps_the_worker_up_before_it_resumes_and_archives_the_step builds its expected prompt from prompts.rungs_held, the code under test, so a bug there passes it. The technical principles' test bullet bans that shape. Assert the new rung and one review launch as literals, as the typed answer's step-up test does. Raised by the principles audit of PR #308.

193. Narrow readme_goals's mark to Mark by a typed lookup in place of typing.cast, so a mark added to the regex but not the lookup fails at run time, and one added to the lookup but not Mark fails mypy.

Found by review of PR #317. bin/release_plan/ranking.py's readme_goals writes typing.cast(Mark, mark or None), which asserts the type goal_weights branches on without checking it: a mark added to the regex reaches goal_weights as a value Mark lacks. mypy does not read the regex, so no lookup lets it catch that. Replace the cast with a lookup typed dict[str, Mark], from each mark the regex captures, and "" for none, to its Mark value. A mark added to the regex but not the lookup then raises KeyError at run time, and a value added to the lookup but not Mark fails mypy.

194. Make test_waits_out_a_usage_limit_which_ends_a_run_of_failures expect a usage-limit wait independent of the wall-clock time that passes during the run.

Found by review of PR #317. The black-box test, bin/loop_claude/test_black_box.py:609, not the unit test of the same name in test_loop_claude.py, which runs on a fake clock, sets resets_at from the test's time.time() and expects the wait, rounded to tens, to be 3720. When more than about 5 s pass between that read and the loop's, the wait rounds to 3710 and the test fails with no bug. Item 102 covers only replacing the time.sleep swap; this item changes the expected value, for example by asserting the wait against resets_at + 120 minus the time the loop read, or a bound on it.

265. Archive each wait that costs a chunk wall time, for a usage limit, low memory, a failed worker start or a heavy slot, with its start and end stamps, so goal 1.5's hours split waiting from work.

No record holds these waits today. An outcomes file holds verdicts, stops, step-ups and the judge's cost (bin/transcript_archive/outcomes.py), and ~/.local/state/run-heavy/ holds only the slots' lock files. loop-claude waits out a usage limit and low memory in bin/loop_claude/cycle/retry.py; run-heavy waits for a slot in bin/run_heavy/. A heavy slot's wait happens inside a worker's Bash call, so loop-claude doesn't see it; run-heavy would write it where the archive can find it.

169. Have rule-hook's todo-rank-check catch a todo.md that the same Bash call edits and then commits.

The hook judges a call before it runs, and changed in bin/rule_hook/todo_check.py compares todo.md with the index and HEAD as they stand then. A call that edits todo.md and commits it, such as a heredoc script followed by git commit, passes unchecked: PR #296's commit 149108e did, and the override marker it carried was never logged. larv-review's gate still runs rank_todo.py --check, so an unranked plan stops at merge rather than at commit. A git pre-commit hook would see the staged file.

197. Let the human edit what they type at loop-claude's terminal questions with the arrow keys, so Left moves the cursor in place of printing ^[[D.

bin/loop_effects/effects.py hands loop-claude Python's builtin input, and nothing under bin/ imports readline, so the terminal gets no line editing: fixing a typo means erasing back to it. loop-claude asks two questions at its terminal. effects.input reads the pick of the project's model, in project/model_choice.py's ask_for_model. effects.input_or reads the interrupt's answer, in cycle/interrupt.py's first_answer, straight from stdin, since it also watches loop-inbox. Importing readline in effects.py gives input line editing, at two costs; input_or would also need to read through input while it watches. It moves the prompt from stderr to stdout, while the question above it stays on stderr. test_black_box.py waits for the prompt on stderr. readline's bracketed paste takes a pasted block whole, so an answer can hold several lines. prompts.typed_answer ends the answer at its first blank line, so the judge would read the rest of such a paste as loop-claude's words. The product-owner review of PR #308 raised the interrupt's case. lilleman, 2026-10-18: "Not super-important, but a bit irritating."

1. Say in README → Install how the transcript archive is backed up, once bender-infra backs up ai-sandbox's data volume.

It lives under ~/.claude, which .gitignore keeps from the remote, so a lost disk loses every unattended run's record. Back it up only to a destination private to me and encrypted at rest: the worker runs with permissions bypassed, so the archived tool results can hold credentials it read.

2026-10-02, the human: ai-sandbox is the VM loop-claude will run on, hosted on the server bender. bender-infra, the infrastructure-as-code project that manages bender, will back up ai-sandbox's data volume once ai-sandbox is rebuilt. The item waits for the human to say the rebuild has landed; do not remind them. Before writing the README line, check that ~/.claude lives on that volume and that the backup is private and encrypted at rest.

The README line covers the bench's transcripts in workflow-bench/logs/ too (goal 3).