A pinned declaration shows the words of each test line that cites it

spec:consumers.spec-studio.cited-line-text

Use Case / Behavior · storyscoped floor scoped

New since the base graph base da4b141. See the diff.

Base input: schema 0.11.0, 405 Specs.

Next rung defined waits on 1 unmet clause:

no-blocking-open-questions · Spec has no blocking open question in intent.openQuestions.

Packs: pack:roadmap, pack:self-hosting-v1

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

Findings: no errors, no warnings

specs/consumers/spec-studio.cited-line-text.sdp.md

2 open questions and 1 blocking question; implementation binding none, verifier binding none, and expected-outcome oracle none.

A reader checking a pinned declaration reaches the test line that cites it and then follows a source link to read the assertion. The words of that line would close the task on the page. The graph records where a line cites an entry and never what the line says, and the Studio reads only the graph and its named inputs, so one of them has to hold the words. The extractor already reads the line when it records the citation, which makes the citation row the cheapest honest home; the choice is the owner's, because it puts source text in the graph for the first time.

Intent

actor: A reviewer with only a link, checking that a pinned declaration is held to its code.
problem: The declarations page names each citing line by file and line only, so the reader leaves the page to read it, and has no route at all when the page set carries no source link.
outcome: Show beside each pinned declaration the text of every test line that cites it, so a reviewer reads the check without leaving the page.

Open questions

blocking · question.lineText line 26 · specs/consumers/spec-studio.cited-line-text.sdp.md:26 · May the Studio show source text the graph does not hold, and if so is it recorded in the graph beside the citation or read as a named input?Decider: ownerProvisional: the extractor records the citing line's text, trimmed and bounded, on the citation row it already writes, as inferred data that confers nothing, and the Studio reads no source
non-blocking · question.lineBound line 29 · specs/consumers/spec-studio.cited-line-text.sdp.md:29 · How long may a recorded line be, and how does a page show a line that was cut?Decider: delegatedProvisional: a bound of a few hundred code units, cut at a word boundary and marked as cut, the whole line one source link away

Behavior

rule.lineShown line 35 · specs/consumers/spec-studio.cited-line-text.sdp.md:35: Beside each citing line, the declarations page and the Spec page show the line's words as code after its file and line, and the reader's citation row carries them.
no example exercises it
rule.wordsNotVerdict line 36 · specs/consumers/spec-studio.cited-line-text.sdp.md:36: The words are what the citing line said at the commit the graph was derived from; no page says the line asserts, checks or passes anything because of them.
no example exercises it
rule.withoutWords line 37 · specs/consumers/spec-studio.cited-line-text.sdp.md:37: A citation whose words are not recorded shows its file and line as it does now.
no example exercises it

0 unkeyed rules.

Verification

Verifier bindings

No verifier binding recorded.

Design view

Requirement drawing

Declared verifying examples: no declared verifying example.
Satisfying or referencing units: no recorded binding.
Test or oracle bindings: no recorded binding.

Requirement drawing for spec:consumers.spec-studio.cited-line-text

Arrows: refines (declared).

The diagram as text

spec:consumers.spec-studio.cited-line-text: A pinned declaration shows the words of each test line that cites it · declared Spec · no satisfying binding
spec:consumers.spec-studio: The Spec Studio is a static HTML workbench over the one graph · declared Spec
spec:consumers.spec-studio.cited-line-text refines spec:consumers.spec-studio · declared

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:consumers.spec-studio.cited-line-text

requirementDiagram
  requirement n0 {
    text: "A pinned declaration shows the words of each test line that cites it · declared Spec · no satisfying binding · spec:consumers.spec-studio.cited-line-text"
  }
  requirement n1 {
    text: "The Spec Studio is a static HTML workbench over the one graph · declared Spec · spec:consumers.spec-studio"
  }
  %% claim: declared
  n0 - refines -> n1

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.spec-studio.cited-line-text

The diagram as text

spec:consumers.spec-studio: The Spec Studio is a static HTML workbench over the one graph
spec:consumers.spec-studio.cited-line-text: A pinned declaration shows the words of each test line that cites it
spec:consumers.spec-studio.registers: The corpus's registers are pages a reviewer opens from a link
spec:extraction.entry-citations: The graph records where anchored source cites an entry address
spec:consumers.spec-studio.cited-line-text dependsOn spec:consumers.spec-studio.registers · declared — the declarations page lists each citing line beside its declaration
spec:consumers.spec-studio.cited-line-text dependsOn spec:extraction.entry-citations · declared — the words belong to a citation the graph already records by file and line
spec:consumers.spec-studio.cited-line-text refines spec:consumers.spec-studio · 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:consumers.spec-studio.cited-line-text

flowchart TB
  n0["The Spec Studio is a static HTML workbench over the one graph · spec:consumers.spec-studio"]
  n1["The corpus's registers are pages a reviewer opens from a link · spec:consumers.spec-studio.registers"]
  n2["The graph records where anchored source cites an entry address · spec:extraction.entry-citations"]
  n3["A pinned declaration shows the words of each test line that cites it · spec:consumers.spec-studio.cited-line-text"]
  n3 -->|"refines · declared"| n0
  n3 -->|"dependsOn · declared — the declarations page lists each citing line beside its declaration"| n1
  n3 -->|"dependsOn · declared — the words belong to a citation the graph already records by file and line"| n2

Rests on

refines · spec:consumers.spec-studio · stated ready, floor ready
dependsOn · spec:consumers.spec-studio.registers · stated ready, floor ready
dependsOn · spec:extraction.entry-citations · stated ready, floor ready

Rested on by

No Spec rests on this Spec.

Relations

Relation and direction	Other end	Claim	Reason	Exercised keys
dependsOn · outgoing	The corpus's registers are pages a reviewer opens from a link `spec:consumers.spec-studio.registers` · resolves	declared	the declarations page lists each citing line beside its declaration	None
dependsOn · outgoing	The graph records where anchored source cites an entry address `spec:extraction.entry-citations` · resolves	declared	the words belong to a citation the graph already records by file and line	None
refines · outgoing	The Spec Studio is a static HTML workbench over the one graph `spec:consumers.spec-studio` · resolves	declared	None	None

Bindings

Implementation binding: none

Design reference: none

Verifier binding: none

Expected-outcome oracle: none

Runtime observation: not tracked.

Run results: not recorded in the graph.

Findings

None.

Composing (0)

Composing needs the script.