Spec Studio

A source file reaches the Spec its binding names, and a carrier reaches its own Spec

spec:consumers.reader.file-entryExample / Scenario · storyready floor ready

Packs: pack:self-hosting-v1

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

Findings: no errors, no warnings

specs/consumers/reader.sdp.gherkin

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

Intent
outcome
Execute the file entry on both halves it has to bridge — a source file the graph records only a binding at, and the carrier a Spec is authored in.
Behavior

Examples

Given a reader built over the graph a real extraction derives from the probe root
Given the source file {boundFile: "src/create-order.ts"} carries the binding {bindingId: "impl:orders.create-order"}
When the reader answers the {entry: "file"} entry
Then the file entry names the node {nodeId: "impl:orders.create-order"} the graph records at that path
Then the file entry reaches the spec {reachedSpecId: "spec:orders.create-order"} that binding names
Then the spec carrier {carrierFile: "specs/create-order.sdp.md"} answers with its own spec {carrierSpecId: "spec:orders.create-order"}
Verification

Verifier bindings

  • test:protocol.reader.file-entry · the file-entry point verifies both halves of the file bridge · anchored · test anchor binding present · test/self-hosting-consumers.test.ts:507

    External run evidence from test/self-hosting-consumers.test.ts

    Test anchors: test:protocol.agent-surface.demand-map-entries, test:protocol.agent-surface.scripted-context-body, test:protocol.reader.changeset-entry, test:protocol.reader.concept-entry, test:protocol.reader.file-entry. Specs verified by those bindings: spec:consumers.agent-surface, spec:consumers.agent-surface.demand-map-entries, spec:consumers.agent-surface.scripted-context-body, spec:consumers.reader, spec:consumers.reader.changeset-entry, spec:consumers.reader.concept-entry, spec:consumers.reader.file-entry.

    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

    NameSuiteResultDuration
    executes the bound example against a fresh worldA scripted body returns claim-decoded context, pre-shaped by the body (spec:consumers.agent-surface.scripted-context-body)passed55.11 ms
    executes the bound example against a fresh worldOne body reaches every entry point the demand map names, and no symbol entry (spec:consumers.agent-surface.demand-map-entries)passed17.19 ms
    executes the bound example against a fresh worldA concept recorded only inside a Spec's sections is still reached, and the field is named (spec:consumers.reader.concept-entry)passed29.24 ms
    executes the bound example against a fresh worldA source file reaches the Spec its binding names, and a carrier reaches its own Spec (spec:consumers.reader.file-entry)passed23.41 ms
    executes the bound example against a fresh worldA changeset names what it reaches, why, and what it cannot see (spec:consumers.reader.changeset-entry)passed17.23 ms
Design view

Requirement drawing

  • Satisfying or referencing units: no recorded binding.
Requirement drawing for spec:consumers.reader.file-entry
The diagram as text
  • spec:consumers.reader.file-entry: A source file reaches the Spec its binding names, and a carrier reaches its own Spec · declared Spec
  • spec:consumers.reader: The reader bridges agent entry points to composable graph context · declared Spec
  • test:protocol.reader.file-entry: the file-entry point verifies both halves of the file bridge · anchored test binding · binding present · test/self-hosting-consumers.test.ts:507
  • spec:consumers.reader.file-entry refines spec:consumers.reader · declared
  • spec:consumers.reader.file-entry verifies spec:consumers.reader · declared
  • test:protocol.reader.file-entry verifies spec:consumers.reader.file-entry · 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.

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.reader.file-entry
  • E2: verifies · declared
The diagram as text
  • spec:consumers.reader: The reader bridges agent entry points to composable graph context
  • spec:consumers.reader.file-entry: A source file reaches the Spec its binding names, and a carrier reaches its own Spec
  • spec:consumers.reader.file-entry refines spec:consumers.reader · declared
  • spec:consumers.reader.file-entry verifies spec:consumers.reader · declared
Mermaid source

Copyable source; the Studio draws static SVG.

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

Rests on

Rested on by

No Spec rests on this Spec.

Relations

Relation and directionOther endClaimReasonExercised keys
refines · outgoingThe reader bridges agent entry points to composable graph context
spec:consumers.reader · resolves		declaredNoneNone
verifies · outgoingThe reader bridges agent entry points to composable graph context
spec:consumers.reader · resolves		declaredNonefileEntry

Bindings

Implementation binding: none

Design reference: none

Verifier binding: present

  • test:protocol.reader.file-entry · the file-entry point verifies both halves of the file bridge · anchored · test/self-hosting-consumers.test.ts:507 · 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.