The readiness planner orders the statements a person can make

actor

The owner of a corpus, or an agent preparing the owner's review, with more waiting statements than a session can make.

problem

No page orders the statements a person may make, so the owner either states rungs in an order that has to be undone or rebuilds the dependency order by hand with promotion preflight and dependency footing.

outcome

Order the Specs whose floor allows a higher rung than their author stated, the Specs they rest on first, so a person makes those statements in an order that holds while tooling states nothing.

rule.waiting line 32 · specs/consumers/readiness-planner.sdp.md:32

A waiting statement is a Spec whose floor reaches a rung above the rung it states; the queue lists every such Spec once, with the rung its floor allows, and no other Spec.

spec:consumers.readiness-planner.dependency-order · enabled, spec:consumers.readiness-planner.owner-question-holds · enabled

rule.restsOn line 33 · specs/consumers/readiness-planner.sdp.md:33

A waiting Spec rests on each other waiting Spec it names by dependsOn, constrainedBy, decidedBy or refines, the four relations the ready floor reads; no Spec rests on itself.

spec:consumers.readiness-planner.dependency-order · enabled

rule.refinesYields line 34 · specs/consumers/readiness-planner.sdp.md:34

A refines from a Spec to a Spec that names it by dependsOn, constrainedBy or decidedBy orders nothing, so a decision comes before the Spec it shapes and a part before the parent that rests on it.

spec:consumers.readiness-planner.decision-first · enabled

rule.rounds line 35 · specs/consumers/readiness-planner.sdp.md:35

A waiting Spec that rests on no waiting Spec is in round 1, the statements a person can make first; any other waiting Spec is in the round after the latest round among the waiting Specs it rests on.

spec:consumers.readiness-planner.decision-first · enabled, spec:consumers.readiness-planner.dependency-order · enabled

rule.order line 36 · specs/consumers/readiness-planner.sdp.md:36

The queue lists the waiting Specs by round, and within a round by id in code-unit order, numbering each by its place, so each comes after every waiting Spec it rests on unless the two share a cycle.

spec:consumers.readiness-planner.cycle-shares-a-round · enabled, spec:consumers.readiness-planner.dependency-order · enabled

rule.cycles line 37 · specs/consumers/readiness-planner.sdp.md:37

Waiting Specs that reach each other through those rests-on links form a cycle; its members share one round, the round after the latest round among the waiting Specs outside the cycle that any member rests on, or round 1 when there is none, and the planner lists each cycle with one closed path through it and refuses nothing.

spec:consumers.readiness-planner.cycle-shares-a-round · enabled

rule.ownerQuestions line 38 · specs/consumers/readiness-planner.sdp.md:38

Apart from the statements, the planner lists each open question whose decider names the person the caller gives, the owner by default, blocking questions first, each with the Specs it holds: a blocking question holds its own Spec below defined, and it holds every Spec whose ready the typed-dependency clause refuses because the question's own Spec states below defined.

spec:consumers.readiness-planner.owner-question-holds · enabled

rule.undecided line 39 · specs/consumers/readiness-planner.sdp.md:39

The planner counts the open questions that carry no decider, and how many of them block, so an empty list of the owner's questions never reads as nothing waiting on the owner.

no example exercises it

rule.statesNothing line 40 · specs/consumers/readiness-planner.sdp.md:40

The planner is a catalog recipe that reads the graph and states, records and gates nothing; each statement it lists stays a person's edit of the carrier, and a Spec stated out of its order is never a finding.

no example exercises it

0 unkeyed rules.

Verifying examples

Given a probe corpus in which {corpus: "two waiting Specs depend on each other"}
When the statement queue runs over the probe corpus
Then the queue lists {queue: "spec:probe.a, spec:probe.b"} in that order
Then round 1 holds {firstRound: "spec:probe.a, spec:probe.b"}
Then the queue reports {cycles: 1} cycles

Given a probe corpus in which {corpus: "a waiting Spec names a waiting decision that refines it"}
When the statement queue runs over the probe corpus
Then the queue lists {queue: "spec:probe.decision, spec:probe.shaped"} in that order
Then round 1 holds {firstRound: "spec:probe.decision"}
Then the queue reports {cycles: 0} cycles

Given a probe corpus in which {corpus: "one waiting Spec depends on another"}
When the statement queue runs over the probe corpus
Then the queue lists {queue: "spec:probe.base, spec:probe.dependent"} in that order
Then round 1 holds {firstRound: "spec:probe.base"}
Then the queue reports {cycles: 0} cycles

Given a probe corpus in which {corpus: "a Spec carries a blocking question its owner decides and another Spec depends on it"}
When the statement queue runs over the probe corpus
Then the queue lists {queue: ""} in that order
Then the owner's questions hold {held: "spec:probe.subject, spec:probe.dependent"}

Example space

Given a probe corpus in which {corpus:"one waiting Spec depends on another"|"a waiting Spec names a waiting decision that refines it"|"two waiting Specs depend on each other"|"a Spec carries a blocking question its owner decides and another Spec depends on it"}
When the statement queue runs over the probe corpus
Then the queue lists {queue:string} in that order
Then round 1 holds {firstRound:string}
Then the queue reports {cycles:number} cycles
Then the owner's questions hold {held:string}

queueRecipe line 43 · specs/consumers/readiness-planner.sdp.md:43

recipe 46, the statement queue, takes params.decider, a token on the decider field's grammar, "owner" by default; another value returns { diagnostics: [{ parameter, problem }] } and no queue.

queueAnswer line 44 · specs/consumers/readiness-planner.sdp.md:44

{ decider, totals: { waiting, firstRound, rounds, cycles, questions, blockingQuestions, withoutDecider, blockingWithoutDecider }, statements, cycles, questions }, where firstRound counts the round 1 statements, rounds the highest round, questions and blockingQuestions the listed questions, and the last two the open questions that carry no decider.

no citation recorded

statementRow line 45 · specs/consumers/readiness-planner.sdp.md:45

{ place, round, id, title, specKind, packs, statedReadiness, floorReached, restsOn }, where place counts from 1 in queue order, packs lists the Spec's Pack ids in code-unit order, floorReached is the rung its floor allows, and restsOn lists the waiting Specs it rests on, sorted by id.

no citation recorded

cycleRow line 46 · specs/consumers/readiness-planner.sdp.md:46

{ members, cycle }, members sorted by id and cycle the shortest closed path from the first member through the members, found by a breadth-first walk over the ordering relations with targets in code-unit order, as dependency cycles finds its path; rows sort by first member.

no citation recorded

questionRow line 47 · specs/consumers/readiness-planner.sdp.md:47

{ address, spec, index, question, blocking, decider, holds }, where address is the question's entry address or null when it carries no key, index its authored position from 0, and holds its own Spec followed by the Specs it holds below ready, in code-unit order, empty for a non-blocking question.

no citation recorded

questionOrder line 48 · specs/consumers/readiness-planner.sdp.md:48

blocking questions first, then the question that holds more Specs first, then by Spec id and authored position.

Verifier bindings

• spec:consumers.readiness-planner.cycle-shares-a-round · Waiting Specs that rest on each other share a round and report a cycle · declared · example enabled · specs/consumers/readiness-planner.cycle-shares-a-round.sdp.md

  External run evidence from test/self-hosting-readiness-planner.test.ts

  Test anchors: test:protocol.readiness-planner.cycle-shares-a-round, test:protocol.readiness-planner.decision-first, test:protocol.readiness-planner.dependency-order, test:protocol.readiness-planner.owner-question-holds. Specs verified by those bindings: spec:consumers.readiness-planner, spec:consumers.readiness-planner.cycle-shares-a-round, spec:consumers.readiness-planner.decision-first, spec:consumers.readiness-planner.dependency-order, spec:consumers.readiness-planner.owner-question-holds.

  Run 1: external run evidence from vitest 4.1.10

  Build: CI 380 · Branch: feature/roadmap-and-slices-v0 · Commit: 34909918bf0be0e849959644401797191cae379f · Start: 2026-10-22T17:40:31.456Z · Stop: 2026-10-22T17:42:16.171Z

  Name	Suite	Result	Duration
  executes the bound example against a fresh world	The Spec another rests on comes first in the queue (spec:consumers.readiness-planner.dependency-order)	passed	16.93 ms
  executes the bound example against a fresh world	A waiting decision comes before the Spec it shapes (spec:consumers.readiness-planner.decision-first)	passed	3.53 ms
  executes the bound example against a fresh world	Waiting Specs that rest on each other share a round and report a cycle (spec:consumers.readiness-planner.cycle-shares-a-round)	passed	2.58 ms
  executes the bound example against a fresh world	An owner's blocking question lists the Specs it holds (spec:consumers.readiness-planner.owner-question-holds)	passed	2.85 ms
  diagnoses invalid decider null	statement queue details	passed	5.3 ms
  diagnoses invalid decider false	statement queue details	passed	2.91 ms
  diagnoses invalid decider 1	statement queue details	passed	2.79 ms
  diagnoses invalid decider ""	statement queue details	passed	2.7 ms
  diagnoses invalid decider "Owner"	statement queue details	passed	5.63 ms
  diagnoses invalid decider "two words"	statement queue details	passed	2.82 ms
  diagnoses invalid decider "with_underscore"	statement queue details	passed	3 ms
  orders SCCs by longest dependency chain, ignores non-ordering and self edges, and sorts ids by code unit	statement queue details	passed	6.48 ms
  yields refines to the reverse dependsOn relation	statement queue details	passed	1.71 ms
  yields refines to the reverse constrainedBy relation	statement queue details	passed	2.39 ms
  yields refines to the reverse decidedBy relation	statement queue details	passed	1.68 ms
  chooses a shortest cycle path before breaking ties by target id	statement queue details	passed	3.3 ms
  selects every higher floor, ignores lower or equal floors, and orders only direct waiting links	statement queue details	passed	3.23 ms
  selects questions, counts undecided ones, and holds direct typed dependents by stated rung	statement queue details	passed	4.57 ms

• spec:consumers.readiness-planner.decision-first · A waiting decision comes before the Spec it shapes · declared · example enabled · specs/consumers/readiness-planner.decision-first.sdp.md
• spec:consumers.readiness-planner.dependency-order · The Spec another rests on comes first in the queue · declared · example enabled · specs/consumers/readiness-planner.dependency-order.sdp.md
• spec:consumers.readiness-planner.owner-question-holds · An owner's blocking question lists the Specs it holds · declared · example enabled · specs/consumers/readiness-planner.owner-question-holds.sdp.md

Requirement drawing

Decisions

No decision record named.

• impl:protocol.statement-queue-recipe · realizes the statement queue in the shipped recipe catalog · test/self-hosting-readiness-planner.test.ts:74

  Uses

  None.

Runtime observation: not tracked.

Runtime observation: not tracked.

Build attestations: not tracked.

Deployments: not tracked.

Bills of materials: not tracked.