An outside register is a named Studio input, so a cited token links to its entry

spec:consumers.spec-studio.register-input

Use Case / Behavior · storyscoped floor scoped

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

specs/consumers/spec-studio.register-input.sdp.md

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

A corpus that cites an outside register, an open-decisions list or an earlier system's references, writes its tokens in prose. The external-registers recipe checks them against a register file the corpus passes; a reader on the page still sees only the token. On the first adopter's pages a reader met a cited open decision and found no route to its entry. The register is the corpus's own data, so it reaches the Studio the way the base graph and the run records do: named on the command line, named on every page that shows it, and never graph data.

Intent

actor: A reviewer with only a link who meets a cited token, such as an open decision's number, in a Spec's text.
problem: A cited token reads as bare text on every page, and the register that defines it is neither linked nor shown.
outcome: Let the Studio take an outside register as a named input, so each token a corpus cites from it links to its entry, named as outside evidence and never as graph data.

Open questions

blocking · question.registerEntry line 26 · specs/consumers/spec-studio.register-input.sdp.md:26 · What does a register file give the Studio beyond what the external-registers recipe reads, so a token's entry can be shown?Decider: delegatedProvisional: an optional title and an optional href on a token object; the Studio writes one page per register listing each token with its title, retired tokens marked, each linking to its href when present
blocking · question.inputForm line 29 · specs/consumers/spec-studio.register-input.sdp.md:29 · How does the studio verb name a register, its pattern and the words that name it on a page?Decider: delegatedProvisional: a repeatable --register NAME=PATH with a matching --register-pattern NAME=SOURCE, the name naming the register in words wherever it shows
non-blocking · question.textLinks line 32 · specs/consumers/spec-studio.register-input.sdp.md:32 · Does a cited token become a link inside the rendered text of a Spec, or only in a list beside it?Decider: delegatedProvisional: inside the text, matched by the register's pattern exactly as the recipe matches it, so the page and the check agree on what is cited

Behavior

rule.registerNamed line 38 · specs/consumers/spec-studio.register-input.sdp.md:38: A register is a named input like the base graph and the run records: a page that shows it names it in words, and it never becomes graph data, a finding, a fact or a rung.
no example exercises it
rule.tokenRoute line 39 · specs/consumers/spec-studio.register-input.sdp.md:39: Each token the register's pattern finds in a Spec's text routes to that token's entry on the register's page, and a token the register does not list, or retires, reads so beside it.
no example exercises it
rule.withoutRegister line 40 · specs/consumers/spec-studio.register-input.sdp.md:40: Without the input every page is what the graph alone writes.
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.register-input

Arrows: refines (declared).

The diagram as text

spec:consumers.spec-studio.register-input: An outside register is a named Studio input, so a cited token links to its entry · 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.register-input 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.register-input

requirementDiagram
  requirement n0 {
    text: "An outside register is a named Studio input, so a cited token links to its entry · declared Spec · no satisfying binding · spec:consumers.spec-studio.register-input"
  }
  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.register-input

The diagram as text

spec:consumers.spec-studio: The Spec Studio is a static HTML workbench over the one graph
spec:consumers.spec-studio.data.inputs: The Studio reads two named inputs beside the graph, a base graph and run records
spec:consumers.spec-studio.register-input: An outside register is a named Studio input, so a cited token links to its entry
spec:validation.external-registers: A corpus checks the register tokens its prose cites
spec:consumers.spec-studio.register-input dependsOn spec:consumers.spec-studio.data.inputs · declared — the register joins the base graph and the run records as a named input
spec:consumers.spec-studio.register-input dependsOn spec:validation.external-registers · declared — the input is the register file and pattern the external-registers recipe already reads
spec:consumers.spec-studio.register-input 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.register-input

flowchart TB
  n0["The Spec Studio is a static HTML workbench over the one graph · spec:consumers.spec-studio"]
  n1["The Studio reads two named inputs beside the graph, a base graph and run records · spec:consumers.spec-studio.data.inputs"]
  n2["A corpus checks the register tokens its prose cites · spec:validation.external-registers"]
  n3["An outside register is a named Studio input, so a cited token links to its entry · spec:consumers.spec-studio.register-input"]
  n3 -->|"refines · declared"| n0
  n3 -->|"dependsOn · declared — the register joins the base graph and the run records as a named input"| n1
  n3 -->|"dependsOn · declared — the input is the register file and pattern the external-registers recipe already reads"| n2

Rests on

refines · spec:consumers.spec-studio · stated ready, floor ready
dependsOn · spec:consumers.spec-studio.data.inputs · stated ready, floor ready
dependsOn · spec:validation.external-registers · 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 Studio reads two named inputs beside the graph, a base graph and run records `spec:consumers.spec-studio.data.inputs` · resolves	declared	the register joins the base graph and the run records as a named input	None
dependsOn · outgoing	A corpus checks the register tokens its prose cites `spec:validation.external-registers` · resolves	declared	the input is the register file and pattern the external-registers recipe already reads	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.