A keyed question is reified and its address resolves

outcome

Execute the key grammar and the question address on one keyed question beside an unkeyed one.

assumptions

• The world writes two Markdown carriers in one extraction root. The first is a story-altitude rule Spec stating scoped with an Intent outcome, one rule, and one declared refines on the second; its Open questions hold the entries written in questions, one line each, where the slot joins them with a semicolon and a space. The second is a story-altitude rule Spec stating idea with an Intent outcome and one rule; it names the address in its narrative and declares dependsOn on the first. The messages of the extraction findings are joined by a semicolon and a space, and an empty string names no finding; the keys of every Spec in the graph are joined by a comma and a space.

Examples

Given a Markdown Spec carrier {specId: "spec:probe.subject"} whose open questions read {questions: "- [blocking #aggregateReach] Does the owner widen the aggregate?; - [non-blocking] Is the name final?"}
Given a second Spec that names {address: "spec:probe.subject#question.aggregateReach"} in its narrative and declares dependsOn on the first
When the extractor reifies both carriers and the graph is validated
Then the first carrier is reified: {reified: true}
Then the extraction findings name {extractMessage: ""}
Then the graph holds the question keys {keys: "aggregateReach"}
Then the report holds {mentionErrors: 0} prose-mention errors

Verifier bindings

• test:protocol.open-question-keys.keyed-question-resolves · verifies a keyed question is reified and its question address resolves · anchored · test anchor binding present · test/self-hosting-open-question-keys.test.ts:329

  External run evidence from test/self-hosting-open-question-keys.test.ts

  Test anchors: test:protocol.open-question-keys.keyed-question-resolves, test:protocol.open-question-keys.renamed-key-breaks, test:protocol.open-question-keys.repeated-key-refused. Specs verified by those bindings: spec:model.open-question-keys, spec:model.open-question-keys.keyed-question-resolves, spec:model.open-question-keys.renamed-key-breaks, spec:model.open-question-keys.repeated-key-refused.

  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 keyed question is reified and its address resolves (spec:model.open-question-keys.keyed-question-resolves)	passed	17.42 ms
  executes the bound example against a fresh world	A renamed question key fails the mention that addresses it (spec:model.open-question-keys.renamed-key-breaks)	passed	4.62 ms
  executes the bound example against a fresh world	A repeated question key refuses its carrier (spec:model.open-question-keys.repeated-key-refused)	passed	3.92 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.