Code spans in section descriptions are literal

spec:carrier.inline-code-spans.description

Example / Scenario · storyready floor ready

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

specs/carrier/inline-code-spans.description.sdp.md

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

Given

the code-span matrix in {location: "description"}

When

the extractor reifies the probes

Then

matched spans preserve {accepted: 15} carriers and exposed HTML refuses {refused: 20} carriers

Composing needs the script.

Intent

outcome: Check matched and unmatched runs, literal HTML, exposed HTML on the same line, and authored text in the description probes.
assumptions: Each probe has its own carrier. Each Spec is a story-altitude behavior stating idea with no relations and an Intent outcome. The probe sits in the Behavior description.

Behavior

Examples

Given the code-span matrix in {location: "description"}
When the extractor reifies the probes
Then matched spans preserve {accepted: 15} carriers and exposed HTML refuses {refused: 20} carriers

Verification

Verifier bindings

test:protocol.inline-code-spans.description · verifies inline code in section descriptions · anchored · test anchor binding present · test/self-hosting-inline-code.test.ts:219

External run evidence from `test/self-hosting-inline-code.test.ts`

Test anchors: test:protocol.inline-code-spans.description, test:protocol.inline-code-spans.list, test:protocol.inline-code-spans.narrative, test:protocol.inline-code-spans.pack. Specs verified by those bindings: spec:carrier.inline-code-spans, spec:carrier.inline-code-spans.description, spec:carrier.inline-code-spans.list, spec:carrier.inline-code-spans.narrative, spec:carrier.inline-code-spans.pack.

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

Name	Suite	Result	Duration
executes the bound example against a fresh world	Code spans in a Spec narrative are literal (spec:carrier.inline-code-spans.narrative)	passed	63.42 ms
executes the bound example against a fresh world	Code spans in section descriptions are literal (spec:carrier.inline-code-spans.description)	passed	21.18 ms
executes the bound example against a fresh world	Code spans in list entries are literal (spec:carrier.inline-code-spans.list)	passed	31.9 ms
executes the bound example against a fresh world	Code spans in Pack framing are literal (spec:carrier.inline-code-spans.pack)	passed	20.55 ms

Design view

Requirement drawing

Satisfying or referencing units: no recorded binding.

Requirement drawing for spec:carrier.inline-code-spans.description

The diagram as text

spec:carrier.inline-code-spans.description: Code spans in section descriptions are literal · declared Spec
spec:carrier.inline-code-spans: Inline code is content, never markup · declared Spec
test:protocol.inline-code-spans.description: verifies inline code in section descriptions · anchored test binding · binding present · test/self-hosting-inline-code.test.ts:219
spec:carrier.inline-code-spans.description refines spec:carrier.inline-code-spans · declared
spec:carrier.inline-code-spans.description verifies spec:carrier.inline-code-spans · declared
test:protocol.inline-code-spans.description verifies spec:carrier.inline-code-spans.description · 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.

Mermaid source for Requirement drawing for spec:carrier.inline-code-spans.description

requirementDiagram
  requirement n0 {
    text: "Code spans in section descriptions are literal · declared Spec · spec:carrier.inline-code-spans.description"
  }
  element n1 {
    type: "verifies inline code in section descriptions · anchored test binding · binding present · test:protocol.inline-code-spans.description"
  }
  requirement n2 {
    text: "Inline code is content, never markup · declared Spec · spec:carrier.inline-code-spans"
  }
  %% claim: declared
  n0 - refines -> n2
  %% claim: declared
  n0 - verifies -> n2
  %% claim: anchored
  n1 - verifies -> n0

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:carrier.inline-code-spans.description

E2: verifies · declared

The diagram as text

spec:carrier.inline-code-spans: Inline code is content, never markup
spec:carrier.inline-code-spans.description: Code spans in section descriptions are literal
spec:carrier.inline-code-spans.description refines spec:carrier.inline-code-spans · declared
spec:carrier.inline-code-spans.description verifies spec:carrier.inline-code-spans · declared

Mermaid source

Copyable source; the Studio draws static SVG.

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

Mermaid source for Relations of spec:carrier.inline-code-spans.description

flowchart TB
  n0["Inline code is content, never markup · spec:carrier.inline-code-spans"]
  n1["Code spans in section descriptions are literal · spec:carrier.inline-code-spans.description"]
  n1 -->|"refines · declared"| n0
  n1 -->|"verifies · declared"| n0

Rests on

refines · spec:carrier.inline-code-spans · stated ready, floor ready

Rested on by

No Spec rests on this Spec.

Relations

Relation and direction	Other end	Claim	Reason	Exercised keys
refines · outgoing	Inline code is content, never markup `spec:carrier.inline-code-spans` · resolves	declared	None	None
verifies · outgoing	Inline code is content, never markup `spec:carrier.inline-code-spans` · resolves	declared	None	`literalSpan`, `lineScoped`, `noEscape`, `spanBeforeTag`, `rawHtmlRefused`

Bindings

Implementation binding: none

Design reference: none

Verifier binding: present

test:protocol.inline-code-spans.description · verifies inline code in section descriptions · anchored · test/self-hosting-inline-code.test.ts:219 · 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.

Examples

Verifier bindings

External run evidence from test/self-hosting-inline-code.test.ts

Run 1: external run evidence from vitest 4.1.10

Requirement drawing

Decisions

Rests on

Rested on by

Relations

Bindings

Implementation binding: none

Design reference: none

Verifier binding: present

Expected-outcome oracle: none

Findings

External run evidence from `test/self-hosting-inline-code.test.ts`