A Spec page shows one Spec in collapsible panels, in a fixed order

outcome

Show everything the graph holds about one Spec on one page, in panels a person opens and closes one at a time.

rule line 42 · specs/consumers/spec-studio.spec-page.sdp.md:42

Each panel collapses and expands on its own.

rule line 43 · specs/consumers/spec-studio.spec-page.sdp.md:43

The page's core, its header, sections, relations, bindings and findings, is the one spec:consumers.spec-studio.spec-page.core states, and the panels below add to it.

rule.sourceText line 44 · specs/consumers/spec-studio.spec-page.sdp.md:44

Every Spec and Pack a panel names links to its page. A code unit, component or anchor shows its id and its recorded repository-relative file and line as text, with an action that copies file:line; the page set holds no code-unit page and writes no editor URI, absolute path or assumed source URL; a recorded file and line become a link only when a stamp beside the page set names a source template, as spec:consumers.spec-studio.sharing states; a component's attributes, members and uses show in the architecture lens, which its id links to.

no example exercises it

rule.panelOrder line 45 · specs/consumers/spec-studio.spec-page.sdp.md:45

After the core's sections the page adds five panels, in this order, each open by default: Verification, Design view, Runtime, Evidence and Impact; a panel with nothing to show says so in one sentence and stays in its place; the core's relations, bindings and findings follow them.

no example exercises it

rule.sectionAdditions line 46 · specs/consumers/spec-studio.spec-page.sdp.md:46

Inside the core's sections the page adds a composing action beside each keyed entry that proposes new text for it, the composing actions beside each open question, the rule coverage beside each keyed rule or flow and the example cards after the rules, each constraint's target, the citations beside each cited entry, and an element id on each keyed term, as the rules below state.

no example exercises it

rule.termIds line 47 · specs/consumers/spec-studio.spec-page.sdp.md:47

Each keyed Model term in the core's Model section carries the element id term.<key>, its address after the #, and shows its key and its recorded line, as the core's entry ids do.

no example exercises it

rule.citations line 48 · specs/consumers/spec-studio.spec-page.sdp.md:48

Beside each keyed entry an anchored source file cites, its section lists every citing file and line recipe 51 records, as text with a copy action; a pinned declaration no file cites reads no citation recorded.

spec:consumers.spec-studio.spec-page.cited-declaration · enabled

rule.designView line 49 · specs/consumers/spec-studio.spec-page.sdp.md:49

The Design view panel draws the requirement drawing defined by spec:consumers.spec-studio.diagram-kinds.requirement-trace in place of realization, then lists the decision records the Spec names through decidedBy with linked titles and decision text inline. The Runtime panel retains the implementation anchors' components and uses.

no example exercises it

rule.runtime line 50 · specs/consumers/spec-studio.spec-page.sdp.md:50

The Runtime panel shows the structural neighborhood of the Spec's implementation anchors: each anchor's component with its layer and context, and the units it uses, each with its file and line; runtime observation reads not tracked.

no example exercises it

rule.impact line 51 · specs/consumers/spec-studio.spec-page.sdp.md:51

The Impact panel draws the Spec's trace graph, one hop each way, and then lists what it rests on with each target's stated and derived rung, from recipe 21, and every Spec that rests on it to any depth, by distance, with the units, enabled verifiers and Packs each brings, from recipe 30.

no example exercises it

rule.diffChangeNote line 52 · specs/consumers/spec-studio.spec-page.sdp.md:52

Given a base graph, a line under the header names the base and lists the Spec's changed parts, as spec:consumers.spec-studio.diff-page states.

no example exercises it

2 unkeyed rules.

Verifying examples

Given a Spec with two pinned declarations, the first of which an anchored test file {file: "test/orders.test.ts"} cites at line {line: 12}
When the build renders the Spec's page
Then beside the first declaration the page lists {cited: "test/orders.test.ts:12"}
Then beside the second declaration the page reads {uncited: "no citation recorded"}

Example space

Given a Spec with two pinned declarations, the first of which an anchored test file {file:string} cites at line {line:number}
When the build renders the Spec's page
Then beside the first declaration the page lists {cited:string}
Then beside the second declaration the page reads {uncited:string}

The panels the core does not hold, in page order.

entryAction line 56 · specs/consumers/spec-studio.spec-page.sdp.md:56

beside each keyed entry, an action that composes intent proposing new text for it, with the entry's address as the change's scope and as the address it replaces.

intentActions line 57 · specs/consumers/spec-studio.spec-page.sdp.md:57

beside each open question, actions that compose intent to resolve it or to promote it to a decision record.

behaviorAdditions line 58 · specs/consumers/spec-studio.spec-page.sdp.md:58

beside each keyed rule or flow, its exercising examples as spec:consumers.spec-studio.verification-panels lays them out, then the example cards and unwritten example cards.

constraintsAdditions line 59 · specs/consumers/spec-studio.spec-page.sdp.md:59

each constraint with its target, laid out as spec:consumers.spec-studio.verification-panels states.

citationList line 60 · specs/consumers/spec-studio.spec-page.sdp.md:60

under a cited entry, Cited at and each citing file and line with a copy action, the citing anchor's id as code when the citation names one.

verificationPanel line 61 · specs/consumers/spec-studio.spec-page.sdp.md:61

the verifier list, with run evidence given run records, then the coverage grid when the Spec owns an example space, laid out as spec:consumers.spec-studio.verification-panels states; the panel's element id is panel.verification.

designViewPanel line 62 · specs/consumers/spec-studio.spec-page.sdp.md:62

The requirement drawing, with the text equivalent naming each binding's id, source file and line under the source-text rule, then the decision records and their decision text; its element id remains panel.design-view.

runtimePanel line 63 · specs/consumers/spec-studio.spec-page.sdp.md:63

the structural neighborhood of the Spec's implementation anchors, each anchor's component and the code units it uses, with file and line, then Runtime observation: not tracked; the panel's element id is panel.runtime.

evidencePanel line 64 · specs/consumers/spec-studio.spec-page.sdp.md:64

the evidence fields and absence labels spec:consumers.spec-studio.verification-panels states, with no invented build, deployment, measurement or bill-of-materials data; the panel's element id is panel.evidence.

impactPanel line 65 · specs/consumers/spec-studio.spec-page.sdp.md:65

the trace graph, then Rests on and Rested on by lists, the second grouped by distance, each row with its units, enabled verifiers and Packs; the panel's element id is panel.impact.

Verifier bindings

• spec:consumers.spec-studio.spec-page.cited-declaration · A pinned declaration shows the test line that cites it · declared · example enabled · specs/consumers/spec-studio.spec-page.cited-declaration.sdp.md

  External run evidence from test/studio-s2.test.ts

  Test anchors: test:protocol.studio-cited-declaration, test:protocol.studio-panels, test:protocol.studio-rule-coverage. Specs verified by those bindings: spec:consumers.spec-studio.pack-page.maturity-map, spec:consumers.spec-studio.spec-page, spec:consumers.spec-studio.spec-page.cited-declaration, spec:consumers.spec-studio.verification-panels, spec:consumers.spec-studio.verification-panels.rule-coverage.

  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

  Name	Suite	Result	Duration
  marks every displayed file and line across the Studio page set for source links	not recorded	passed	109.94 ms
  renders citation labels consistently on Spec and declaration pages	not recorded	passed	39.55 ms
  executes the bound example against a fresh world	A pinned declaration shows the test line that cites it (spec:consumers.spec-studio.spec-page.cited-declaration)	passed	12.75 ms
  executes the bound example against a fresh world	Each keyed rule shows the examples that exercise it, or that none does (spec:consumers.spec-studio.verification-panels.rule-coverage)	passed	16.15 ms
  renders the five open panels in order, the space, bound values, absent evidence, and empty composing slots	Spec panels	passed	14.06 ms
  gives keyed terms address ids, source lines, and citations while hiding termKeys metadata	Spec panels	passed	15.16 ms
  places resolved Pack members in stated/floor cells in authored order	Spec panels	passed	22.35 ms
  keeps the maturity heading and axis explanations inside the embeddable element	Spec panels	passed	20.36 ms
  distinguishes test lines from citations by files with unrelated anchors	Spec panels	passed	21.31 ms
  renders composing slots beside unkeyed questions using the Spec scope	Spec panels	passed	14.33 ms
  keeps the unbound-verifier sentence to graph bindings without run input	Spec panels	passed	19.45 ms
  renders source locations, component links, decisions and transitive impact by distance	Structural panels and targets	passed	30.62 ms
  states absence on unwritten examples and unset constraint targets	Structural panels and targets	passed	22.85 ms
  labels a keyed rule's unbound example as not enabled	Structural panels and targets	passed	10.05 ms
  renders structure from recipe answers and reader records without exposing raw graph data	Structural panels and targets	passed	19.72 ms
  renders verifying examples for a Model without Behavior and keeps short cards to their summary	not recorded	passed	10.67 ms
  keeps example steps and composing actions outside a short Spec card	not recorded	passed	18.09 ms
  keeps trace and requirement description and arrow ids distinct for one Spec subject	not recorded	passed	15.14 ms

• test:protocol.studio-architecture-maturity-requirement · anchored · test anchor binding present · test/studio-panels.test.ts:35

  External run evidence from test/studio-panels.test.ts

  Test anchors: test:protocol.studio-architecture-maturity-requirement. Specs verified by those bindings: spec:consumers.spec-studio.diagram-kinds.maturity-picture, spec:consumers.spec-studio.diagram-kinds.requirement-trace, spec:consumers.spec-studio.lenses.architecture, spec:consumers.spec-studio.lenses.architecture.unit-register, spec:consumers.spec-studio.pack-page.maturity-map, spec:consumers.spec-studio.spec-page.

  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

  Name	Suite	Result	Duration
  orders both matrix axes by layer and id, links counts to supporting unit edges and keeps zeros compact	architecture tables and register	passed	73.28 ms
  groups unfamiliar and omitted roles in code-unit order, with source rows and separate binding lists	architecture tables and register	passed	32.56 ms
  draws equal categorical cells, exact counts and marks with ordered complete lists and unresolved members apart	maturity picture	passed	46.28 ms
  places the map inside the page's expander so a cell link opens its member list	maturity picture	passed	24.84 ms
  puts a uniform map behind a closed disclosure and uses solid fill above the mark bound	maturity picture	passed	392.9 ms
  selects the subject, refiners and verifying examples and keeps declared and anchored claims separate	requirement drawing	passed	36.4 ms
  keeps a refining verifier in the examples band and outside Specs apart	requirement drawing	passed	12.74 ms
  offers requirement syntax for the supported exact relation subset	requirement drawing	passed	16.94 ms
  counts the subject example when reporting selected verifying examples	requirement drawing	passed	8.34 ms
  folds the largest exact relation group deterministically and keeps every original binding in text	not recorded	passed	5.8 ms
  keeps a sparse large uses matrix readable with one visible zero legend and hidden cell words	not recorded	passed	20.31 ms
  contains the matrix's hidden cell words inside their scroll region	not recorded	passed	0.45 ms
  does not assert missing bindings on a boundary Spec whose bindings are outside the selected set	not recorded	passed	9.66 ms
  lets full component ids wrap so every uses column fits the printed page	not recorded	passed	0.6 ms
  keeps roles out of the pinned search record while preserving them on graph units	not recorded	passed	3.09 ms
  lists a unit whose recorded component is missing in No component and in unresolved structure	not recorded	passed	4.13 ms
  uses the singular member in a one-member Pack's uniform sentence	not recorded	passed	8.24 ms
  states each absent requirement band without implying that a populated drawing is missing	not recorded	passed	5.2 ms
  breaks equal requirement fold groups by 'kind' in lexical order	not recorded	passed	3.58 ms
  breaks equal requirement fold groups by 'direction' in lexical order	not recorded	passed	2.34 ms
  breaks equal requirement fold groups by 'claim' in lexical order	not recorded	passed	1.14 ms
  offers only the active relation and member renderers after requirement replaces realization	not recorded	passed	0.26 ms
  applies the closed-source print rule to both requirement and maturity drawings	not recorded	passed	0.29 ms

• test:protocol.studio-panels · anchored · test anchor binding present · test/studio-s2.test.ts:256

Requirement drawing

Decisions

• The Design Review renders open-section entries as a list

  The Design Review renders each entry of a design or ui section as a list item in authored order, its key as inline code. A string value renders as Markdown text through the prose escaping rule; a number or boolean renders as inline code; an array or object renders as a fenced JSON block nested under its item, so a structured value the TypeScript carrier admits survives without loss. The fenced-JSON rule of the Design Review stops covering an open section as a whole and keeps covering a structured value inside one entry. The freeze on the four shipped projections stands for everything else.

• component:protocol.projections · read-only output, layout and owned publication · src/projections/design-review.ts:29 · layer edge · context protocol

  Uses

  • component:protocol.extract · the carrier and source pipeline · src/extract/index.ts:192 · layer application · context protocol
  • component:protocol.graph · the one graph and its semantic decisions · src/graph/schema.ts:34 · layer domain · context protocol
  • component:protocol.model · the authored contracts and stable ids · src/model/anchors.ts:100 · layer domain · context protocol
  • component:protocol.notation · the leaf step codec · src/notation/slots.ts:261 · layer domain · context protocol
  • component:protocol.reader · the typed graph contract and body evaluator · src/reader/reader.ts:671 · layer application · context protocol
  • component:protocol.validate · one finding currency and ordered checks · src/validate/validators.ts:72 · layer domain · context protocol
• impl:protocol.studio-requirement-view · selects Spec refiners, verifying examples and their recorded bindings · src/projections/studio/pages/requirement-view.ts:8

  Component: component:protocol.projections · read-only output, layout and owned publication · src/projections/design-review.ts:29 · layer edge · context protocol

  Uses

  None.

• impl:protocol.studio-spec-page · renders Spec intent, relations and realization bindings · src/projections/studio/pages/spec-page.ts:201

  Component: component:protocol.projections · read-only output, layout and owned publication · src/projections/design-review.ts:29 · layer edge · context protocol

  Uses

  None.

• impl:protocol.studio-spec-structure · renders requirement and trace diagrams and the recorded structural neighborhood · src/projections/studio/pages/spec-structure.ts:44

  Component: component:protocol.projections · read-only output, layout and owned publication · src/projections/design-review.ts:29 · layer edge · context protocol

  Uses

  None.

Runtime observation: not tracked.

Runtime observation: not tracked.

Build attestations: not tracked.

Deployments: not tracked.

Bills of materials: not tracked.