A waiting decision comes before the Spec it shapes

outcome

Execute the yielding rule on a waiting decision that refines the waiting Spec naming it through decidedBy.

assumptions

• The world writes a probe corpus of a story-altitude behavior Spec stating defined with an Intent outcome and one rule, and a decision stating defined with its context and choice. The decision refines the behavior Spec, and the behavior Spec names the decision through decidedBy, so both floors reach ready. The Specs carry the ids the queue names, and the world reads the queue as the dependency-order example does.

Examples

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

Verifier bindings

• test:protocol.readiness-planner.decision-first · anchored · test anchor binding present · test/self-hosting-readiness-planner.test.ts:220

  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 391 · Branch: cursor/media-plan-and-articles-09b1 · Commit: 076cd4f1f85640d8236e5cca1bffffa68ab79a33 · Start: 2026-10-31T15:32:20.471Z · Stop: 2026-10-31T15:34:02.073Z

  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	28.37 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	5.84 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	4.2 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	4.25 ms
  diagnoses invalid decider null	statement queue details	passed	7.23 ms
  diagnoses invalid decider false	statement queue details	passed	4.92 ms
  diagnoses invalid decider 1	statement queue details	passed	3.28 ms
  diagnoses invalid decider ""	statement queue details	passed	2.82 ms
  diagnoses invalid decider "Owner"	statement queue details	passed	10.22 ms
  diagnoses invalid decider "two words"	statement queue details	passed	3.6 ms
  diagnoses invalid decider "with_underscore"	statement queue details	passed	2.3 ms
  orders SCCs by longest dependency chain, ignores non-ordering and self edges, and sorts ids by code unit	statement queue details	passed	5.7 ms
  yields refines to the reverse dependsOn relation	statement queue details	passed	2.38 ms
  yields refines to the reverse constrainedBy relation	statement queue details	passed	2.54 ms
  yields refines to the reverse decidedBy relation	statement queue details	passed	1.85 ms
  chooses a shortest cycle path before breaking ties by target id	statement queue details	passed	4 ms
  selects every higher floor, ignores lower or equal floors, and orders only direct waiting links	statement queue details	passed	3.06 ms
  selects questions, counts undecided ones, and holds direct typed dependents by stated rung	statement queue details	passed	4.51 ms

Requirement drawing

• Satisfying or referencing units: no recorded binding.

Decisions

No decision record named.

No implementation neighborhood recorded.

Runtime observation: not tracked.

Runtime observation: not tracked.

Build attestations: not tracked.

Deployments: not tracked.

Bills of materials: not tracked.