The diff page shows what changed in the design since a base graph

outcome

Let a person read, from a link, what changed in the design between a base graph the build was given and the graph it built, down to each entry.

rule.onlyWithBase line 22 · specs/consumers/spec-studio.diff-page.sdp.md:22

The page set holds diff.html only when the build was given a base graph; without one, no page, link or change note names a diff.

no example exercises it

rule.namesTheBase line 23 · specs/consumers/spec-studio.diff-page.sdp.md:23

The page opens by naming its input: the base graph, its label when the build was given one, its schema version and its Spec count beside the built graph's, and a sentence that the comparison reads the two graphs only.

no example exercises it

rule.diffSections line 24 · specs/consumers/spec-studio.diff-page.sdp.md:24

The page renders recipe 35's answer with detail: true over the whole corpus, in sections in this order: the totals as sentences; the Specs added, linked; the Specs removed, as their ids in text, since no page holds them; the Specs changed, each linked, with each changed part, its change in words, and for a changed value the base value and the built value as readable text blocks or lists, one above the other, never a raw JSON array; keyed changes list in the head's rule and flow order, each as one line with the entry's text rendered as on its Spec page beside its old and new address or none; the Packs whose membership, order or order meaning changed, an added Pack whose order is priority read as added as a roadmap, its added members in manifest order, a removed Pack whose order was priority read as removed as a roadmap, and a known change to priority read as now a roadmap or from priority as no longer a roadmap, stating the before and after order values for other changes of meaning; the bindings changed, kept apart and headed as derived from anchors; and the diagnostics.

spec:consumers.spec-studio.diff-page.changed-entry · enabled

rule.specChangeNotes line 25 · specs/consumers/spec-studio.diff-page.sdp.md:25

Given a base graph, each changed Spec's page adds a line under its header that names the base input, counts keyed parts apart as <n> rules keyed, wording unchanged beside any other changed parts it lists, and links to its row on the diff page; each added Spec's page says it is new since the base.

spec:consumers.spec-studio.diff-page.changed-entry · enabled

rule.packChangeNotes line 26 · specs/consumers/spec-studio.diff-page.sdp.md:26

Given a base graph, each Pack page adds a Changed since the base section after its maturity map, from recipe 35's answer for that Pack, listing its changed and added members, linked, and its own membership change, with the same roadmap and order-meaning wording as the diff page; a member whose only changes are keying is marked keyed only.

no example exercises it

rule.confersNothing line 27 · specs/consumers/spec-studio.diff-page.sdp.md:27

The page and the change notes state differences between two graphs and confer nothing: no approval, staleness or readiness, and no record that a design pass happened.

no example exercises it

0 unkeyed rules.

Verifying examples

Given a base graph in which the Design entry {key: "limit"} of a Spec reads {before: "ten items"}
Given the built graph in which that entry reads {after: "twenty items"}
When the build renders the diff page
Then the Spec's row shows the base value {baseShown: "ten items"} and the built value {nowShown: "twenty items"}
Then the Spec's page carries the changed-since-base line: {changeNote: true}

Example space

Given a base graph in which the Design entry {key:string} of a Spec reads {before:string}
Given the built graph in which that entry reads {after:string}
When the build renders the diff page
Then the Spec's row shows the base value {baseShown:string} and the built value {nowShown:string}
Then the Spec's page carries the changed-since-base line: {changeNote:boolean}

baseLine line 30 · specs/consumers/spec-studio.diff-page.sdp.md:30

Compared with the base graph <label>, schema <version>, <n> Specs; the built graph has schema <version>, <m> Specs., the label left out when none was given.

changedSpec line 31 · specs/consumers/spec-studio.diff-page.sdp.md:31

the title linked, the id as code, then one row per part: the part as code, its change in words, keyed changes in the head's rule and flow order, each as one line with the entry's text rendered as on its Spec page beside Base and Now addresses or none, and for a changed value two labelled blocks, Base and Now, holding readable text or lists without a raw JSON array; the block's element id is the Spec's id, which the Spec page's change note links to.

bindingRow line 32 · specs/consumers/spec-studio.diff-page.sdp.md:32

the Spec linked, then for implementing units, referencing units, enabled verifiers and delivery facts the ids added and removed, under the heading Bindings, derived from anchors.

changeNote line 33 · specs/consumers/spec-studio.diff-page.sdp.md:33

Changed since the base graph <label>: followed by <n> rules keyed, wording unchanged when any parts are keyed, using rule for one, beside the other changed parts as code, linked to the Spec's row on the diff page.

Verifier bindings

• spec:consumers.spec-studio.diff-page.changed-entry · The diff page shows a changed entry's base and built values · declared · example enabled · specs/consumers/spec-studio.diff-page.changed-entry.sdp.md

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

  Test anchors: test:protocol.studio-diff-changed-entry, test:protocol.studio-glossary-same-word-twice, test:protocol.studio-navigation, test:protocol.studio-queue-dependency-first, test:protocol.studio-registers-blocking-first. Specs verified by those bindings: spec:consumers.spec-studio.diff-page, spec:consumers.spec-studio.diff-page.changed-entry, spec:consumers.spec-studio.glossary-page, spec:consumers.spec-studio.glossary-page.same-word-twice, spec:consumers.spec-studio.navigation, spec:consumers.spec-studio.owner-queue, spec:consumers.spec-studio.owner-queue.dependency-first, spec:consumers.spec-studio.registers, spec:consumers.spec-studio.registers.blocking-first.

  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	The questions page lists the Specs with a blocking question first (spec:consumers.spec-studio.registers.blocking-first)	passed	37.62 ms
  executes the bound example against a fresh world	The owner queue lists a waiting statement after the one it rests on (spec:consumers.spec-studio.owner-queue.dependency-first)	passed	24.75 ms
  executes the bound example against a fresh world	The diff page shows a changed entry's base and built values (spec:consumers.spec-studio.diff-page.changed-entry)	passed	22.28 ms
  executes the bound example against a fresh world	A word two Specs define appears once per Spec on the glossary page (spec:consumers.spec-studio.glossary-page.same-word-twice)	passed	11.45 ms
  renders declaration citations, decision reasons and design backlog from the shipped answers	Studio register pages	passed	39.22 ms
  reaches each page in order, marks it current and omits every diff reference without a base	Studio register pages	passed	6.54 ms
  refuses malformed base flags and unreadable JSON before extraction	Studio register pages	passed	1.23 ms
  refuses a base in generated output before writing through graph	Studio base comparison	passed	15.97 ms
  refuses a base in generated output before writing through nested	Studio base comparison	passed	28 ms
  refuses a base in generated output before writing through file alias	Studio base comparison	passed	15.08 ms
  refuses a base in generated output before writing through root alias	Studio base comparison	passed	6.55 ms
  refuses a base in generated output before writing through input alias	Studio base comparison	passed	9.33 ms
  renders only existing sides for added and removed entries and one value for moved entries	Studio base comparison	passed	12.09 ms
  shows per-Pack diagnostics without no-change claims for invalid graph	Studio base comparison	passed	18.4 ms
  shows per-Pack diagnostics without no-change claims for different schema	Studio base comparison	passed	16.77 ms
  keeps additions, removals, Pack order and anchor bindings apart and escapes compared values	Studio base comparison	passed	30.65 ms
  shows unreadable graph values as the recipe's diagnostics on the named diff page	Studio base comparison	passed	3.27 ms
  leaves the base file unchanged and certifies repeat publication with the same input	Studio base comparison	passed	39.36 ms
  keeps a cycle's round separate from statements that rest on nothing, and lists owner holds	Studio base comparison	passed	11.47 ms
  sorts terms without locale collation and keeps non-letter headings addressable	Studio base comparison	passed	5.22 ms
  orders queue floor options by rung and carries the Pack and floor on each row	Studio base comparison	passed	19.62 ms
  uses authored term keys and orders duplicate terms by Spec id	Studio base comparison	passed	5.83 ms
  reads each owner question's provisional reading from its reader Spec and key	not recorded	passed	7.54 ms
  renders a keying proposal as one line per keyed entry and readable changed rule text	not recorded	passed	7.28 ms
  lists keyed lines in head rule order with rendered text for added, renamed and removed keys	not recorded	passed	15.17 ms
  counts keyed rules apart from changed parts, mixed changes: false	not recorded	passed	6.13 ms
  counts keyed rules apart from changed parts, mixed changes: true	not recorded	passed	5.87 ms
  names one keyed rule in the singular	not recorded	passed	11.75 ms
  marks only members with exclusively keyed changes as keyed only	not recorded	passed	16.34 ms
  renders changed list values as lists instead of raw JSON arrays	not recorded	passed	5.82 ms
  retains the owning list when readable rule text moves to a flow	not recorded	passed	5.4 ms

• test:protocol.roadmap-priority · checks Pack priority extraction, comparison and Studio change notes · anchored · test anchor binding present · test/roadmap-priority.test.ts:44

  External run evidence from test/roadmap-priority.test.ts

  Test anchors: test:protocol.roadmap-priority. Specs verified by those bindings: spec:carrier.markdown-pack-authoring, spec:consumers.design-diff, spec:consumers.spec-studio.diff-page, spec:consumers.spec-studio.pack-page, spec:extraction.pack-member-order, spec:model.pack-aggregate.

  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
  derives equal Markdown and TypeScript Pack nodes and edges, serializes order last, and exposes it through the reader	roadmap priority manifest	passed	47.3 ms
  refuses the invalid Markdown value reading	roadmap priority manifest	passed	1.58 ms
  refuses the invalid Markdown value arbitrary	roadmap priority manifest	passed	1.33 ms
  refuses the invalid Markdown value true	roadmap priority manifest	passed	1.28 ms
  refuses the invalid Markdown value null	roadmap priority manifest	passed	1.65 ms
  refuses the invalid Markdown value []	roadmap priority manifest	passed	1.21 ms
  refuses the invalid Markdown value {}	roadmap priority manifest	passed	1.24 ms
  refuses the invalid TypeScript value "reading"	roadmap priority manifest	passed	3.6 ms
  refuses the invalid TypeScript value "arbitrary"	roadmap priority manifest	passed	2.76 ms
  refuses the invalid TypeScript value true	roadmap priority manifest	passed	3.43 ms
  refuses the invalid TypeScript value null	roadmap priority manifest	passed	3.5 ms
  refuses the invalid TypeScript value []	roadmap priority manifest	passed	2.87 ms
  refuses the invalid TypeScript value {}	roadmap priority manifest	passed	3.83 ms
  refuses the invalid TypeScript value undefined	roadmap priority manifest	passed	2.78 ms
  refuses the invalid TypeScript value chosenOrder	roadmap priority manifest	passed	3.35 ms
  names a removed Pack by its order meaning (priority true)	roadmap priority design diff	passed	14.29 ms
  names a removed Pack by its order meaning (priority false)	roadmap priority design diff	passed	12.82 ms
  names an added roadmap and preserves manifest order in its member delta	roadmap priority design diff	passed	17.33 ms
  labels Pack membership by its order meaning (priority true)	roadmap priority design diff	passed	8.11 ms
  labels Pack membership by its order meaning (priority false)	roadmap priority design diff	passed	5.46 ms
  states order values when a change is not a known roadmap transition	roadmap priority design diff	passed	4.7 ms
  documents the order comparison fields, default and diagnostic in the recipe contract	roadmap priority design diff	passed	1.09 ms
  compares a priority transition to true without a membership edit	roadmap priority design diff	passed	3.05 ms
  compares a priority transition to false without a membership edit	roadmap priority design diff	passed	2.22 ms
  reads an absent order as reading order in a base schema that predates the field	roadmap priority design diff	passed	7.31 ms
  marks the absent side of an added or removed roadmap as null (true)	roadmap priority design diff	passed	2.44 ms
  marks the absent side of an added or removed roadmap as null (false)	roadmap priority design diff	passed	2.06 ms
  diagnoses an unknown order at the base without reporting an order change	roadmap priority design diff	passed	1.69 ms
  diagnoses an unknown order at the head without reporting an order change	roadmap priority design diff	passed	1.71 ms
  still compares membership and member order when the base order is unknown	roadmap priority design diff	passed	2.58 ms
  still compares membership and member order when the head order is unknown	roadmap priority design diff	passed	6.34 ms
  keeps an order-only change in the selected Pack's comparison scope	roadmap priority design diff	passed	3.01 ms
  shows no roadmap transition for a membership-only change (priority true)	roadmap priority design diff	passed	7.93 ms
  shows no roadmap transition for a membership-only change (priority false)	roadmap priority design diff	passed	6.63 ms
  shows the roadmap transition to true on the diff and Pack pages	roadmap priority design diff	passed	8.43 ms
  shows the roadmap transition to false on the diff and Pack pages	roadmap priority design diff	passed	6.96 ms

Requirement drawing

Decisions

No decision record named.

• 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-diff · renders declared design changes and binding changes separately · src/projections/studio/pages/diff-page.ts:91

  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.