Spec Studio

SDP carries delivery planning across projects

spec:hq.delivery-planningUse Case / Behavior · featuredefined floor ready

Next rung ready: nothing blocks; it waits only for the author's statement.

Packs: pack:hq-roadmap

Design: no design entries · no pinned declarations · 1 decision

Findings: no errors, no warnings

specs/hq/delivery-planning.sdp.md

No open questions and no blocking questions; implementation binding none, verifier binding none, and expected-outcome oracle none.

Specs cover the path from idea to implemented, so SDP can be instantiated to cover the software delivery views of every project. A project adopts it as this repository does, by pinning it and writing Specs. What no single corpus gives is the view across projects.

Intent
actor
The owner, reading across projects from HQ.
problem
About fifty projects each hold their own plan, or none, and nothing shows them together.
outcome
Every project that needs it manages its delivery in its own SDP corpus, and HQ reads across them through projections.
Behavior
rule.sdpPerProject line 29 · specs/hq/delivery-planning.sdp.md:29
Any project can adopt SDP to manage its own delivery, from idea to implemented.

no example exercises it

rule.crossProjectProjections line 30 · specs/hq/delivery-planning.sdp.md:30
The cross-project view is a read-time projection over each corpus's graph, heuristic first, with LLM-powered projections on top.

no example exercises it

rule.sdpInSdp line 31 · specs/hq/delivery-planning.sdp.md:31
SDP's own development stays in SDP's repository, and this corpus names that work in prose.

no example exercises it

rule.readByScript line 32 · specs/hq/delivery-planning.sdp.md:32
Agents read the graph by scripting it, beside grep and their other tools, and the plan asks SDP for no fixed set of verbs.

no example exercises it

0 unkeyed rules.

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:hq.delivery-planning

Arrows: refines (declared).

The diagram as text
  • spec:hq.delivery-planning: SDP carries delivery planning across projects · declared Spec · no satisfying binding
  • spec:decisions.sdp-holds-the-plan: HQ's plan for all software delivery is an SDP corpus in a small repository of its own · declared Spec
  • spec:hq.headquarters: HQ plans and designs across every project, and starts the engineering work · declared Spec
  • spec:decisions.sdp-holds-the-plan refines spec:hq.delivery-planning · declared — settles what carries HQ's plan and where it sits
  • spec:hq.delivery-planning refines spec:hq.headquarters · declared — one of the aspects the owner names
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.

Decisions

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:hq.delivery-planning
  • E2: decidedBy · declared — the ruling makes SDP the carrier of all of HQ's delivery planning
The diagram as text
  • spec:decisions.sdp-holds-the-plan: HQ's plan for all software delivery is an SDP corpus in a small repository of its own
  • spec:hq.delivery-planning: SDP carries delivery planning across projects
  • spec:hq.headquarters: HQ plans and designs across every project, and starts the engineering work
  • spec:hq.session-handoff: HQ hands a settled piece to a detailed session
  • spec:hq.delivery-planning decidedBy spec:decisions.sdp-holds-the-plan · declared — the ruling makes SDP the carrier of all of HQ's delivery planning
  • spec:hq.delivery-planning dependsOn spec:hq.session-handoff · declared — a project joins the plan through a detailed session started in it
  • spec:hq.delivery-planning refines spec:hq.headquarters · declared — one of the aspects the owner names
  • spec:decisions.sdp-holds-the-plan refines spec:hq.delivery-planning · declared — settles what carries HQ's plan and where it sits
Mermaid source

Copyable source; the Studio draws static SVG.

Preferred syntax: flowchart. Chosen syntax: labelled flowchart, preserving exact relations, claims and folds.

Rests on

Rested on by

Distance 1

Distance 2

Distance 3

Distance 4

Relations

Relation and directionOther endClaimReasonExercised keys
decidedBy · outgoingHQ's plan for all software delivery is an SDP corpus in a small repository of its own
spec:decisions.sdp-holds-the-plan · resolves		declaredthe ruling makes SDP the carrier of all of HQ's delivery planningNone
dependsOn · outgoingHQ hands a settled piece to a detailed session
spec:hq.session-handoff · resolves		declareda project joins the plan through a detailed session started in itNone
refines · outgoingHQ plans and designs across every project, and starts the engineering work
spec:hq.headquarters · resolves		declaredone of the aspects the owner namesNone
refines · incomingHQ's plan for all software delivery is an SDP corpus in a small repository of its own
spec:decisions.sdp-holds-the-plan · resolves		declaredsettles what carries HQ's plan and where it sitsNone

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.