A ready unbound part needs building

spec:consumers.roadmap.buildable-part

Example / Scenario · storyready floor ready

Packs: pack:roadmaps-and-slices-v1, pack:self-hosting-v1

Design: no design entries · no pinned declarations · no decisions

specs/consumers/roadmap.buildable-part.sdp.md

No open questions and no blocking questions; implementation binding none, verifier binding present, and expected-outcome oracle none.

Given

a probe roadmap whose entry holds the work {work: "spec:probe.root, spec:probe.part"}
that work {state: "has one part ready and not implemented"}

When

the roadmap recipe reads the probe roadmap

Then

the entry's need reads {need: "to build"}

Composing needs the script.

Intent

outcome: Execute one roadmap reading over a probe corpus.
assumptions: The world writes a roadmap Pack with one ready behavior root and one behavior descendant, each with an Intent outcome. The root has one rule and a direct implementation binding; both Specs have resolving relations. The root has a binding and its ready descendant has none. The roadmap reads the shipped body over the extracted probe corpus.

Behavior

Examples

Given a probe roadmap whose entry holds the work {work: "spec:probe.root, spec:probe.part"}
Given that work {state: "has one part ready and not implemented"}
When the roadmap recipe reads the probe roadmap
Then the entry's need reads {need: "to build"}

Verification

Verifier bindings

test:protocol.roadmap.buildable-part · anchored · test anchor binding present · test/roadmap-examples.test.ts:174

External run evidence from `test/roadmap-examples.test.ts`

Test anchors: test:protocol.roadmap.blocking-part, test:protocol.roadmap.buildable-part, test:protocol.roadmap.built-work, test:protocol.roadmap.design-part, test:protocol.roadmap.drifting-part, test:protocol.roadmap.missing-evidence, test:protocol.roadmap.outside-parent, test:protocol.roadmap.statement-order, test:protocol.roadmap.statement-part. Specs verified by those bindings: spec:consumers.roadmap, spec:consumers.roadmap.blocking-part, spec:consumers.roadmap.buildable-part, spec:consumers.roadmap.built-work, spec:consumers.roadmap.design-part, spec:consumers.roadmap.drifting-part, spec:consumers.roadmap.missing-evidence, spec:consumers.roadmap.outside-parent, spec:consumers.roadmap.statement-order, spec:consumers.roadmap.statement-part.

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
rejects a statement-order point with a different bound state	not recorded	passed	2.38 ms
checks the bound work against the observed scope	not recorded	passed	35.82 ms
executes the bound example against a fresh world	Built work stays on the roadmap (spec:consumers.roadmap.built-work)	passed	8.17 ms
executes the bound example against a fresh world	A ready unbound part needs building (spec:consumers.roadmap.buildable-part)	passed	6.64 ms
executes the bound example against a fresh world	A complete part waits for a statement (spec:consumers.roadmap.statement-part)	passed	6.31 ms
executes the bound example against a fresh world	An unfinished part needs design (spec:consumers.roadmap.design-part)	passed	9.78 ms
executes the bound example against a fresh world	A binding below ready remains drift (spec:consumers.roadmap.drifting-part)	passed	13.87 ms
executes the bound example against a fresh world	A descendant without evidence names its holding clause (spec:consumers.roadmap.missing-evidence)	passed	4.62 ms
executes the bound example against a fresh world	A descendant question holds the entry for design (spec:consumers.roadmap.blocking-part)	passed	4.81 ms
executes the bound example against a fresh world	A descendant names its outside parent (spec:consumers.roadmap.outside-parent)	passed	8.57 ms
executes the bound example against a fresh world	Waiting statements keep dependency order against roadmap places (spec:consumers.roadmap.statement-order)	passed	4.83 ms

Design view

Requirement drawing

Satisfying or referencing units: no recorded binding.

Requirement drawing for spec:consumers.roadmap.buildable-part

The diagram as text

spec:consumers.roadmap.buildable-part: A ready unbound part needs building · declared Spec
spec:consumers.roadmap: A roadmap orders the next bodies of work, and the graph says what each still needs · declared Spec
test:protocol.roadmap.buildable-part: test:protocol.roadmap.buildable-part · anchored test binding · binding present · test/roadmap-examples.test.ts:174
spec:consumers.roadmap.buildable-part refines spec:consumers.roadmap · declared
spec:consumers.roadmap.buildable-part verifies spec:consumers.roadmap · declared
test:protocol.roadmap.buildable-part verifies spec:consumers.roadmap.buildable-part · anchored

Mermaid source

Copyable source; the Studio draws static SVG.

Preferred and chosen syntax: requirementDiagram; exact refines, satisfies and verifies, with claim words in nodes and per-edge comments.

Mermaid source for Requirement drawing for spec:consumers.roadmap.buildable-part

requirementDiagram
  requirement n0 {
    text: "A ready unbound part needs building · declared Spec · spec:consumers.roadmap.buildable-part"
  }
  element n1 {
    type: "test:protocol.roadmap.buildable-part · anchored test binding · binding present · test:protocol.roadmap.buildable-part"
  }
  requirement n2 {
    text: "A roadmap orders the next bodies of work, and the graph says what each still needs · declared Spec · spec:consumers.roadmap"
  }
  %% claim: declared
  n0 - refines -> n2
  %% claim: declared
  n0 - verifies -> n2
  %% claim: anchored
  n1 - verifies -> n0

Decisions

No decision record named.

Runtime

No implementation neighborhood recorded.

Runtime observation: not tracked.

Evidence

Runtime observation: not tracked.

Build attestations: not tracked.

Deployments: not tracked.

Bills of materials: not tracked.

Impact

Relations of spec:consumers.roadmap.buildable-part

E2: verifies · declared

The diagram as text

spec:consumers.roadmap: A roadmap orders the next bodies of work, and the graph says what each still needs
spec:consumers.roadmap.buildable-part: A ready unbound part needs building
spec:consumers.roadmap.buildable-part refines spec:consumers.roadmap · declared
spec:consumers.roadmap.buildable-part verifies spec:consumers.roadmap · declared

Mermaid source

Copyable source; the Studio draws static SVG.

Preferred syntax: flowchart. Chosen syntax: labelled flowchart, preserving exact relations, claims and folds.

Mermaid source for Relations of spec:consumers.roadmap.buildable-part

flowchart TB
  n0["A roadmap orders the next bodies of work, and the graph says what each still needs · spec:consumers.roadmap"]
  n1["A ready unbound part needs building · spec:consumers.roadmap.buildable-part"]
  n1 -->|"refines · declared"| n0
  n1 -->|"verifies · declared"| n0

Rests on

refines · spec:consumers.roadmap · stated ready, floor ready

Rested on by

No Spec rests on this Spec.

Relations

Relation and direction	Other end	Claim	Reason	Exercised keys
refines · outgoing	A roadmap orders the next bodies of work, and the graph says what each still needs `spec:consumers.roadmap` · resolves	declared	None	None
verifies · outgoing	A roadmap orders the next bodies of work, and the graph says what each still needs `spec:consumers.roadmap` · resolves	declared	None	`scope`, `specNeed`, `entryNeed`, `workRows`

Bindings

Implementation binding: none

Design reference: none

Verifier binding: present

test:protocol.roadmap.buildable-part · anchored · test/roadmap-examples.test.ts:174 · test anchor

Expected-outcome oracle: none

Runtime observation: not tracked.

Run results: not recorded in the graph.

Findings

None.

Composing (0)

Composing needs the script.

Examples

Verifier bindings

External run evidence from test/roadmap-examples.test.ts

Run 1: external run evidence from vitest 4.1.10

Requirement drawing

Decisions

Rests on

Rested on by

Relations

Bindings

Implementation binding: none

Design reference: none

Verifier binding: present

Expected-outcome oracle: none

Findings

External run evidence from `test/roadmap-examples.test.ts`