Design slice: HQ's roadmap

pack:hq-roadmap

The design as a whole

6 members; 0 example members counted in their parents.
4 relations among members; deepest depth 4; 0 cycles.
2 members held below their stated next rung; 4 waiting only for their author.
12 outside Specs the slice rests on; 0 hold a member; 6 outside Specs rest on it.
0 components touched: 0 through members' code, 0 through what the slice rests on, 0 named by member designs; 0 outside components shown for context.
0 member component designs; 0 realized; 0 of those match.
8 decisions in scope; 8 state below ready.
7 open questions; 3 blocking.

Members read with the ones others rest on first. The columns count the design each member carries beside its rung; they never judge whether it is enough. This page records no review and approves nothing.

How the members rest on each other

Declared relations by depth

Depths are structural, never phases, dates or priority. Dashed relations order nothing. The text keeps every member and original relation.

The diagram as text

spec:hq.session-handoff: HQ hands a settled piece to a detailed session, depth 1, stated defined, floor ready
spec:hq.orchestration: Orchestration lives in one plugin, apart from infra and HQ, depth 1, stated defined, floor ready
spec:hq.infra: Infra delivers configuration by projection, under HQ's plan, depth 2, stated defined, floor ready
spec:hq.context: HQ's private context stays in one place and stays clean, depth 3, stated scoped, floor scoped
spec:hq.delivery-planning: SDP carries delivery planning across projects, depth 2, stated defined, floor ready
spec:hq.assistant: An assistant capability handles the owner's recurring work, depth 4, stated scoped, floor scoped
Outside this scope: spec:decisions.client-material-deferred: HQ holds everything until a per-project review screens client material, stated defined, floor defined
Outside this scope: spec:decisions.coordination-native-first: Coordination is built on Claude Code's own messaging, and cc-agents adds only what that lacks, stated defined, floor ready
Outside this scope: spec:decisions.design-locked-by-projection: An approved part of the graph reaches engineering as a read-only projection, stated defined, floor ready
Outside this scope: spec:decisions.hq-starts-engineering: HQ does the core design and starts detailed work in the engineering environment, stated defined, floor ready
Outside this scope: spec:decisions.isolated-infra-manages-hq: Infra is super isolated and manages the isolated HQ, stated defined, floor ready
Outside this scope: spec:decisions.orchestration-leaves-infra: Generic orchestration moves from infra to cc-agents, and Relay runs jobs until cc-agents earns trust, stated defined, floor ready
Outside this scope: spec:decisions.recovery-closed: The recovery chain stops and this corpus replaces its master plan, stated defined, floor ready
Outside this scope: spec:decisions.sdp-holds-the-plan: HQ's plan for all software delivery is an SDP corpus in a small repository of its own, stated defined, floor ready
Outside this scope: spec:hq.engineering-environment: The engineering environment runs apart from HQ, stated defined, floor ready
Outside this scope: spec:hq.environment: HQ runs in an isolated environment that infra manages, stated defined, floor ready
Outside this scope: spec:hq.headquarters: HQ plans and designs across every project, and starts the engineering work, stated defined, floor ready
Outside this scope: spec:hq.isolation: HQ works apart from detailed work, and infra manages its environment, stated defined, floor ready
spec:hq.assistant dependsOn spec:hq.context · declared — it reads HQ's context and passes what it finds back
spec:hq.context dependsOn spec:hq.infra · declared — per-project settings exist only once infra deploys to projects
spec:hq.delivery-planning dependsOn spec:hq.session-handoff · declared — a project joins the plan through a detailed session started in it
spec:hq.infra dependsOn spec:hq.orchestration · declared — the owner's order takes over Relay and cc-agents before infra, and the inbox leaves infra first
spec:hq.context decidedBy spec:decisions.client-material-deferred · declared — the ruling holds per-project screening until infra deploys to projects
spec:hq.orchestration decidedBy spec:decisions.coordination-native-first · declared — settles what coordination is built from
spec:hq.session-handoff decidedBy spec:decisions.design-locked-by-projection · declared — the ruling makes a read-only projection how an approved design reaches the session
spec:hq.session-handoff decidedBy spec:decisions.hq-starts-engineering · declared — the ruling makes the session the only way detailed work leaves HQ
spec:hq.infra decidedBy spec:decisions.isolated-infra-manages-hq · declared — the ruling sets the two directions between HQ and infra
spec:hq.orchestration decidedBy spec:decisions.orchestration-leaves-infra · declared — the ruling places generic orchestration in Relay's rewrite
spec:hq.infra decidedBy spec:decisions.orchestration-leaves-infra · declared — the ruling takes generic orchestration out of infra
spec:hq.orchestration decidedBy spec:decisions.recovery-closed · declared — items 7 and 8 of the master plan continue here
spec:hq.infra decidedBy spec:decisions.recovery-closed · declared — items 3 and 5 of the master plan continue here
spec:hq.context decidedBy spec:decisions.recovery-closed · declared — item 6 of the master plan continues here
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.session-handoff dependsOn spec:hq.engineering-environment · declared — detailed sessions run there
spec:hq.session-handoff dependsOn spec:hq.environment · declared — the handoff starts from an isolated HQ
spec:hq.session-handoff refines spec:hq.headquarters · declared — realizes how HQ starts the work it does not do itself
spec:hq.orchestration refines spec:hq.headquarters · declared — names how work moves between harnesses, models and machines
spec:hq.infra refines spec:hq.headquarters · declared — one of the aspects 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.assistant refines spec:hq.headquarters · declared — the third aspect the owner names
spec:hq.session-handoff constrainedBy spec:hq.isolation · declared — the requirement makes a session the way detailed work leaves HQ
spec:hq.infra constrainedBy spec:hq.isolation · declared — deployment and access boundaries are designed here

Mermaid source

Copyable source; the Studio draws static SVG. See the full text equivalent for every original relation and folded member.

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

Mermaid source for Declared relations by depth

flowchart TB
  subgraph depth0["Depth 4"]
    n0["An assistant capability handles the owner's recurring work, stated scoped, floor scoped, 0 example members folded in · spec:hq.assistant"]
  end
  subgraph depth1["Depth 3"]
    n1["HQ's private context stays in one place and stays clean, stated scoped, floor scoped, 0 example members folded in · spec:hq.context"]
  end
  subgraph depth2["Depth 2"]
    n2["2 members at depth 2, folded"]
  end
  subgraph depth3["Depth 1"]
    n3["2 members at depth 1, folded"]
  end
  subgraph depth4["Outside this scope"]
    n4["8 outside Specs, decidedBy, folded"]
    n5["2 outside Specs, dependsOn, folded"]
    n6["1 outside Specs, refines, folded"]
    n7["1 outside Specs, constrainedBy, folded"]
  end
  %% folded diagram.pack:hq-roadmap.dependencies.fold.2: spec:hq.infra, spec:hq.delivery-planning
  %% folded diagram.pack:hq-roadmap.dependencies.fold.1: spec:hq.session-handoff, spec:hq.orchestration
  %% folded diagram.pack:hq-roadmap.dependencies.outside.decidedBy: spec:decisions.client-material-deferred, spec:decisions.coordination-native-first, spec:decisions.design-locked-by-projection, spec:decisions.hq-starts-engineering, spec:decisions.isolated-infra-manages-hq, spec:decisions.orchestration-leaves-infra, spec:decisions.recovery-closed, spec:decisions.sdp-holds-the-plan
  %% folded diagram.pack:hq-roadmap.dependencies.outside.dependsOn: spec:hq.engineering-environment, spec:hq.environment
  %% folded diagram.pack:hq-roadmap.dependencies.outside.refines: spec:hq.headquarters
  %% folded diagram.pack:hq-roadmap.dependencies.outside.constrainedBy: spec:hq.isolation
  n3 -->|"constrainedBy · declared — the requirement makes a session the way detailed work leaves HQ"| n7
  %% count: 1; diagram.pack:hq-roadmap.dependencies.fold.1 to diagram.pack:hq-roadmap.dependencies.outside.constrainedBy
  n3 -->|"decidedBy · declared (5 relations)"| n4
  %% count: 5; diagram.pack:hq-roadmap.dependencies.fold.1 to diagram.pack:hq-roadmap.dependencies.outside.decidedBy
  n3 -->|"dependsOn · declared (2 relations)"| n5
  %% count: 2; diagram.pack:hq-roadmap.dependencies.fold.1 to diagram.pack:hq-roadmap.dependencies.outside.dependsOn
  n3 -->|"refines · declared (2 relations)"| n6
  %% count: 2; diagram.pack:hq-roadmap.dependencies.fold.1 to diagram.pack:hq-roadmap.dependencies.outside.refines
  n2 -->|"dependsOn · declared (2 relations)"| n3
  %% count: 2; diagram.pack:hq-roadmap.dependencies.fold.2 to diagram.pack:hq-roadmap.dependencies.fold.1
  n2 -->|"constrainedBy · declared — deployment and access boundaries are designed here"| n7
  %% count: 1; diagram.pack:hq-roadmap.dependencies.fold.2 to diagram.pack:hq-roadmap.dependencies.outside.constrainedBy
  n2 -->|"decidedBy · declared (4 relations)"| n4
  %% count: 4; diagram.pack:hq-roadmap.dependencies.fold.2 to diagram.pack:hq-roadmap.dependencies.outside.decidedBy
  n2 -->|"refines · declared (2 relations) — one of the aspects the owner names"| n6
  %% count: 2; diagram.pack:hq-roadmap.dependencies.fold.2 to diagram.pack:hq-roadmap.dependencies.outside.refines
  n0 -->|"refines · declared — the third aspect the owner names"| n6
  %% count: 1; spec:hq.assistant to diagram.pack:hq-roadmap.dependencies.outside.refines
  n0 -->|"dependsOn · declared — it reads HQ's context and passes what it finds back"| n1
  %% count: 1; spec:hq.assistant to spec:hq.context
  n1 -->|"dependsOn · declared — per-project settings exist only once infra deploys to projects"| n2
  %% count: 1; spec:hq.context to diagram.pack:hq-roadmap.dependencies.fold.2
  n1 -->|"decidedBy · declared (2 relations)"| n4
  %% count: 2; spec:hq.context to diagram.pack:hq-roadmap.dependencies.outside.decidedBy
  n1 -->|"refines · declared — names where HQ's context lives and how it stays clean"| n6
  %% count: 1; spec:hq.context to diagram.pack:hq-roadmap.dependencies.outside.refines

What each member needs next

Member	Depth	Rung	Next rung	Design carried	Code
HQ hands a settled piece to a detailed session `spec:hq.session-handoff` workflow	1	defined floor ready	next ready: nothing blocks	9 rules, 9 keyed0 entries0 declarations1 questions2 decisions0 of 0 verifying examples bound	0 implementing0 referencing
Orchestration lives in one plugin, apart from infra and HQ `spec:hq.orchestration` behavior	1	defined floor ready	next ready: nothing blocks	12 rules, 12 keyed0 entries0 declarations0 questions3 decisions0 of 0 verifying examples bound	0 implementing0 referencing
Infra delivers configuration by projection, under HQ's plan `spec:hq.infra` behavior	2	defined floor ready	next ready: nothing blocks	7 rules, 7 keyed0 entries0 declarations2 questions3 decisions0 of 0 verifying examples bound	0 implementing0 referencing
SDP carries delivery planning across projects `spec:hq.delivery-planning` behavior	2	defined floor ready	next ready: nothing blocks	4 rules, 4 keyed0 entries0 declarations0 questions1 decisions0 of 0 verifying examples bound	0 implementing0 referencing
HQ's private context stays in one place and stays clean `spec:hq.context` behavior	3	scoped floor scoped	next defined: `no-blocking-open-questions` · Spec has no blocking open question in intent.openQuestions.	6 rules, 6 keyed0 entries0 declarations1 questions, 1 blocking2 decisions0 of 0 verifying examples bound	0 implementing0 referencing
An assistant capability handles the owner's recurring work `spec:hq.assistant` behavior	4	scoped floor scoped	next defined: `no-blocking-open-questions` · Spec has no blocking open question in intent.openQuestions.	4 rules, 4 keyed0 entries0 declarations3 questions, 2 blocking0 decisions0 of 0 verifying examples bound	0 implementing0 referencing

The architecture it touches

No component is touched and no member designs a component. 12 Specs the slice rests on have no implementation binding.

Components the slice touches

None.

Member component designs

None.

Outside the slice, shown for context and not counted as touched

None.

Units bound to a member and to no component

None.

Decisions in scope

Decision	Rung	In the slice	Shapes	Questions
HQ holds everything until a per-project review screens client material `spec:decisions.client-material-deferred`	defined floor defined	outside	HQ's private context stays in one place and stays clean	0 open, 0 blocking
Coordination is built on Claude Code's own messaging, and cc-agents adds only what that lacks `spec:decisions.coordination-native-first`	defined floor ready	outside	Orchestration lives in one plugin, apart from infra and HQ	0 open, 0 blocking
An approved part of the graph reaches engineering as a read-only projection `spec:decisions.design-locked-by-projection`	defined floor ready	outside	HQ hands a settled piece to a detailed session	0 open, 0 blocking
HQ does the core design and starts detailed work in the engineering environment `spec:decisions.hq-starts-engineering`	defined floor ready	outside	HQ hands a settled piece to a detailed session	0 open, 0 blocking
Infra is super isolated and manages the isolated HQ `spec:decisions.isolated-infra-manages-hq`	defined floor ready	outside	Infra delivers configuration by projection, under HQ's plan	0 open, 0 blocking
Generic orchestration moves from infra to cc-agents, and Relay runs jobs until cc-agents earns trust `spec:decisions.orchestration-leaves-infra`	defined floor ready	outside	Orchestration lives in one plugin, apart from infra and HQ, Infra delivers configuration by projection, under HQ's plan	0 open, 0 blocking
The recovery chain stops and this corpus replaces its master plan `spec:decisions.recovery-closed`	defined floor ready	outside	Orchestration lives in one plugin, apart from infra and HQ, Infra delivers configuration by projection, under HQ's plan, HQ's private context stays in one place and stays clean	0 open, 0 blocking
HQ's plan for all software delivery is an SDP corpus in a small repository of its own `spec:decisions.sdp-holds-the-plan`	defined floor ready	outside	SDP carries delivery planning across projects	0 open, 0 blocking

Open questions in scope

blocking · question.agentPlacement · spec:hq.assistant · Where does the assistant run, given that it needs HQ's context and faces outward?Decider: delegatedTrigger: the assistant is taken upHolds: An assistant capability handles the owner's recurring work
blocking · question.sendsAlone · spec:hq.assistant · What may the assistant send without the owner reading it first?Decider: ownerTrigger: the assistant is taken upHolds: An assistant capability handles the owner's recurring work
blocking · question.clientMaterial · spec:hq.context · How is client material handled, project by project: what is screened, and where?Decider: ownerTrigger: infra deploys per-project settingsHolds: HQ's private context stays in one place and stays clean
non-blocking · question.runtime · spec:hq.assistant · Which runtime carries the assistant?Decider: delegatedProvisional: Something like Hermes Agent, the kind the owner named.
non-blocking · question.rollbackPoint · spec:hq.infra · Where did infra's orchestration trouble start, at the takeover of PR #13 where Kimi K3.1 replaced Opus 5.5 or earlier, and which earlier delivery does infra's tooling roll back to?Decider: owner
non-blocking · question.takeover · spec:hq.infra · Is HQ ready to take over infra, and what must hold first?Decider: owner
non-blocking · question.sessionModels · spec:hq.session-handoff · Which harness and models does a detailed session run on?Decider: delegatedProvisional: The session's lead chooses per task, under the orchestration aspect's rules.

Where the slice meets the rest

Rests on (12)

Spec	Rung	Implementation binding	Joined members	Holds
HQ holds everything until a per-project review screens client material `spec:decisions.client-material-deferred`	defined floor defined	none	decidedBy: HQ's private context stays in one place and stays clean	none
Coordination is built on Claude Code's own messaging, and cc-agents adds only what that lacks `spec:decisions.coordination-native-first`	defined floor ready	none	decidedBy: Orchestration lives in one plugin, apart from infra and HQ	none
An approved part of the graph reaches engineering as a read-only projection `spec:decisions.design-locked-by-projection`	defined floor ready	none	decidedBy: HQ hands a settled piece to a detailed session	none
HQ does the core design and starts detailed work in the engineering environment `spec:decisions.hq-starts-engineering`	defined floor ready	none	decidedBy: HQ hands a settled piece to a detailed session	none
Infra is super isolated and manages the isolated HQ `spec:decisions.isolated-infra-manages-hq`	defined floor ready	none	decidedBy: Infra delivers configuration by projection, under HQ's plan	none
Generic orchestration moves from infra to cc-agents, and Relay runs jobs until cc-agents earns trust `spec:decisions.orchestration-leaves-infra`	defined floor ready	none	decidedBy: Orchestration lives in one plugin, apart from infra and HQ, Infra delivers configuration by projection, under HQ's plan	none
The recovery chain stops and this corpus replaces its master plan `spec:decisions.recovery-closed`	defined floor ready	none	decidedBy: Orchestration lives in one plugin, apart from infra and HQ, Infra delivers configuration by projection, under HQ's plan, HQ's private context stays in one place and stays clean	none
HQ's plan for all software delivery is an SDP corpus in a small repository of its own `spec:decisions.sdp-holds-the-plan`	defined floor ready	none	decidedBy: SDP carries delivery planning across projects	none
The engineering environment runs apart from HQ `spec:hq.engineering-environment`	defined floor ready	none	dependsOn: HQ hands a settled piece to a detailed session	none
HQ runs in an isolated environment that infra manages `spec:hq.environment`	defined floor ready	none	dependsOn: HQ hands a settled piece to a detailed session	none
HQ plans and designs across every project, and starts the engineering work `spec:hq.headquarters`	defined floor ready	none	refines: HQ hands a settled piece to a detailed session, Orchestration lives in one plugin, apart from infra and HQ, Infra delivers configuration by projection, under HQ's plan, HQ's private context stays in one place and stays clean, SDP carries delivery planning across projects, An assistant capability handles the owner's recurring work	none
HQ works apart from detailed work, and infra manages its environment `spec:hq.isolation`	defined floor ready	none	constrainedBy: HQ hands a settled piece to a detailed session, Infra delivers configuration by projection, under HQ's plan	none

Rested on by (6)

Spec	Rung	Implementation binding	Joined members	Holds
HQ holds everything until a per-project review screens client material `spec:decisions.client-material-deferred`	defined floor defined	none	refines: HQ's private context stays in one place and stays clean	none
Coordination is built on Claude Code's own messaging, and cc-agents adds only what that lacks `spec:decisions.coordination-native-first`	defined floor ready	none	refines: Orchestration lives in one plugin, apart from infra and HQ	none
An approved part of the graph reaches engineering as a read-only projection `spec:decisions.design-locked-by-projection`	defined floor ready	none	refines: HQ hands a settled piece to a detailed session	none
Infra is super isolated and manages the isolated HQ `spec:decisions.isolated-infra-manages-hq`	defined floor ready	none	refines: Infra delivers configuration by projection, under HQ's plan	none
Generic orchestration moves from infra to cc-agents, and Relay runs jobs until cc-agents earns trust `spec:decisions.orchestration-leaves-infra`	defined floor ready	none	refines: Orchestration lives in one plugin, apart from infra and HQ	none
HQ's plan for all software delivery is an SDP corpus in a small repository of its own `spec:decisions.sdp-holds-the-plan`	defined floor ready	none	refines: SDP carries delivery planning across projects	none

Verified by (0)

None.

Superseded by (0)

None.

Composing (0)

Composing needs the script.