Spec Studio

Architecture

Components, their members and uses, and planned component designs.

0 components realized and 3 planned. They state 1 context and no layers. 0 uses edges between components. 0 designs differ from their components.

Components by context and layer

Arrows: plans to use (declared). Dashed arrows: plans to use (declared).

The diagram as text
  • component:orchestration.cc-agents: component:orchestration.cc-agents, planned
  • component:orchestration.inbox: component:orchestration.inbox, planned
  • component:orchestration.relay: component:orchestration.relay, planned
  • component:orchestration.cc-agents plans to use component:orchestration.inbox · declared
Mermaid source

Copyable source; the Studio draws static SVG.

Preferred syntax: block; flowchart fallback because block cannot carry edge claims and counts.

Component uses

Rows use columns. · means no anchored use recorded; a component's own cell is empty.

Which components use which
Using / used

Designed, not built

DesignComponentContextLayerRolePlans to useAnchor exists without satisfying
spec:architecture.cc-agentscomponent:orchestration.cc-agentsorchestrationnot statednot statedcomponent:engineering.claude-harness, component:orchestration.inboxno
spec:architecture.inboxcomponent:orchestration.inboxorchestrationnot statednot statedcomponent:engineering.claude-harnessno
spec:architecture.relaycomponent:orchestration.relayorchestrationnot statednot statedcomponent:engineering.claude-harnessno

Significant units

Recorded bindings state no review approval or execution verdict.

None.

No component

Role not stated
Composing (0)

Composing needs the script.