0010 — The code ladder is 0, 1, 3; level 3 is trunk flow by itself

Status: accepted (amends 0006 on the ladder's levels; maturity.code alone picking the process stands) Date: 2026-11-15 Story: stories/041-maturity-code-3-is-accepted-and-means-trunk-flow.md

Context

ADR 0006 made the ladder trunk, batch, gated (0, 1, 2). The manual has since retired level 2, which was never built and which no project declared, and specified level 3, agent flow: level 1 with agents doing the work between a defined story and its landing. It is trunk flow underneath. Level 1 meanwhile has two processes, the batch and trunk flow, chosen by the temporary maturity.flow (0008) until #199 removes the batch.

So two things had to be settled before anything of agent flow could be built behind the declaration: what a declared 2 means now, and which of level 1's two processes level 3 stands on.

Options

What maturity.code: 3 releases with:

Option Complexity Testability Domain clarity Operational risk
A. As level 1: the batch unless maturity.flow: trunk none as today level 3 over a batch is a state the manual does not have agent flow built twice, or a config that loads and cannot work
B. maturity.flow: trunk required at 3; an error without it one more config error one row the level needs a second key that #199 then removes from every level 3 project a migration when #199 lands
C. 3 means trunk flow; the key is not read, and trunk is accepted one predicate one row the level alone picks the process again, as 0006 intended none: flow: trunk left in place is harmless

What maturity.code: 2 does:

Option Complexity Testability Domain clarity Operational risk
D. Read as 1, with a warning from tp check a second meaning for a number two rows a level that is declared and does not exist a warning nobody reads
E. A config error naming 1 and 3 one check in the loader one row the ladder in tp is the manual's a project declaring 2 stops until it edits one line; none does

Decision

C and E. maturity.code is 0, 1 or 3. At 3 stories land with tp story land and the release is made on the base branch, whatever maturity.flow says; reports give the mode as trunk flow (maturity.code 3). A declared 2, and any other value off the ladder, fails the load of task-plus.yml, so every command refuses it, and tp maturity code 2 is refused before the forge is asked. tp maturity code 3 asks of the forge what code 1 does: the base branch protected, merge commits the default, the repository at rest.

Consequences

Easier: agent flow is built on one process. A project moving from 1 to 3 changes one number; #199 has nothing to migrate at level 3.

Harder: the levels are no longer consecutive, so "level N and up" in code and docs has to say which levels it means. Moving from level 1 under trunk flow to 3 is still a change of level and still needs the repository at rest (story 029), though the release process is the same.

CI on pull requests (#51) is closed, not renumbered: the manual leaves it to the forge at any level.