The Protocol's roadmap

pack:roadmap

specs/roadmap.pack.sdp.md

Where the design stands

4 members in priority order; no unresolved members.
3 members held below their stated next rung: The Protocol removes its frozen plans, review reports and superseded concept material (1 unmet clause), A pinned declaration shows the words of each test line that cites it (1 unmet clause), An outside register is a named Studio input, so a cited token links to its entry (1 unmet clause).
No members waiting only for their author's statement.
No design entries and no pinned declarations.
6 open questions and 4 blocking questions.
No members with an implementation binding.
1 member with a design reference.
8 outside Specs the Pack rests on; 7 outside Specs rest on the Pack; no outside Specs verify it; no outside Specs supersede it.

Maturity map

Rows: stated readiness, idea to ready. Columns: floor reached, none to ready. Each mark counts one member; above 100 members a cell is solid. Floor none is distinct from idea.

Outlined diagonal: matches. Right of diagonal: floor above statement. Left of diagonal: statement above floor.

Maturity map as text

Counts by stated readiness and floor reached. To the right the floor exceeds the statement; to the left the statement exceeds the floor.
Stated rung / floor reached	floor none	floor idea	floor scoped	floor defined	floor ready
stated idea	—	1	—	—	—
stated scoped	—	—	2	—	—
stated defined	—	—	—	—	—
stated ready	—	—	—	—	1

stated idea, floor idea · 1 member

The Protocol removes its frozen plans, review reports and superseded concept material · spec:protocol.delivery-record-cleanup · idea floor idea

stated scoped, floor scoped · 2 members

A pinned declaration shows the words of each test line that cites it · spec:consumers.spec-studio.cited-line-text · scoped floor scoped
An outside register is a named Studio input, so a cited token links to its entry · spec:consumers.spec-studio.register-input · scoped floor scoped

stated ready, floor ready · 1 member

Views compose scoped intent instead of patching canonical source · spec:consumers.edit-model · ready floor ready

Mermaid source

Preferred syntax: block. Fixed categorical cells; membership appears in comments.

Mermaid source for maturity map

block-beta
  columns 6
  axis["Stated / floor"]
  h0["none"]
  h1["idea"]
  h2["scoped"]
  h3["defined"]
  h4["ready"]
  r0["idea"]
  c00["0"]
  c01["1"]
  %% diagram.pack:roadmap.maturity.cell.idea.idea: spec:protocol.delivery-record-cleanup · The Protocol removes its frozen plans, review reports and superseded concept material
  c02["0"]
  c03["0"]
  c04["0"]
  r1["scoped"]
  c10["0"]
  c11["0"]
  c12["2"]
  %% diagram.pack:roadmap.maturity.cell.scoped.scoped: spec:consumers.spec-studio.cited-line-text · A pinned declaration shows the words of each test line that cites it
  %% diagram.pack:roadmap.maturity.cell.scoped.scoped: spec:consumers.spec-studio.register-input · An outside register is a named Studio input, so a cited token links to its entry
  c13["0"]
  c14["0"]
  r2["defined"]
  c20["0"]
  c21["0"]
  c22["0"]
  c23["0"]
  c24["0"]
  r3["ready"]
  c30["0"]
  c31["0"]
  c32["0"]
  c33["0"]
  c34["1"]
  %% diagram.pack:roadmap.maturity.cell.ready.ready: spec:consumers.edit-model · Views compose scoped intent instead of patching canonical source
  %% Accessible count table: diagram.pack:roadmap.maturity.text

Framing

The Protocol's next work, first entry first. The order is a preference: it dates, gates and sequences nothing, and what each entry still needs is read from the graph each time.

First the cleanup that removes the frozen plans, review reports and superseded concept material, as the roadmap and the pull request record make possible. Then the two steps a reader of the Studio's pages could not take, the words of a test line that checks a declaration and an outside register's entries, and then the composed-intent model the build backlog holds. What the first adopter's mass update asks for joins when the owner selects it; a capture landing adds nothing here. An entry leaves by an edit to this manifest once its selected work is complete or no longer belongs among the next work.

Changed since the base

Compared with the base graph base b5e0a8b. Read the diff.

Base input: schema 0.12.0, 456 Specs.

Changed members

None.

Added members

None.

Pack membership

No membership or order change.

Members

1. The Protocol removes its frozen plans, review reports and superseded concept materialbehavior · idea floor idea · next rung scoped: waits on 1 unmet clause · 1 open, 1 blocking questions · implementation binding none · verifier binding none

spec:protocol.delivery-record-cleanup

Next rung scoped waits on 1 unmet clause:

kind-evidence-present · The kind's natural evidence is present (per-kind evidence table).

Design

No design entries · no pinned declarations

Decisions

Plan and review files stop carrying the delivery record once the roadmap and the pull request do · stated ready

Open questions

blocking · question.durableContent · line 23 · specs/protocol/delivery-record-cleanup.sdp.md:23 · Which content in plans/, reviews/ and the concept documents does no Spec, test, decision or recipe carry yet, and where does each piece belong?Decider: ownerProvisional: a measured inventory by the arc that removes them, reviewed before anything is deleted

Implementation binding: none

Design reference: none

Verifier binding: none

2. A pinned declaration shows the words of each test line that cites itbehavior · scoped floor scoped · next rung defined: waits on 1 unmet clause · 2 open, 1 blocking questions · implementation binding none · verifier binding none

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

Next rung defined waits on 1 unmet clause:

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

Design

No design entries · no pinned declarations

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

Implementation binding: none

Design reference: none

Verifier binding: none

3. An outside register is a named Studio input, so a cited token links to its entrybehavior · scoped floor scoped · next rung defined: waits on 1 unmet clause · 3 open, 2 blocking questions · implementation binding none · verifier binding none

spec:consumers.spec-studio.register-input

Next rung defined waits on 1 unmet clause:

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

Design

No design entries · no pinned declarations

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

Implementation binding: none

Design reference: none

Verifier binding: none

4. Views compose scoped intent instead of patching canonical sourcebehavior · ready floor ready · 0 open, 0 blocking questions · implementation binding none · verifier binding present

spec:consumers.edit-model

Design

No design entries · no pinned declarations

Open questions

None.

Implementation binding: none

Design reference: present

impl:protocol.studio-intent-panel · gathers ordered intents under the page-root storage key and partitions their hand-off · src/studio-elements/intent-panel.ts:51 · role service · component component:protocol.studio-elements · layer edge · context protocol
impl:protocol.studio-intent-panel-element · displays gathered requests and writes copy selections or local download links · src/studio-elements/intent-panel-element.ts:14 · role interaction · component component:protocol.studio-elements · layer edge · context protocol

Verifier binding: present

1 verifier, 1 enabled · no verifying examples, 0 enabled

Boundary

Rests on (8)

Spec	Stated rung	Implementation binding	Joined members
Projections fan out from one graph without becoming truth stores `spec:consumers.projections-model`	ready	present	refines: spec:consumers.edit-model
The Spec Studio is a static HTML workbench over the one graph `spec:consumers.spec-studio`	ready	present	refines: spec:consumers.spec-studio.cited-line-text, spec:consumers.spec-studio.register-input
The Studio reads two named inputs beside the graph, a base graph and run records `spec:consumers.spec-studio.data.inputs`	ready	present	dependsOn: spec:consumers.spec-studio.register-input
The corpus's registers are pages a reviewer opens from a link `spec:consumers.spec-studio.registers`	ready	present	dependsOn: spec:consumers.spec-studio.cited-line-text
Plan and review files stop carrying the delivery record once the roadmap and the pull request do `spec:decisions.roadmap-over-plans`	ready	none	decidedBy: spec:protocol.delivery-record-cleanup
The graph records where anchored source cites an entry address `spec:extraction.entry-citations`	ready	present	dependsOn: spec:consumers.spec-studio.cited-line-text
The Protocol reads its next work from its roadmap and keeps its delivery record in git and its pull requests `spec:protocol.roadmap-replaces-plans`	ready	present	refines: spec:protocol.delivery-record-cleanup
A corpus checks the register tokens its prose cites `spec:validation.external-registers`	ready	present	dependsOn: spec:consumers.spec-studio.register-input

Rested on by (7)

Spec	Stated rung	Implementation binding	Joined members
Authors move one Spec from intent to reviewed evidence `spec:consumers.authoring-on-ramp`	ready	present	dependsOn: spec:consumers.edit-model
Composed intent hands off on one proposal shape `spec:consumers.intent-composition`	ready	none	refines: spec:consumers.edit-model
A change proposal is addressed, based and checked before it lands `spec:consumers.intent-composition.proposal`	ready	present	dependsOn: spec:consumers.edit-model
A design pass is followed and answered from the vault `spec:consumers.obsidian-vault.iteration`	ready	present	dependsOn: spec:consumers.edit-model
The Spec Studio is a static HTML workbench over the one graph `spec:consumers.spec-studio`	ready	present	dependsOn: spec:consumers.edit-model
A composing panel on every page gathers scoped intent for an agent `spec:consumers.spec-studio.intent-panel`	ready	present	dependsOn: spec:consumers.edit-model
The upgrade kit shows a corpus what it could adopt `spec:consumers.upgrade-kit`	ready	present	dependsOn: spec:consumers.edit-model

Verified by (0)

None.

Superseded by (0)

None.

Members with no verifier binding

The graph records bindings and never runs. Decision records are left out: a decision never needs a verifier binding. The runs page, the tests lens and the Spec pages of the Specs their files verify show the run records as external evidence from test files.

The Protocol removes its frozen plans, review reports and superseded concept material · spec:protocol.delivery-record-cleanup · stated idea
A pinned declaration shows the words of each test line that cites it · spec:consumers.spec-studio.cited-line-text · stated scoped
An outside register is a named Studio input, so a cited token links to its entry · spec:consumers.spec-studio.register-input · stated scoped

Findings

None.

Composing (0)

Composing needs the script.