Read the routing ladder from routing-ladder.json, which a project may replace with a file of its own #553

Merged
lilleman merged 12 commits from patch-0.10.1 into main 2026-11-15 20:00:45 +01:00
Owner

The routing ladder moves from a constant in code to bin/model_routing/routing-ladder.json. A project that keeps a routing-ladder.json in its config's folder, ~/.claude-projects/<key>/, runs on that ladder instead, and each cycle of such a project says so.

The branch was cut from v0.10.0 and is tagged v0.10.1 at daaa61b. This pull request merges that tagged commit into main with a merge commit, so that the tag stays in main's history and deploy-release can move on to 0.11.0.

Two places the comprehension seats found hard are touched and no easier to read: unfinished_route in bin/loop_claude/routing.py takes ladder as one more argument, and Cycle in bin/loop_claude/cycle/run.py holds one more field. Binding a project's rung to its ladder in one value would undo both. It changes the type of project across loop-claude, rule-hook and the replay tools, which is too wide for a patch cut during an outage, so it is filed as item 387.

Rule overrides, both ruled accepted by the overrides pass:

  • todo-rank-check, on the merge of main into the branch and on the commit that files items 387 and 388. Reason: the checkout's rank_todo.py needs the config's standards setting, which CHANGELOG.md says to add only once ~/.claude moves to the next release; ~/.claude/bin/rank_todo.py --check todo.md exits 0.
The routing ladder moves from a constant in code to `bin/model_routing/routing-ladder.json`. A project that keeps a `routing-ladder.json` in its config's folder, `~/.claude-projects/<key>/`, runs on that ladder instead, and each cycle of such a project says so. The branch was cut from v0.10.0 and is tagged v0.10.1 at daaa61b. This pull request merges that tagged commit into main with a merge commit, so that the tag stays in main's history and `deploy-release` can move on to 0.11.0. Two places the comprehension seats found hard are touched and no easier to read: `unfinished_route` in `bin/loop_claude/routing.py` takes `ladder` as one more argument, and `Cycle` in `bin/loop_claude/cycle/run.py` holds one more field. Binding a project's rung to its ladder in one value would undo both. It changes the type of `project` across loop-claude, rule-hook and the replay tools, which is too wide for a patch cut during an outage, so it is filed as item 387. Rule overrides, both ruled accepted by the overrides pass: - `todo-rank-check`, on the merge of main into the branch and on the commit that files items 387 and 388. Reason: the checkout's `rank_todo.py` needs the config's `standards` setting, which `CHANGELOG.md` says to add only once `~/.claude` moves to the next release; `~/.claude/bin/rank_todo.py --check todo.md` exits 0.
lilleman added 1 commit 2026-11-15 18:52:08 +01:00
lilleman added 3 commits 2026-11-15 19:13:43 +01:00
lilleman added 3 commits 2026-11-15 19:42:58 +01:00
lilleman added 2 commits 2026-11-15 19:48:21 +01:00
lilleman added 2 commits 2026-11-15 19:55:38 +01:00
# Conflicts:
#	CHANGELOG.md
#	README.md
#	bin/loop_claude/loop/chunk_start.py
#	bin/loop_claude/loop/close.py
#	bin/loop_claude/loop/main.py
#	bin/loop_claude/routing.py
#	bin/loop_claude/test_loop_claude.py
#	bin/project_config/main.py
#	bin/project_config/test_project_config.py
#	docs/decisions.md
lilleman added 1 commit 2026-11-15 19:57:25 +01:00
lilleman changed title from WIP: Read the routing ladder from routing-ladder.json, which a project replaces with a file of its own to Read the routing ladder from routing-ladder.json, which a project may replace with a file of its own 2026-11-15 19:57:39 +01:00
lilleman merged commit bf1897b1a0 into main 2026-11-15 20:00:45 +01:00
Sign in to join this conversation.
No Reviewers
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: lilleman/claude-config#553