Spec Studio

Capabilities

Epics and their declared refinement, from the capability map.

Each rollup counts distinct descendants of that epic. Scopes may overlap; epic rows are not added together.

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

Epic's own evidence

HQ plans and designs across every project, and starts the engineering work · spec:hq.headquarters · behavior · epic · stated defined · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questions

Distinct descendants, excluding this epic: 30 Specs · No examples · 9 decisions.

Stated rungs
idea 0 · scoped 14 · defined 16 · ready 0
Floors reached
none 0 · idea 0 · scoped 2 · defined 1 · ready 27
Kinds
behavior 19 · workflow 1 · example 0 · rule 0 · constraint 0 · model 1 · decision 9 · contract 0
Altitudes
epic 0 · feature 30 · story 0
Binding evidence
No Specs with implementation binding present · No Specs with verifier binding present
Questions
7 open questions · 3 blocking questions

Show these Specs

Refinement · parent to child reading order

Arrows: refines (declared). Later visits repeat a Spec and link to its first occurrence.

Scroll horizontally to read the whole drawing.

Refinement · parent to child reading orderRootsdiagram.spec:hq.headquarters.capability.branch.spec%3Ahq.headquartersHQ plans and designs acrossevery project, and startsthe engineering workspec:hq.headquartersepicDepth 1 · Children ofspec:hq.headquartersdiagram.spec:hq.headquarters.capability.branch.spec%3Aarchitecture.assistantThe assistant…architecture.assistantfeaturediagram.spec:hq.headquarters.capability.branch.spec%3Aarchitecture.cc-agentscc-agents…architecture.cc-agentsfeaturediagram.spec:hq.headquarters.capability.branch.spec%3Aarchitecture.claude-harnessThe Claude harness…architecture.claude-harnessfeaturediagram.spec:hq.headquarters.capability.branch.spec%3Aarchitecture.environmentsThe engineering environments…architecture.environmentsfeaturediagram.spec:hq.headquarters.capability.branch.spec%3Aarchitecture.hqHQ…architecture.hqfeaturediagram.spec:hq.headquarters.capability.branch.spec%3Aarchitecture.hq-planThe HQ plan…architecture.hq-planfeaturediagram.spec:hq.headquarters.capability.branch.spec%3Aarchitecture.inboxThe inbox…architecture.inboxfeaturediagram.spec:hq.headquarters.capability.branch.spec%3Aarchitecture.infralibar-infra…architecture.infrafeaturediagram.spec:hq.headquarters.capability.branch.spec%3Aarchitecture.kontrapunktKontrapunkt…architecture.kontrapunktfeaturediagram.spec:hq.headquarters.capability.branch.spec%3Aarchitecture.relayRelay…architecture.relayfeaturediagram.spec:hq.headquarters.capability.branch.spec%3Aarchitecture.sdpSDP…architecture.sdpfeaturediagram.spec:hq.headquarters.capability.branch.spec%3Aarchitecture.t3-codeT3 Code…architecture.t3-codefeaturediagram.spec:hq.headquarters.capability.branch.spec%3Adecisions.hq-starts-engineeringHQ does the core design andstarts detailed work in theengineering environment…decisions.hq-starts-engineeringfeaturediagram.spec:hq.headquarters.capability.branch.spec%3Adecisions.recovery-closedThe recovery chain stopsand this corpus replacesits master plan…decisions.recovery-closedfeaturediagram.spec:hq.headquarters.capability.branch.spec%3Adecisions.separate-repositoriesRepositories stay separate,and the plan names work inthem in prose…decisions.separate-repositoriesfeaturediagram.spec:hq.headquarters.capability.branch.spec%3Ahq.assistantAn assistant capabilityhandles the owner'srecurring work…hq.assistantfeaturediagram.spec:hq.headquarters.capability.branch.spec%3Ahq.headquarters.foldedFolded branchbranch of spec:hq.headquarters14 unique Specs
The diagram as text

31 unique Specs; 18 rendered boxes.

  • spec:hq.headquarters: HQ plans and designs across every project, and starts the engineering work · epic
  • spec:architecture.assistant: The assistant · feature
  • spec:architecture.cc-agents: cc-agents · feature
  • spec:architecture.claude-harness: The Claude harness · feature
  • spec:architecture.environments: The engineering environments · feature
  • spec:architecture.hq: HQ · feature
  • spec:architecture.hq-plan: The HQ plan · feature
  • spec:architecture.inbox: The inbox · feature
  • spec:architecture.infra: libar-infra · feature
  • spec:architecture.kontrapunkt: Kontrapunkt · feature
  • spec:architecture.relay: Relay · feature
  • spec:architecture.sdp: SDP · feature
  • spec:architecture.t3-code: T3 Code · feature
  • spec:decisions.hq-starts-engineering: HQ does the core design and starts detailed work in the engineering environment · feature
  • spec:decisions.recovery-closed: The recovery chain stops and this corpus replaces its master plan · feature
  • spec:decisions.separate-repositories: Repositories stay separate, and the plan names work in them in prose · feature
  • spec:hq.assistant: An assistant capability handles the owner's recurring work · feature
  • spec:hq.context: HQ's private context stays in one place and stays clean · feature
  • spec:decisions.client-material-deferred: HQ holds everything until a per-project review screens client material · feature
  • spec:hq.delivery-planning: SDP carries delivery planning across projects · feature
  • spec:decisions.sdp-holds-the-plan: HQ's plan for all software delivery is an SDP corpus in a small repository of its own · feature
  • spec:hq.engineering-environment: The engineering environment runs apart from HQ · feature
  • spec:hq.environment: HQ runs in an isolated environment that infra manages · feature
  • spec:hq.infra: Infra delivers configuration by projection, under HQ's plan · feature
  • spec:decisions.isolated-infra-manages-hq: Infra is super isolated and manages the isolated HQ · feature
  • spec:hq.model: HQ's vocabulary · feature
  • spec:hq.orchestration: Orchestration lives in one plugin, apart from infra and HQ · feature
  • spec:decisions.coordination-native-first: Coordination is built on Claude Code's own messaging, and cc-agents adds only what that lacks · feature
  • spec:decisions.orchestration-leaves-infra: Generic orchestration moves from infra to cc-agents, and Relay runs jobs until cc-agents earns trust · feature
  • spec:hq.session-handoff: HQ hands a settled piece to a detailed session · feature
  • spec:decisions.design-locked-by-projection: An approved part of the graph reaches engineering as a read-only projection · feature
  • 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: mindmap. Chosen syntax: flowchart BT because the drawing has a fold.

Complete refinement text
  1. Root

    HQ plans and designs across every project, and starts the engineering work · spec:hq.headquarters · behavior · epic · stated defined · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questions
  2. Parent: spec:hq.headquarters

    The assistant · spec:architecture.assistant · behavior · feature · stated scoped · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questions
  3. Parent: spec:hq.headquarters

    cc-agents · spec:architecture.cc-agents · behavior · feature · stated scoped · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questions
  4. Parent: spec:hq.headquarters

    The Claude harness · spec:architecture.claude-harness · behavior · feature · stated scoped · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questions
  5. Parent: spec:hq.headquarters

    The engineering environments · spec:architecture.environments · behavior · feature · stated scoped · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questions
  6. Parent: spec:hq.headquarters

    HQ · spec:architecture.hq · behavior · feature · stated scoped · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questions
  7. Parent: spec:hq.headquarters

    The HQ plan · spec:architecture.hq-plan · behavior · feature · stated scoped · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questions
  8. Parent: spec:hq.headquarters

    The inbox · spec:architecture.inbox · behavior · feature · stated scoped · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questions
  9. Parent: spec:hq.headquarters

    libar-infra · spec:architecture.infra · behavior · feature · stated scoped · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questions
  10. Parent: spec:hq.headquarters

    Kontrapunkt · spec:architecture.kontrapunkt · behavior · feature · stated scoped · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questions
  11. Parent: spec:hq.headquarters

    Relay · spec:architecture.relay · behavior · feature · stated scoped · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questions
  12. Parent: spec:hq.headquarters

    SDP · spec:architecture.sdp · behavior · feature · stated scoped · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questions
  13. Parent: spec:hq.headquarters

    T3 Code · spec:architecture.t3-code · behavior · feature · stated scoped · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questions
  14. Parent: spec:hq.headquarters

    Decision · HQ does the core design and starts detailed work in the engineering environmentHQ does the core design and starts detailed work in the engineering environment · spec:decisions.hq-starts-engineering · decision · feature · stated defined · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questions
  15. Parent: spec:hq.headquarters

    Decision · The recovery chain stops and this corpus replaces its master planThe recovery chain stops and this corpus replaces its master plan · spec:decisions.recovery-closed · decision · feature · stated defined · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questions
  16. Parent: spec:hq.headquarters

    Decision · Repositories stay separate, and the plan names work in them in proseRepositories stay separate, and the plan names work in them in prose · spec:decisions.separate-repositories · decision · feature · stated defined · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questions
  17. Parent: spec:hq.headquarters

    An assistant capability handles the owner's recurring work · spec:hq.assistant · behavior · feature · stated scoped · floor scoped · implementation binding none · verifier binding none · 3 open questions · 2 blocking questions
    • non-blocking: Which runtime carries the assistant?
    • blocking: Where does the assistant run, given that it needs HQ's context and faces outward?
    • blocking: What may the assistant send without the owner reading it first?
  18. Parent: spec:hq.headquarters

    HQ's private context stays in one place and stays clean · spec:hq.context · behavior · feature · stated scoped · floor scoped · implementation binding none · verifier binding none · 1 open question · 1 blocking question
    • blocking: How is client material handled, project by project: what is screened, and where?
  19. Parent: spec:hq.context

    Decision · HQ holds everything until a per-project review screens client materialHQ holds everything until a per-project review screens client material · spec:decisions.client-material-deferred · decision · feature · stated defined · floor defined · implementation binding none · verifier binding none · No open questions · No blocking questions
  20. Parent: spec:hq.headquarters

    SDP carries delivery planning across projects · spec:hq.delivery-planning · behavior · feature · stated defined · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questions
  21. Parent: spec:hq.delivery-planning

    Decision · HQ's plan for all software delivery is an SDP corpus in a small repository of its ownHQ's plan for all software delivery is an SDP corpus in a small repository of its own · spec:decisions.sdp-holds-the-plan · decision · feature · stated defined · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questions
  22. Parent: spec:hq.headquarters

    The engineering environment runs apart from HQ · spec:hq.engineering-environment · behavior · feature · stated defined · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questions
  23. Parent: spec:hq.headquarters

    HQ runs in an isolated environment that infra manages · spec:hq.environment · behavior · feature · stated defined · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questions
  24. Parent: spec:hq.headquarters

    Infra delivers configuration by projection, under HQ's plan · spec:hq.infra · behavior · feature · stated defined · floor ready · implementation binding none · verifier binding none · 2 open questions · No blocking questions
    • non-blocking: 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?
    • non-blocking: Is HQ ready to take over infra, and what must hold first?
  25. Parent: spec:hq.infra

    Decision · Infra is super isolated and manages the isolated HQInfra is super isolated and manages the isolated HQ · spec:decisions.isolated-infra-manages-hq · decision · feature · stated defined · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questions
  26. Parent: spec:hq.headquarters

    HQ's vocabulary · spec:hq.model · model · feature · stated defined · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questions
  27. Parent: spec:hq.headquarters

    Orchestration lives in one plugin, apart from infra and HQ · spec:hq.orchestration · behavior · feature · stated defined · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questions
  28. Parent: spec:hq.orchestration

    Decision · Coordination is built on Claude Code's own messaging, and cc-agents adds only what that lacksCoordination is built on Claude Code's own messaging, and cc-agents adds only what that lacks · spec:decisions.coordination-native-first · decision · feature · stated defined · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questions
  29. Parent: spec:hq.orchestration

    Decision · Generic orchestration moves from infra to cc-agents, and Relay runs jobs until cc-agents earns trustGeneric orchestration moves from infra to cc-agents, and Relay runs jobs until cc-agents earns trust · spec:decisions.orchestration-leaves-infra · decision · feature · stated defined · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questions
  30. Parent: spec:hq.headquarters

    HQ hands a settled piece to a detailed session · spec:hq.session-handoff · workflow · feature · stated defined · floor ready · implementation binding none · verifier binding none · 1 open question · No blocking questions
    • non-blocking: Which harness and models does a detailed session run on?
  31. Parent: spec:hq.session-handoff

    Decision · An approved part of the graph reaches engineering as a read-only projectionAn approved part of the graph reaches engineering as a read-only projection · spec:decisions.design-locked-by-projection · decision · feature · stated defined · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questions

No epic reaches these Specs

Show these Specs

Refinement · parent to child reading order

Arrows: refines (declared). Later visits repeat a Spec and link to its first occurrence.

The diagram as text

1 unique Specs; 1 rendered boxes.

  • spec:hq.isolation: HQ works apart from detailed work, and infra manages its environment · feature
  • Unreached ids: spec:hq.isolation
Mermaid source

Copyable source; the Studio draws static SVG.

Preferred syntax: mindmap. Chosen syntax: flowchart BT because the drawing has an unreached band.

Complete refinement text
  1. Root

    HQ works apart from detailed work, and infra manages its environment · spec:hq.isolation · constraint · feature · stated defined · floor ready · implementation binding none · verifier binding none · No open questions · No blocking questions
Composing (0)

Composing needs the script.