Spec Studio

Generic orchestration moves from infra to cc-agents, and Relay runs jobs until cc-agents earns trust

spec:decisions.orchestration-leaves-infraDecision 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/orchestration-leaves-infra.sdp.md

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

Intent
outcome
Decide where the inbox, the chain and other generic orchestration live, and what runs harness jobs meanwhile.
Decision
context
The inbox coordination lives in infra because the attempt at bootstrapping HQ needed it there. The owner ruled that all generic orchestration moves to the Relay plugin, and on 30 October named the destination: the rewrite of Relay, cc-agents, built to the official Claude Code mods extension standard and almost done. Relay already carries mission-critical multi-day work.
decision
The inbox, the chain and similar generic orchestration move from infra to cc-agents. Until cc-agents' job runner earns trust it stays off on every machine and Relay runs the harness jobs, while its coordination can already be on. Infra deploys the result to projects as an extension.
rationale
  • Hard to reverse: every project's sessions will coordinate through it. Surprising without context: the machinery that moves work sits in neither HQ nor infra. A real trade-off: a plugin that must work across harnesses, against one repository's concerns leaking into all fifty projects.
alternatives
  • Keep orchestration in infra: infra would stay the dependency of all coordination, and it is the repository that has to be most isolated.
  • Put orchestration in HQ: HQ would become a runtime, and it would lose the quiet the isolation exists for.
  • Switch to cc-agents now: its earlier cut has not earned trust, and the fleet's work depends on what runs jobs today.
consequences
  • The owner's recorded order takes over Relay and cc-agents before infra, so the roadmap puts orchestration ahead of infra's takeover.
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.orchestration-leaves-infra

Arrows: refines (declared).

The diagram as text
  • 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:hq.orchestration: Orchestration lives in one plugin, apart from infra and HQ · declared Spec
  • spec:decisions.orchestration-leaves-infra refines spec:hq.orchestration · declared — settles where generic orchestration lives and what runs jobs until then
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.orchestration-leaves-infra
  • E3: decidedBy · declared — the ruling places generic orchestration in Relay's rewrite
The diagram as text
  • spec:decisions.orchestration-leaves-infra: Generic orchestration moves from infra to cc-agents, and Relay runs jobs until cc-agents earns trust
  • spec:hq.infra: Infra delivers configuration by projection, under HQ's plan
  • spec:hq.orchestration: Orchestration lives in one plugin, apart from infra and HQ
  • spec:decisions.orchestration-leaves-infra refines spec:hq.orchestration · declared — settles where generic orchestration lives and what runs jobs until then
  • spec:hq.infra decidedBy spec:decisions.orchestration-leaves-infra · declared — the ruling takes generic orchestration out of infra
  • spec:hq.orchestration decidedBy spec:decisions.orchestration-leaves-infra · declared — the ruling places generic orchestration in Relay's rewrite
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

Distance 5

Distance 6

Distance 7

Distance 8

Relations

Relation and directionOther endClaimReasonExercised keys
refines · outgoingOrchestration lives in one plugin, apart from infra and HQ
spec:hq.orchestration · resolves		declaredsettles where generic orchestration lives and what runs jobs until thenNone
decidedBy · incomingInfra delivers configuration by projection, under HQ's plan
spec:hq.infra · resolves		declaredthe ruling takes generic orchestration out of infraNone
decidedBy · incomingOrchestration lives in one plugin, apart from infra and HQ
spec:hq.orchestration · resolves		declaredthe ruling places generic orchestration in Relay's rewriteNone

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.