An unsettled constraint bounds ready but permits defined

outcome

Check the unsettled-fact matrix through the readiness floor.

assumptions

• The world has three rule subjects, each declaring constrainedBy on its own resolving constraint target. The first subject states defined and its target states scoped; the second subject states ready and its target states scoped; the third subject states defined and its target states defined. Each target carries the blocking open question "Is this fact settled?". The subjects have no blocking open questions.
• All probes are story-altitude Specs with declared relations and an Intent outcome. Each rule subject carries a behavior rule, and each constraint target carries a statement and target. Each resolving target declares dependsOn back to its subject. No anchors are present. The expected counts include only honesty/readiness-floor findings, not findings from other validators.
• All three targets derive scoped. The first subject lawfully states defined; the second fails typed-dependency-targets-are-defined; the third target alone fails no-blocking-open-questions for stating defined. Both subjects with scoped targets derive defined, while the third derives ready because the target clause reads the target's stated rung. No target is missing.

Examples

Given the typed dependency matrix {matrix: "unsettled-fact"}
When the reader checks the readiness floor
Then the matrix reports {targetFailures: 1} target failures and {resolutionFailures: 0} resolution failures and {questionFailures: 1} blocking question failures

Verifier bindings

• test:protocol.typed-dependency-floor.unsettled-fact · verifies blocking questions and bounded readiness · anchored · test anchor binding present · test/self-hosting-typed-dependency.test.ts:327

  External run evidence from test/self-hosting-typed-dependency.test.ts

  Test anchors: test:protocol.typed-dependency-floor.missing-targets, test:protocol.typed-dependency-floor.relation-rungs, test:protocol.typed-dependency-floor.stated-readiness, test:protocol.typed-dependency-floor.unsettled-fact. Specs verified by those bindings: spec:validation.typed-dependency-floor, spec:validation.typed-dependency-floor.missing-targets, spec:validation.typed-dependency-floor.relation-rungs, spec:validation.typed-dependency-floor.stated-readiness, spec:validation.typed-dependency-floor.unsettled-fact.

  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	Every relation reads the four stated target rungs (spec:validation.typed-dependency-floor.relation-rungs)	passed	18.95 ms
  executes the bound example against a fresh world	Missing targets fail relation resolution once (spec:validation.typed-dependency-floor.missing-targets)	passed	1.52 ms
  executes the bound example against a fresh world	An unsettled constraint bounds ready but permits defined (spec:validation.typed-dependency-floor.unsettled-fact)	passed	1.09 ms
  executes the bound example against a fresh world	Target floor failures do not propagate across dependencies (spec:validation.typed-dependency-floor.stated-readiness)	passed	46.06 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.