Roadmap views read releases, baselines and phases from git and the graph

spec:consumers.projections-model.roadmap-views

Domain Model · storyscoped floor scoped

Changed since the base graph base da4b141: narrative; question.namedRoadmapReader; question.releaseReader; relation.dependsOn:spec:consumers.roadmap; statedReadiness; term.phase / iteration / milestone; term.roadmap

Base input: schema 0.11.0, 405 Specs.

Next rung defined waits on 1 unmet clause:

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

Packs: pack:roadmaps-and-slices-v1, pack:self-hosting-v1

Design: no design entries · no pinned declarations · no decisions

Findings: no errors, no warnings

specs/consumers/projections-model.roadmap-views.sdp.md

1 open question and 1 blocking question; implementation binding none, verifier binding none, and expected-outcome oracle none.

Release, baseline and roadmap vocabulary belongs to optional projections that wait until a reader needs them. The owner, choosing what the next pull requests take up, is the reader the roadmap view waited for, and the roadmap reading answers it: a Pack whose manifest states a priority order, read with what each entry still needs, shown on the Studio's roadmap page and rendered as a pull request's forward section. Release and baseline views still wait for a reader of their own.

Intent

outcome: Name the release, baseline and roadmap views a delivery reader may want, as optional projections that never gate or sequence work.

Open questions

blocking · question.releaseReader line 22 · specs/consumers/projections-model.roadmap-views.sdp.md:22 · Does a reader need release or baseline views that the roadmap, the recipes and git tags do not serve?Decider: ownerProvisional: Keep release and baseline views deferred; the trigger opens this question and does not authorize either view's build.Trigger: the first published release

Model

release line 29 · specs/consumers/projections-model.roadmap-views.sdp.md:29: A tagged set surfaced as a git-tag projection.
baseline line 30 · specs/consumers/projections-model.roadmap-views.sdp.md:30: A named approved snapshot whose signed git tag is the approval artifact, with approval remaining outside the authored model.
roadmap line 31 · specs/consumers/projections-model.roadmap-views.sdp.md:31: A Pack whose manifest states a priority order, read with what each entry still needs next; its order is an advisory preference, never a schedule or a gate.
phase / iteration / milestone line 32 · specs/consumers/projections-model.roadmap-views.sdp.md:32: Descriptive words a roadmap's framing may use, never an entry field, a date, a gate or an enforced sequence.

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.projections-model.roadmap-views

Arrows: refines (declared).

The diagram as text

spec:consumers.projections-model.roadmap-views: Roadmap views read releases, baselines and phases from git and the graph · declared Spec · no satisfying binding
spec:consumers.projections-model: Projections fan out from one graph without becoming truth stores · declared Spec
spec:consumers.projections-model.roadmap-views refines spec:consumers.projections-model · 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.projections-model.roadmap-views

requirementDiagram
  requirement n0 {
    text: "Roadmap views read releases, baselines and phases from git and the graph · declared Spec · no satisfying binding · spec:consumers.projections-model.roadmap-views"
  }
  requirement n1 {
    text: "Projections fan out from one graph without becoming truth stores · declared Spec · spec:consumers.projections-model"
  }
  %% 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.projections-model.roadmap-views

The diagram as text

spec:consumers.projections-model: Projections fan out from one graph without becoming truth stores
spec:consumers.projections-model.roadmap-views: Roadmap views read releases, baselines and phases from git and the graph
spec:consumers.roadmap: A roadmap orders the next bodies of work, and the graph says what each still needs
spec:consumers.projections-model.roadmap-views dependsOn spec:consumers.roadmap · declared — the roadmap view the owner asked for is the roadmap reading, its page and its memo
spec:consumers.projections-model.roadmap-views refines spec:consumers.projections-model · 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.projections-model.roadmap-views

flowchart TB
  n0["Projections fan out from one graph without becoming truth stores · spec:consumers.projections-model"]
  n1["A roadmap orders the next bodies of work, and the graph says what each still needs · spec:consumers.roadmap"]
  n2["Roadmap views read releases, baselines and phases from git and the graph · spec:consumers.projections-model.roadmap-views"]
  n2 -->|"refines · declared"| n0
  n2 -->|"dependsOn · declared — the roadmap view the owner asked for is the roadmap reading, its page and its memo"| n1

Rests on

refines · spec:consumers.projections-model · stated ready, floor ready
dependsOn · spec:consumers.roadmap · 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	A roadmap orders the next bodies of work, and the graph says what each still needs `spec:consumers.roadmap` · resolves	declared	the roadmap view the owner asked for is the roadmap reading, its page and its memo	None
refines · outgoing	Projections fan out from one graph without becoming truth stores `spec:consumers.projections-model` · 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.