A defined Spec resting on a scoped dependency is told which one

outcome

Execute the next rung's evidence on a Spec whose own floor clears defined and whose ready floor fails on one dependency.

assumptions

• The world holds three story-altitude rule Specs with an Intent outcome and one rule each. The subject declares dependsOn on the basis Spec named in the targets, which states scoped and declares refines on a third Spec stating idea. No Spec records an open question and no anchor is present. A target is written as its relation type, its id, and its stated rung in parentheses.

Examples

Given the graph holds a rule spec {specId: "spec:probe.subject"} stating readiness {statedReadiness: "defined"}
Given the spec {structure: "depends on a spec stating scoped"}
When the reader builds the spec's context
Then the floor reached is {floorReached: "defined"} and the next rung is {nextRung: "ready"}
Then the next rung's first unmet clause is {clauseId: "typed-dependency-targets-are-defined"}
Then that failure names the targets {targets: "dependsOn spec:probe.basis (scoped)"}
Then the stated rung's floor failures number {currentFailures: 0}

Verifier bindings

• test:protocol.next-rung-floor.typed-dependency-targets · verifies the next rung's failure names the dependency stated below defined · anchored · test anchor binding present · test/self-hosting-next-rung-floor.test.ts:234

  External run evidence from test/self-hosting-next-rung-floor.test.ts

  Test anchors: test:protocol.next-rung-floor.blocking-question, test:protocol.next-rung-floor.typed-dependency-targets. Specs verified by those bindings: spec:validation.next-rung-floor, spec:validation.next-rung-floor.blocking-question, spec:validation.next-rung-floor.typed-dependency-targets.

  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	A defined Spec resting on a scoped dependency is told which one (spec:validation.next-rung-floor.typed-dependency-targets)	passed	10.27 ms
  executes the bound example against a fresh world	A scoped Spec held by a blocking question is told the clause (spec:validation.next-rung-floor.blocking-question)	passed	1.18 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.