roadmap: lanes added to Tier 1

ROADMAP.md

@@ -1,6 +1,6 @@
 # ck: Product Roadmap
 
-> Maintained by [claude-roadmap-skill](https://github.com/code-katz/claude-roadmap-skill). Last updated: 2026-10-26.
+> Maintained by [claude-roadmap-skill](https://github.com/code-katz/claude-roadmap-skill). Last updated: 2026-10-27.
 
 ---
 
@@ -58,7 +58,7 @@ Carried forward from the roadmap's revision 3 (2026-10-26). ck2 is abandoned: a
 | 1 | **A team per project** | `.claude/ck-team.conf` invites or drops personas; `/ck:team` shows and changes it; every session is told who is on the team | Built | Not planned |
 | 2 | **`/ck:proof`** | Any file, or a document written from a request, becomes a page you comment on until approved; with the proof loop rules and one document contract for a proposal, an analysis, or a note | Built | Removed: 0.1.13 already makes a proof page for any document |
 | 3 | **Ask the owner first** | Before a judgment question reaches you, the stage's owning persona answers it on its own model, and the session asks with "<Owner> recommends" | Built | Not planned: a stage session already runs as its owner, on the owner's model |
-| 4 | **Lanes for `/ck:do`** | A small task runs in background lanes (builder, checker, reducer, researcher, scout, writer) on its own branch, with a limit on the size of the change | Built | Not planned |
+| 4 | **Lanes for `/ck:do`** | A small task runs in background lanes (builder, checker, reducer, researcher, scout, writer) on its own branch, with a limit on the size of the change | Built | Planned: Tier 1 item 4, for plan stages as well as `/ck:do`, with the model set by the task |
 | 5 | **`/ck:start` as a phase coordinator** | One session per phase: a card per ready stage, or auto mode for the whole phase, and a hand-over at the phase's end; `plan.py` prints the board, ready stages, and cards | Built | Partly: 0.1.17 puts up a chip per ready stage; no auto mode or phase hand-over |
 | 6 | **`/ck:lean`** | Asks whether a branch's code is as little as it needs to be | Built | Not planned; a one-off lean review was done instead ([ck: is it lean?](https://claude.ai/artifact/PKCgiGsjZroKmLVXXEjuuB)) |
 | 7 | **The cost script** | `cost.py` prices a piece of work from session transcripts, by stage, phase, agent, and model | Built | Planned: 0.1.19, `/ck:cost`, rebuilt small |
@@ -86,6 +86,7 @@ Dropped with ck2: its 0.2.0 release plan, which would have replaced ck in the `c
 | 1 | **Try the memory gate in d20mob** | It is released and on stable, but not yet tried by hand | A save shows the proposal ending "Reply 1, 2 or 3", then the approval prompt |
 | 2 | **0.1.18: `/ck:do`** | It reads 2,737 words every time it is typed; whether to shorten it or remove it is being decided | The decision made, and the release on ck-next |
 | 3 | **0.1.19: a small cost script** | Shows what work costs by session, persona and model, so a release's saving can be measured | `/ck:cost` prints d20mob's last 7 days |
+| 4 | **Lanes: the model follows the task, not the persona** | A stage runs on its owner's tier, so Akira writes on Fable whether the job is a design call or a small edit, and each d20mob plan row needs a ruling to say otherwise. The V2 proposal (2026-10-13) designed lanes and ck2 built them (ck2 features, row 4); they are rebuilt from scratch | A plan's Who column names no model; in d20mob a stage runs its scout, builder and checker on the models one config file gives each lane, and its author on a model chosen for the job, with no per-row ruling |
 
 ### Tier 2: High Value, Plan for Next Sprint
 
@@ -107,6 +108,7 @@ Dropped with ck2: its 0.2.0 release plan, which would have replaced ck in the `c
 ```
 Now:   try the memory gate in d20mob
 Next:  0.1.18 (/ck:do) -> 0.1.19 (cost script) -> ck-next -> test -> stable
+Then:  lanes -> ck-next -> a d20mob phase -> stable
 Later: the lean review's recommendations
 ```
 
@@ -116,6 +118,7 @@ Later: the lean review's recommendations
 
 1. Is the install drill on Clare's machine still wanted?
 2. What happens to the ck2 repository: archive it on GitHub, or leave it as it is?
+3. Is effort set per lane as well as the model, and where is it set?
 
 ---
 
@@ -132,6 +135,23 @@ Later: the lean review's recommendations
 
 ## Revision History
 
+## [2026-10-27] Lanes added to Tier 1
+
+**Change Type:** `add`
+**Triggered by:** `planning-session`
+**Items Affected:** Tier 1 item 4; ck2 features, row 4; Recommended Sequencing; Open Questions
+
+### What Changed
+Lanes are Tier 1 item 4, and row 4 of the ck2 features table moves from not planned to planned. A lane is a kind of task (scout, author, builder, writer, reducer, checker, coordinator) with its model, effort and tools set once in one file; a persona only judges and authors. The plan contract stops naming a model, and the author's model is chosen for the job rather than taken from the persona's tier. Lanes cover plan stages as well as `/ck:do`. The sequencing gains a Then line after 0.1.19, and Open Questions gains question 3.
+
+### Why
+You decided that a model should suit the task, not the persona. Released ck still sets it by persona (`skills/plan-artifact/SKILL.md`, the Who rule), which is why each d20mob plan row carries a hand ruling. ck2 built lanes, though its author lane still ran on the persona's tier.
+
+### Open Questions Resolved / Added
+- Added: is effort set per lane as well as the model, and where is it set?
+
+---
+
 ## [2026-10-27] ck2's features listed, with where each stands
 
 **Change Type:** `add`