Spec Studio

A prefix excludes its own tree and leaves a similar sibling standing

spec:extraction.excludes.segment-boundaryExample / Scenario · storyready floor ready

Packs: pack:self-hosting-v1

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

Findings: no errors, no warnings

specs/extraction/excludes.segment-boundary.sdp.md

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

Intent
outcome
Execute the segment-boundary rule across both discovery surfaces.
Behavior

Examples

Given the extraction root carries the tree {excludedTree: "foo"} and the similar sibling {similarTree: "foobar"}
Given the consumer supplies the exclusion {exclusion: "foo"}
When the root is discovered
Then the discovery attempt {outcome: "completes"}
Then the surviving spec carrier is {specCarrier: "foobar/included.sdp.ts"} and the surviving anchor candidate is {anchorCandidate: "foobar/helper.ts"}
Verification

Verifier bindings

  • test:protocol.excludes.segment-boundary · the segment-boundary point verifies the exact-prefix exclusion rule · anchored · test anchor binding present · test/self-hosting-extraction.test.ts:285

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

    Test anchors: test:protocol.build-pipeline.same-invocation, test:protocol.example-runner.red-step-naming, test:protocol.example-runner.step-order, test:protocol.excludes.refused-path, test:protocol.excludes.segment-boundary, test:protocol.executable-contracts.case-colliding-path, test:protocol.executable-contracts.concreteness-refusal, test:protocol.executable-contracts.multi-entry-example, test:protocol.schema-versioning.declared-version. Specs verified by those bindings: spec:extraction.build-pipeline, spec:extraction.build-pipeline.same-invocation, spec:extraction.example-runner, spec:extraction.example-runner.red-step-naming, spec:extraction.example-runner.step-order, spec:extraction.excludes, spec:extraction.excludes.refused-path, spec:extraction.excludes.segment-boundary, spec:extraction.executable-contracts, spec:extraction.executable-contracts.case-colliding-path, spec:extraction.executable-contracts.concreteness-refusal, spec:extraction.executable-contracts.multi-entry-example, spec:extraction.schema-versioning, spec:extraction.schema-versioning.declared-version.

    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

    NameSuiteResultDuration
    executes the bound example against a fresh worldOne query invocation shares its extracted graph and validation result (spec:extraction.build-pipeline.same-invocation)passed13.53 ms
    executes the bound example against a fresh worldA prefix excludes its own tree and leaves a similar sibling standing (spec:extraction.excludes.segment-boundary)passed1.19 ms
    executes the bound example against a fresh worldA Windows-drive absolute path is refused rather than normalized (spec:extraction.excludes.refused-path)passed0.66 ms
    executes the bound example against a fresh worldA derived payload carries a schema version its consumer can read (spec:extraction.schema-versioning.declared-version)passed0.42 ms
    executes the bound example against a fresh worldAn unbound slot in a used step earns no step contract (spec:extraction.executable-contracts.concreteness-refusal)passed1.07 ms
    executes the bound example against a fresh worldA second structured entry is named, never left silently inert (spec:extraction.executable-contracts.multi-entry-example)passed1.8 ms
    executes the bound example against a fresh worldA case-only path collision withholds the whole contracts tree (spec:extraction.executable-contracts.case-colliding-path)passed0.7 ms
    executes the bound example against a fresh worldA repeated step runs its one handler at each occurrence, in contract order (spec:extraction.example-runner.step-order)passed0.32 ms
    executes the bound example against a fresh worldA red step names itself before the assertion detail (spec:extraction.example-runner.red-step-naming)passed0.33 ms
Design view

Requirement drawing

  • Satisfying or referencing units: no recorded binding.
Requirement drawing for spec:extraction.excludes.segment-boundary
The diagram as text
  • spec:extraction.excludes.segment-boundary: A prefix excludes its own tree and leaves a similar sibling standing · declared Spec
  • spec:extraction.excludes: Extraction exclusions are strict consumer input · declared Spec
  • test:protocol.excludes.segment-boundary: the segment-boundary point verifies the exact-prefix exclusion rule · anchored test binding · binding present · test/self-hosting-extraction.test.ts:285
  • spec:extraction.excludes.segment-boundary refines spec:extraction.excludes · declared
  • spec:extraction.excludes.segment-boundary verifies spec:extraction.excludes · declared
  • test:protocol.excludes.segment-boundary verifies spec:extraction.excludes.segment-boundary · 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:extraction.excludes.segment-boundary
  • E2: verifies · declared
The diagram as text
  • spec:extraction.excludes: Extraction exclusions are strict consumer input
  • spec:extraction.excludes.segment-boundary: A prefix excludes its own tree and leaves a similar sibling standing
  • spec:extraction.excludes.segment-boundary refines spec:extraction.excludes · declared
  • spec:extraction.excludes.segment-boundary verifies spec:extraction.excludes · 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 · outgoingExtraction exclusions are strict consumer input
spec:extraction.excludes · resolves
declaredNoneNone
verifies · outgoingExtraction exclusions are strict consumer input
spec:extraction.excludes · resolves
declaredNonesegmentBoundary

Bindings

Implementation binding: none

Design reference: none

Verifier binding: present

  • test:protocol.excludes.segment-boundary · the segment-boundary point verifies the exact-prefix exclusion rule · anchored · test/self-hosting-extraction.test.ts:285 · 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.