A descendant without evidence names its holding clause

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 descendant states scoped, refines the ready root and has no behavior evidence. The roadmap reads the shipped body over the extracted probe corpus.

Examples

Given a probe roadmap whose entry holds the work {work: "spec:probe.root, spec:probe.part"}
Given that work {state: "has a ready root and one descendant without its kind's evidence"}
When the roadmap recipe reads the probe roadmap
Then the entry names {part: "spec:probe.part"} among the parts with its need, held by {clause: "kind-evidence-present"}

Verifier bindings

• test:protocol.roadmap.missing-evidence · anchored · test anchor binding present · test/roadmap-examples.test.ts:202

  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 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
  rejects a statement-order point with a different bound state	not recorded	passed	2.77 ms
  checks the bound work against the observed scope	not recorded	passed	48.37 ms
  executes the bound example against a fresh world	Built work stays on the roadmap (spec:consumers.roadmap.built-work)	passed	10.74 ms
  executes the bound example against a fresh world	A ready unbound part needs building (spec:consumers.roadmap.buildable-part)	passed	7.21 ms
  executes the bound example against a fresh world	A complete part waits for a statement (spec:consumers.roadmap.statement-part)	passed	9.23 ms
  executes the bound example against a fresh world	An unfinished part needs design (spec:consumers.roadmap.design-part)	passed	9.36 ms
  executes the bound example against a fresh world	A binding below ready remains drift (spec:consumers.roadmap.drifting-part)	passed	13.88 ms
  executes the bound example against a fresh world	A descendant without evidence names its holding clause (spec:consumers.roadmap.missing-evidence)	passed	8.83 ms
  executes the bound example against a fresh world	A descendant question holds the entry for design (spec:consumers.roadmap.blocking-part)	passed	6.21 ms
  executes the bound example against a fresh world	A descendant names its outside parent (spec:consumers.roadmap.outside-parent)	passed	9.88 ms
  executes the bound example against a fresh world	Waiting statements keep dependency order against roadmap places (spec:consumers.roadmap.statement-order)	passed	4.79 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.