Spec Studio

HQ's plan for all software delivery is an SDP corpus in a small repository of its own

spec:decisions.sdp-holds-the-planDecision Record · featuredefined floor ready

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

Packs: none

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

Findings: no errors, no warnings

design/hq/decisions/sdp-holds-the-plan.sdp.md

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

Intent
outcome
Decide what carries HQ's plan for all software delivery and which repository holds it.
Decision
context
The recovery's master plan grew to 537 lines beside about a hundred briefs, with status copied everywhere and little delivered. SDP covers Specs from idea to implemented and derives what comes next from one graph. At the start of 30 October the owner thought SDP too early, because Kontrapunkt will be the chief of staff with all the private data. By 10:34 UTC the owner ruled that HQ's plan should definitely be managed by SDP, while doubting direct self-hosting, having bootstrapped it twice and found it too meta, and asked for a small repository outside the project suite.
decision
HQ's plan for all software delivery is the SDP corpus of this repository, a small plain adopter that pins SDP and holds Specs and nothing else. It sits outside the system being bootstrapped, and it is not part of Kontrapunkt.
rationale
  • Hard to reverse: every session HQ starts reads its work from here. Surprising without context: the plan does not sit with the private context, nor with the protocol that carries it. A real trade-off: the plan loses direct sight of Kontrapunkt's private facts and gains a corpus a blank session can read, with no self-hosting loop.
alternatives
  • Keep a master plan document in Kontrapunkt: it is what grew to 537 lines and could not be followed.
  • Bootstrap HQ while keeping its delivery plan inside the system being bootstrapped: the owner described two self-hosting attempts as too meta and proposed a small separate repository.
  • Adopt SDP inside Kontrapunkt: it is too early there, and the corpus would sit beside all of the private data.
consequences
  • AGENTS.md states what this repository is, and it holds no tools, skills of its own, plans, briefs or status files.
  • Roadmap order is advisory and read with the roadmap recipe, and a pull request's description carries the arc's record.
  • Client facts stay in Kontrapunkt, and a Spec here names a client by its slug only.
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:decisions.sdp-holds-the-plan

Arrows: refines (declared).

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 · declared Spec
  • spec:hq.delivery-planning: SDP carries delivery planning across projects · declared Spec
  • 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 and chosen syntax: requirementDiagram; exact refines, satisfies and verifies, with claim words in nodes and per-edge comments.

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:decisions.sdp-holds-the-plan
  • 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: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 decidedBy spec:decisions.sdp-holds-the-plan · declared — the ruling makes SDP the carrier of all of HQ's delivery planning
  • spec:hq.headquarters decidedBy spec:decisions.sdp-holds-the-plan · declared — sets where the plan lives and what reads it
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

Relations

Relation and directionOther endClaimReasonExercised keys
refines · outgoingSDP carries delivery planning across projects
spec:hq.delivery-planning · resolves		declaredsettles what carries HQ's plan and where it sitsNone
decidedBy · incomingSDP carries delivery planning across projects
spec:hq.delivery-planning · resolves		declaredthe ruling makes SDP the carrier of all of HQ's delivery planningNone
decidedBy · incomingHQ plans and designs across every project, and starts the engineering work
spec:hq.headquarters · resolves		declaredsets where the plan lives and what reads itNone

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.