The Protocol's roadmap
pack:roadmapspecs/roadmap.pack.sdp.mdDownload this Pack as one file
Where the design stands
- 4 members in priority order; no unresolved members.
- 1 member held below their stated next rung: An outside register is a named Studio input, so a cited token links to its entry (1 unmet clause).
- 2 members waiting only for their author's statement: The Protocol removes its frozen plans, review reports and superseded concept material, A pinned declaration shows the words of each test line that cites it.
- 1 design entry and no pinned declarations.
- 4 open questions and 3 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
Outlined diagonal: matches. Right of diagonal: floor above statement. Left of diagonal: statement above floor.
Maturity map as text
stated idea, floor scoped · 1 member
- The Protocol removes its frozen plans, review reports and superseded concept material ·
spec:protocol.delivery-record-cleanup· idea floor scoped
stated scoped, floor scoped · 1 member
- 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 scoped, floor ready · 1 member
- A pinned declaration shows the words of each test line that cites it ·
spec:consumers.spec-studio.cited-line-text· scoped floor ready
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.
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
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 scoped · next rung scoped: nothing blocks · 1 open, 1 blocking questions · implementation binding none · verifier binding none
spec:protocol.delivery-record-cleanup
Next rung scoped: nothing blocks; it waits only for the author's statement.
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 inplans/,reviews/and the concept documents does no Spec, test, decision or recipe carry yet, and where does each piece belong?Decider: ownerProvisional: the owner accepted the whole-repository review's measured inventory, with its row rulings, as the answer; the question leaves the Spec when the cleanup arc lands that inventory in its first commit
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 ready · next rung defined: nothing blocks · 0 open, 0 blocking questions · implementation binding none · verifier binding none
spec:consumers.spec-studio.cited-line-text
Next rung defined: nothing blocks; it waits only for the author's statement.
Design
1 design entry · no pinned declarations
Open questions
None.
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 optionaltitleand an optionalhrefon a token object; the Studio writes one page per register listing each token with its title, retired tokens marked, each linking to itshrefwhen 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=PATHwith 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
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:65· role service · component component:protocol.studio-elements· layer edge · context protocolimpl: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)
Rested on by (7)
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.