The board's Now row shows one lane and one awaited role per run; the implement chapter runs a run's lanes in parallel up to its ceiling.

The board's Now row shows one lane and one awaited role per run; the implement chapter runs a run's lanes in parallel up to its ceiling.

A premise contradiction (severity minor) found by the cross-document consistency pass.

• End A: .abcd/development/brief/04-surfaces/08-abcd.md:325 — "a run in progress, with the lane the loop works on, its next stage and the role it waits on"
• End B: .abcd/development/brief/04-surfaces/27-implement.md:386 — "A run works in parallel up to its ceiling (ruling DR6)"

08-abcd's status block lists each intent in a lane as a run in progress, with the lane the loop works on, its next stage and the role it waits on, and its JSON carries a single lane object. 27-implement says a run works in parallel up to its ceiling: a stage moves on any lane, several lanes can each await agents, and the status render names every lane alive with each agent it awaits. A run with several lanes alive has no single lane the loop works on. The board's row shape assumes the one-lane-at-a-time loop that the implement chapter replaced.

Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 413.

Grounds

• declined: Closed in the 2026-10-27 triage (dcn-2610271112330536): the two ends do not conflict when read in full. internal/core/statusblock/statusblock.go reports every lane of a run as its own Now row (Started.Lanes, ruling DR6), so the board already handles the parallel loop; only the chapter's singular phrasing is loose.