Spec Studio

HQ plans and designs across every project, and starts the engineering work

spec:hq.headquartersUse Case / Behavior · epicdefined floor ready

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

Packs: none

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

Findings: no errors, no warnings

specs/hq/headquarters.sdp.md

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

HQ is the owner's headquarters for about fifty projects. It works at the altitude of long-term planning, core design and cross-project context, away from the noise of detailed work. When a piece of the plan settles, HQ starts the detailed planning and the execution as sessions in the engineering environment, and reads back what they delivered.

The owner names three aspects and this design adds what connects them. Infra delivers configuration to machines and manages HQ's isolated environment. Delivery planning uses SDP across projects, with projections over them. An assistant capability handles the owner's recurring work outside engineering. Orchestration moves work between harnesses and models, the session handoff carries a settled piece into engineering, and the private context in Kontrapunkt stands behind all of them. Each is a feature that refines this Spec, and spec:hq.model holds their vocabulary. The systems behind them are component designs under specs/architecture/; the Studio's word planned means that no code in this repository realizes them, and several run today in their own repositories.

Intent
actor
The owner, running about fifty projects from one place.
problem
Planning spread across projects and sessions grows into master plans, briefs and status copied everywhere, with little delivered, and a session doing detailed work carries context its task does not need.
outcome
One isolated HQ holds the long-term plan, the core design and the cross-project context, and starts detailed planning and execution in the engineering environment once a piece settles.
value
The owner reads one plan from one graph, and each engineering session starts with only what its work needs.
Behavior
rule.altitude line 32 · specs/hq/headquarters.sdp.md:32
HQ plans and designs at the altitude of the plan and the core design; detailed planning, detailed design and execution happen in sessions HQ starts in the engineering environment.

no example exercises it

rule.settleFirst line 33 · specs/hq/headquarters.sdp.md:33
HQ starts a detailed session only for a piece of the plan that has settled: the decisions it rests on are made and its blocking questions are answered.

no example exercises it

rule.crossProject line 34 · specs/hq/headquarters.sdp.md:34
HQ holds the context that spans projects, and each project's repository holds that project's detail.

no example exercises it

rule.graphIsTruth line 35 · specs/hq/headquarters.sdp.md:35
What comes next, what each entry needs and what waits on the owner are read from this corpus's graph each time, and no status file, brief or plan document copies them.

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.headquarters

Arrows: refines (declared).

The diagram as text
  • spec:hq.headquarters: HQ plans and designs across every project, and starts the engineering work · declared Spec · no satisfying binding
  • spec:architecture.assistant: The assistant · declared Spec · no satisfying binding
  • spec:architecture.cc-agents: cc-agents · declared Spec · no satisfying binding
  • spec:architecture.claude-harness: The Claude harness · declared Spec · no satisfying binding
  • spec:architecture.environments: The engineering environments · declared Spec · no satisfying binding
  • spec:architecture.hq: HQ · declared Spec · no satisfying binding
  • spec:architecture.hq-plan: The HQ plan · declared Spec · no satisfying binding
  • spec:architecture.inbox: The inbox · declared Spec · no satisfying binding
  • spec:architecture.infra: libar-infra · declared Spec · no satisfying binding
  • spec:architecture.kontrapunkt: Kontrapunkt · declared Spec · no satisfying binding
  • spec:architecture.relay: Relay · declared Spec · no satisfying binding
  • spec:architecture.sdp: SDP · declared Spec · no satisfying binding
  • spec:architecture.t3-code: T3 Code · declared Spec · no satisfying binding
  • spec:decisions.hq-starts-engineering: HQ does the core design and starts detailed work in the engineering environment · declared Spec
  • spec:decisions.recovery-closed: The recovery chain stops and this corpus replaces its master plan · declared Spec
  • spec:decisions.separate-repositories: Repositories stay separate, and the plan names work in them in prose · declared Spec
  • spec:hq.assistant: An assistant capability handles the owner's recurring work · declared Spec · no satisfying binding
  • spec:hq.context: HQ's private context stays in one place and stays clean · declared Spec · no satisfying binding
  • spec:hq.delivery-planning: SDP carries delivery planning across projects · declared Spec · no satisfying binding
  • spec:hq.engineering-environment: The engineering environment runs apart from HQ · declared Spec · no satisfying binding
  • spec:hq.environment: HQ runs in an isolated environment that infra manages · declared Spec · no satisfying binding
  • spec:hq.infra: Infra delivers configuration by projection, under HQ's plan · declared Spec · no satisfying binding
  • spec:hq.model: HQ's vocabulary · declared Spec · no satisfying binding
  • spec:hq.orchestration: Orchestration lives in one plugin, apart from infra and HQ · declared Spec · no satisfying binding
  • spec:hq.session-handoff: HQ hands a settled piece to a detailed session · declared Spec · no satisfying binding
  • spec:decisions.client-material-deferred: HQ holds everything until a per-project review screens client material · declared Spec
  • spec:decisions.coordination-native-first: Coordination is built on Claude Code's own messaging, and cc-agents adds only what that lacks · declared Spec
  • spec:decisions.design-locked-by-projection: An approved part of the graph reaches engineering as a read-only projection · declared Spec
  • spec:decisions.isolated-infra-manages-hq: Infra is super isolated and manages the isolated HQ · declared Spec
  • spec:decisions.orchestration-leaves-infra: Generic orchestration moves from infra to cc-agents, and Relay runs jobs until cc-agents earns trust · declared Spec
  • 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:architecture.assistant refines spec:hq.headquarters · declared — one of the systems HQ's design names
  • spec:architecture.cc-agents refines spec:hq.headquarters · declared — one of the systems HQ's design names
  • spec:architecture.claude-harness refines spec:hq.headquarters · declared — one of the systems HQ's design names
  • spec:architecture.environments refines spec:hq.headquarters · declared — one of the systems HQ's design names
  • spec:architecture.hq refines spec:hq.headquarters · declared — one of the systems HQ's design names
  • spec:architecture.hq-plan refines spec:hq.headquarters · declared — one of the systems HQ's design names
  • spec:architecture.inbox refines spec:hq.headquarters · declared — one of the systems HQ's design names
  • spec:architecture.infra refines spec:hq.headquarters · declared — one of the systems HQ's design names
  • spec:architecture.kontrapunkt refines spec:hq.headquarters · declared — one of the systems HQ's design names
  • spec:architecture.relay refines spec:hq.headquarters · declared — one of the systems HQ's design names
  • spec:architecture.sdp refines spec:hq.headquarters · declared — one of the systems HQ's design names
  • spec:architecture.t3-code refines spec:hq.headquarters · declared — one of the systems HQ's design names
  • spec:decisions.client-material-deferred refines spec:hq.context · declared — settles what HQ holds until per-project review
  • spec:decisions.coordination-native-first refines spec:hq.orchestration · declared — settles what coordination is built from once it leaves infra
  • spec:decisions.design-locked-by-projection refines spec:hq.session-handoff · declared — settles how a settled design reaches the engineering repository and stays locked
  • spec:decisions.hq-starts-engineering refines spec:hq.headquarters · declared — settles HQ's altitude and where detailed work happens
  • spec:decisions.isolated-infra-manages-hq refines spec:hq.infra · declared — records how infra and HQ stand towards each other
  • spec:decisions.orchestration-leaves-infra refines spec:hq.orchestration · declared — settles where generic orchestration lives and what runs jobs until then
  • spec:decisions.recovery-closed refines spec:hq.headquarters · declared — settles what of the recovery's master plan HQ's plan keeps
  • spec:decisions.sdp-holds-the-plan refines spec:hq.delivery-planning · declared — settles what carries HQ's plan and where it sits
  • spec:decisions.separate-repositories refines spec:hq.headquarters · declared — settles how HQ's plan touches other repositories
  • spec:hq.assistant refines spec:hq.headquarters · declared — the third aspect the owner names
  • spec:hq.context refines spec:hq.headquarters · declared — names where HQ's context lives and how it stays clean
  • spec:hq.delivery-planning refines spec:hq.headquarters · declared — one of the aspects the owner names
  • spec:hq.engineering-environment refines spec:hq.headquarters · declared — the place HQ's work goes to be executed
  • spec:hq.environment refines spec:hq.headquarters · declared — gives HQ's isolation its home
  • spec:hq.infra refines spec:hq.headquarters · declared — one of the aspects the owner names
  • spec:hq.model refines spec:hq.headquarters · declared — names what the HQ design speaks of
  • spec:hq.orchestration refines spec:hq.headquarters · declared — names how work moves between harnesses, models and machines
  • spec:hq.session-handoff refines spec:hq.headquarters · declared — realizes how HQ starts the work it does not do itself
Mermaid source

Copyable source; the Studio draws static SVG.

Preferred syntax: requirementDiagram. Chosen syntax: flowchart TB because folds require exact labels unavailable in requirement syntax.

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.headquarters
The diagram as text
  • spec:architecture.assistant: The assistant
  • spec:architecture.cc-agents: cc-agents
  • spec:architecture.claude-harness: The Claude harness
  • spec:architecture.environments: The engineering environments
  • spec:architecture.hq: HQ
  • spec:architecture.hq-plan: The HQ plan
  • spec:architecture.inbox: The inbox
  • spec:architecture.infra: libar-infra
  • spec:architecture.kontrapunkt: Kontrapunkt
  • spec:architecture.relay: Relay
  • spec:architecture.sdp: SDP
  • spec:architecture.t3-code: T3 Code
  • spec:decisions.hq-starts-engineering: HQ does the core design and starts detailed work in the engineering environment
  • spec:decisions.recovery-closed: The recovery chain stops and this corpus replaces its master plan
  • 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:decisions.separate-repositories: Repositories stay separate, and the plan names work in them in prose
  • spec:hq.assistant: An assistant capability handles the owner's recurring work
  • spec:hq.context: HQ's private context stays in one place and stays clean
  • spec:hq.delivery-planning: SDP carries delivery planning across projects
  • spec:hq.engineering-environment: The engineering environment runs apart from HQ
  • spec:hq.environment: HQ runs in an isolated environment that infra manages
  • spec:hq.headquarters: HQ plans and designs across every project, and starts the engineering work
  • spec:hq.infra: Infra delivers configuration by projection, under HQ's plan
  • spec:hq.model: HQ's vocabulary
  • spec:hq.orchestration: Orchestration lives in one plugin, apart from infra and HQ
  • spec:hq.session-handoff: HQ hands a settled piece to a detailed session
  • spec:hq.headquarters decidedBy spec:decisions.hq-starts-engineering · declared — sets the altitude HQ works at and where detailed work happens
  • spec:hq.headquarters decidedBy spec:decisions.recovery-closed · declared — sets what of the recovery's master plan this plan keeps
  • spec:hq.headquarters decidedBy spec:decisions.sdp-holds-the-plan · declared — sets where the plan lives and what reads it
  • spec:hq.headquarters decidedBy spec:decisions.separate-repositories · declared — sets how HQ reaches work in other repositories
  • spec:architecture.assistant refines spec:hq.headquarters · declared — one of the systems HQ's design names
  • spec:architecture.cc-agents refines spec:hq.headquarters · declared — one of the systems HQ's design names
  • spec:architecture.claude-harness refines spec:hq.headquarters · declared — one of the systems HQ's design names
  • spec:architecture.environments refines spec:hq.headquarters · declared — one of the systems HQ's design names
  • spec:architecture.hq refines spec:hq.headquarters · declared — one of the systems HQ's design names
  • spec:architecture.hq-plan refines spec:hq.headquarters · declared — one of the systems HQ's design names
  • spec:architecture.inbox refines spec:hq.headquarters · declared — one of the systems HQ's design names
  • spec:architecture.infra refines spec:hq.headquarters · declared — one of the systems HQ's design names
  • spec:architecture.kontrapunkt refines spec:hq.headquarters · declared — one of the systems HQ's design names
  • spec:architecture.relay refines spec:hq.headquarters · declared — one of the systems HQ's design names
  • spec:architecture.sdp refines spec:hq.headquarters · declared — one of the systems HQ's design names
  • spec:architecture.t3-code refines spec:hq.headquarters · declared — one of the systems HQ's design names
  • spec:decisions.hq-starts-engineering refines spec:hq.headquarters · declared — settles HQ's altitude and where detailed work happens
  • spec:decisions.recovery-closed refines spec:hq.headquarters · declared — settles what of the recovery's master plan HQ's plan keeps
  • spec:decisions.separate-repositories refines spec:hq.headquarters · declared — settles how HQ's plan touches other repositories
  • spec:hq.assistant refines spec:hq.headquarters · declared — the third aspect the owner names
  • spec:hq.context refines spec:hq.headquarters · declared — names where HQ's context lives and how it stays clean
  • spec:hq.delivery-planning refines spec:hq.headquarters · declared — one of the aspects the owner names
  • spec:hq.engineering-environment refines spec:hq.headquarters · declared — the place HQ's work goes to be executed
  • spec:hq.environment refines spec:hq.headquarters · declared — gives HQ's isolation its home
  • spec:hq.infra refines spec:hq.headquarters · declared — one of the aspects the owner names
  • spec:hq.model refines spec:hq.headquarters · declared — names what the HQ design speaks of
  • spec:hq.orchestration refines spec:hq.headquarters · declared — names how work moves between harnesses, models and machines
  • spec:hq.session-handoff refines spec:hq.headquarters · declared — realizes how HQ starts the work it does not do itself
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

Relations

Relation and directionOther endClaimReasonExercised keys
decidedBy · outgoingHQ does the core design and starts detailed work in the engineering environment
spec:decisions.hq-starts-engineering · resolves
declaredsets the altitude HQ works at and where detailed work happensNone
decidedBy · outgoingThe recovery chain stops and this corpus replaces its master plan
spec:decisions.recovery-closed · resolves
declaredsets what of the recovery's master plan this plan keepsNone
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
declaredsets where the plan lives and what reads itNone
decidedBy · outgoingRepositories stay separate, and the plan names work in them in prose
spec:decisions.separate-repositories · resolves
declaredsets how HQ reaches work in other repositoriesNone
refines · incomingThe assistant
spec:architecture.assistant · resolves
declaredone of the systems HQ's design namesNone
refines · incomingcc-agents
spec:architecture.cc-agents · resolves
declaredone of the systems HQ's design namesNone
refines · incomingThe Claude harness
spec:architecture.claude-harness · resolves
declaredone of the systems HQ's design namesNone
refines · incomingThe engineering environments
spec:architecture.environments · resolves
declaredone of the systems HQ's design namesNone
refines · incomingHQ
spec:architecture.hq · resolves
declaredone of the systems HQ's design namesNone
refines · incomingThe HQ plan
spec:architecture.hq-plan · resolves
declaredone of the systems HQ's design namesNone
refines · incomingThe inbox
spec:architecture.inbox · resolves
declaredone of the systems HQ's design namesNone
refines · incominglibar-infra
spec:architecture.infra · resolves
declaredone of the systems HQ's design namesNone
refines · incomingKontrapunkt
spec:architecture.kontrapunkt · resolves
declaredone of the systems HQ's design namesNone
refines · incomingRelay
spec:architecture.relay · resolves
declaredone of the systems HQ's design namesNone
refines · incomingSDP
spec:architecture.sdp · resolves
declaredone of the systems HQ's design namesNone
refines · incomingT3 Code
spec:architecture.t3-code · resolves
declaredone of the systems HQ's design namesNone
refines · incomingHQ does the core design and starts detailed work in the engineering environment
spec:decisions.hq-starts-engineering · resolves
declaredsettles HQ's altitude and where detailed work happensNone
refines · incomingThe recovery chain stops and this corpus replaces its master plan
spec:decisions.recovery-closed · resolves
declaredsettles what of the recovery's master plan HQ's plan keepsNone
refines · incomingRepositories stay separate, and the plan names work in them in prose
spec:decisions.separate-repositories · resolves
declaredsettles how HQ's plan touches other repositoriesNone
refines · incomingAn assistant capability handles the owner's recurring work
spec:hq.assistant · resolves
declaredthe third aspect the owner namesNone
refines · incomingHQ's private context stays in one place and stays clean
spec:hq.context · resolves
declarednames where HQ's context lives and how it stays cleanNone
refines · incomingSDP carries delivery planning across projects
spec:hq.delivery-planning · resolves
declaredone of the aspects the owner namesNone
refines · incomingThe engineering environment runs apart from HQ
spec:hq.engineering-environment · resolves
declaredthe place HQ's work goes to be executedNone
refines · incomingHQ runs in an isolated environment that infra manages
spec:hq.environment · resolves
declaredgives HQ's isolation its homeNone
refines · incomingInfra delivers configuration by projection, under HQ's plan
spec:hq.infra · resolves
declaredone of the aspects the owner namesNone
refines · incomingHQ's vocabulary
spec:hq.model · resolves
declarednames what the HQ design speaks ofNone
refines · incomingOrchestration lives in one plugin, apart from infra and HQ
spec:hq.orchestration · resolves
declarednames how work moves between harnesses, models and machinesNone
refines · incomingHQ hands a settled piece to a detailed session
spec:hq.session-handoff · resolves
declaredrealizes how HQ starts the work it does not do itselfNone

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.