Spec Studio

Repositories stay separate, and the plan names work in them in prose

spec:decisions.separate-repositoriesDecision 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

specs/decisions/separate-repositories.sdp.md

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

Intent
outcome
Decide whether HQ's concerns share a monorepo or keep separate repositories.
Decision
context
The owner asked whether this should run in a completely blank environment and be configured in some kind of monorepo context, and then answered: this was just being bootstrapped, infra lives happily outside this context, and that is why dependencies cannot be called from here.
decision
There is no monorepo. HQ's plan, Kontrapunkt, infra, SDP, Relay and each project stay in their own repositories. A Spec here names work in another repository in prose, by repository and pull request, and this repository imports and calls nothing from them.
rationale
  • Hard to reverse: it fixes how every session finds its work. Surprising without context: the plan has no code link to what it plans. A real trade-off: no cross-repository checks, against a plan that any blank session can read and that an outside project can copy.
alternatives
  • A monorepo holding HQ and its projects: it would reach across the isolation the owner requires and pull private data next to the plan.
  • Git submodules or vendored copies of the other repositories: they copy state this plan is built not to copy.
consequences
  • A statement about another repository is checked by a session in that repository, not by this corpus's gate.
  • A project that needs a shared capability takes it from a package, as this repository takes SDP.
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.separate-repositories

Arrows: refines (declared).

The diagram as text
  • spec:decisions.separate-repositories: Repositories stay separate, and the plan names work in them in prose · declared Spec
  • spec:hq.headquarters: HQ plans and designs across every project, and starts the engineering work · declared Spec
  • spec:decisions.separate-repositories refines spec:hq.headquarters · declared — settles how HQ's plan touches other repositories
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.separate-repositories
  • E2: decidedBy · declared — sets how HQ reaches work in other repositories
The diagram as text
  • spec:decisions.separate-repositories: Repositories stay separate, and the plan names work in them in prose
  • spec:hq.headquarters: HQ plans and designs across every project, and starts the engineering work
  • spec:decisions.separate-repositories refines spec:hq.headquarters · declared — settles how HQ's plan touches other repositories
  • spec:hq.headquarters decidedBy spec:decisions.separate-repositories · declared — sets how HQ reaches work in other repositories
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 · outgoingHQ plans and designs across every project, and starts the engineering work
spec:hq.headquarters · resolves		declaredsettles how HQ's plan touches other repositoriesNone
decidedBy · incomingHQ plans and designs across every project, and starts the engineering work
spec:hq.headquarters · resolves		declaredsets how HQ reaches work in other repositoriesNone

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.