Design slice: Coordination roadmap

pack:cc-agents-coordination

The design as a whole

5 members; 0 example members counted in their parents.
4 relations among members; deepest depth 4; 0 cycles.
0 members held below their stated next rung; 5 waiting only for their author.
2 outside Specs the slice rests on; 0 hold a member; 1 outside Spec rests 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.
1 decision in scope; 1 states below ready.
5 open questions; 0 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:cc-agents.coordination.session-scanning: A scan reads a project's sessions and traces each direction to its outcome, depth 1, stated defined, floor ready
spec:cc-agents.coordination.adoption: Coordination switches on alone, and a project takes it up with one setting and its own boundaries, depth 1, stated defined, floor ready
spec:cc-agents.coordination.record: Messages between sessions this session saw are kept whole, with what is known of who sent them and what came of them, depth 2, stated defined, floor ready
spec:cc-agents.coordination.chain: A lead states its parent once, and the chain is read from what leads stated, depth 3, stated defined, floor ready
spec:cc-agents.coordination.view: The person sees the chain and the traffic without asking a model, depth 4, stated defined, floor ready
Outside this scope: spec:cc-agents.coordination: Sessions that must message each other leave a record and a place in a chain, stated defined, floor ready
Outside this scope: spec:cc-agents.coordination.boundary-only: A second session exists only across a boundary one session cannot cross, stated defined, floor ready
spec:cc-agents.coordination.chain dependsOn spec:cc-agents.coordination.record · declared — a join is a chain entry in the record, and the tree is read from entries
spec:cc-agents.coordination.record dependsOn spec:cc-agents.coordination.adoption · declared — the record is written only with coordination on, and it stores the inbound setting that part reads
spec:cc-agents.coordination.view dependsOn spec:cc-agents.coordination.chain · declared — the view draws the chain
spec:cc-agents.coordination.view dependsOn spec:cc-agents.coordination.record · declared — the view reads entries to say what was heard and when
spec:cc-agents.coordination.session-scanning refines spec:cc-agents.coordination · declared — reads what sessions leave behind, so that work is not lost between them
spec:cc-agents.coordination.adoption refines spec:cc-agents.coordination · declared — how coordination is switched on alone and taken up by a project
spec:cc-agents.coordination.record refines spec:cc-agents.coordination · declared — the first thing the plugin adds to the host's messaging
spec:cc-agents.coordination.chain refines spec:cc-agents.coordination · declared — the second thing the plugin adds to the host's messaging
spec:cc-agents.coordination.view refines spec:cc-agents.coordination · declared — what the person sees of coordination
spec:cc-agents.coordination.chain decidedBy spec:cc-agents.coordination.boundary-only · declared — fixes the roles to top and lead and the agents out of the chain

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["The person sees the chain and the traffic without asking a model, stated defined, floor ready, 0 example members folded in · spec:cc-agents.coordination.view"]
  end
  subgraph depth1["Depth 3"]
    n1["A lead states its parent once, and the chain is read from what leads stated, stated defined, floor ready, 0 example members folded in · spec:cc-agents.coordination.chain"]
  end
  subgraph depth2["Depth 2"]
    n2["Messages between sessions this session saw are kept whole, with what is known of who sent them and what came of them, stated defined, floor ready, 0 example members folded in · spec:cc-agents.coordination.record"]
  end
  subgraph depth3["Depth 1"]
    n3["A scan reads a project's sessions and traces each direction to its outcome, stated defined, floor ready, 0 example members folded in · spec:cc-agents.coordination.session-scanning"]
    n4["Coordination switches on alone, and a project takes it up with one setting and its own boundaries, stated defined, floor ready, 0 example members folded in · spec:cc-agents.coordination.adoption"]
  end
  subgraph depth4["Outside this scope"]
    n5["1 outside Specs, refines, folded"]
    n6["1 outside Specs, decidedBy, folded"]
  end
  %% folded diagram.pack:cc-agents-coordination.dependencies.outside.refines: spec:cc-agents.coordination
  %% folded diagram.pack:cc-agents-coordination.dependencies.outside.decidedBy: spec:cc-agents.coordination.boundary-only
  n4 -->|"refines · declared — how coordination is switched on alone and taken up by a project"| n5
  %% count: 1; spec:cc-agents.coordination.adoption to diagram.pack:cc-agents-coordination.dependencies.outside.refines
  n1 -->|"decidedBy · declared — fixes the roles to top and lead and the agents out of the chain"| n6
  %% count: 1; spec:cc-agents.coordination.chain to diagram.pack:cc-agents-coordination.dependencies.outside.decidedBy
  n1 -->|"refines · declared — the second thing the plugin adds to the host's messaging"| n5
  %% count: 1; spec:cc-agents.coordination.chain to diagram.pack:cc-agents-coordination.dependencies.outside.refines
  n1 -->|"dependsOn · declared — a join is a chain entry in the record, and the tree is read from entries"| n2
  %% count: 1; spec:cc-agents.coordination.chain to spec:cc-agents.coordination.record
  n2 -->|"refines · declared — the first thing the plugin adds to the host's messaging"| n5
  %% count: 1; spec:cc-agents.coordination.record to diagram.pack:cc-agents-coordination.dependencies.outside.refines
  n2 -->|"dependsOn · declared — the record is written only with coordination on, and it stores the inbound setting that part reads"| n4
  %% count: 1; spec:cc-agents.coordination.record to spec:cc-agents.coordination.adoption
  n3 -->|"refines · declared — reads what sessions leave behind, so that work is not lost between them"| n5
  %% count: 1; spec:cc-agents.coordination.session-scanning to diagram.pack:cc-agents-coordination.dependencies.outside.refines
  n0 -->|"refines · declared — what the person sees of coordination"| n5
  %% count: 1; spec:cc-agents.coordination.view to diagram.pack:cc-agents-coordination.dependencies.outside.refines
  n0 -->|"dependsOn · declared — the view draws the chain"| n1
  %% count: 1; spec:cc-agents.coordination.view to spec:cc-agents.coordination.chain
  n0 -->|"dependsOn · declared — the view reads entries to say what was heard and when"| n2
  %% count: 1; spec:cc-agents.coordination.view to spec:cc-agents.coordination.record

What each member needs next

Member	Depth	Rung	Next rung	Design carried	Code
A scan reads a project's sessions and traces each direction to its outcome `spec:cc-agents.coordination.session-scanning` behavior	1	defined floor ready	next ready: nothing blocks	7 rules, 7 keyed0 entries0 declarations1 questions0 decisions0 of 0 verifying examples bound	0 implementing0 referencing
Coordination switches on alone, and a project takes it up with one setting and its own boundaries `spec:cc-agents.coordination.adoption` behavior	1	defined floor ready	next ready: nothing blocks	9 rules, 9 keyed4 entries3 declarations0 questions0 decisions0 of 0 verifying examples bound	0 implementing0 referencing
Messages between sessions this session saw are kept whole, with what is known of who sent them and what came of them `spec:cc-agents.coordination.record` behavior	2	defined floor ready	next ready: nothing blocks	18 rules, 18 keyed7 entries6 declarations3 questions0 decisions0 of 0 verifying examples bound	0 implementing0 referencing
A lead states its parent once, and the chain is read from what leads stated `spec:cc-agents.coordination.chain` behavior	3	defined floor ready	next ready: nothing blocks	12 rules, 12 keyed3 entries2 declarations0 questions1 decisions0 of 0 verifying examples bound	0 implementing0 referencing
The person sees the chain and the traffic without asking a model `spec:cc-agents.coordination.view` behavior	4	defined floor ready	next ready: nothing blocks	5 rules, 5 keyed3 entries0 declarations1 questions0 decisions0 of 0 verifying examples bound	0 implementing0 referencing

The architecture it touches

No component is touched and no member designs a component. 2 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
A second session exists only across a boundary one session cannot cross `spec:cc-agents.coordination.boundary-only`	defined floor ready	outside	A lead states its parent once, and the chain is read from what leads stated	0 open, 0 blocking

Open questions in scope

non-blocking · question.clientText · spec:cc-agents.coordination.record · Should the record hold the full text of messages in a project whose material is confidential?Decider: ownerLinks: spec:cc-agents.coordination.adoptionProvisional: Yes, because attribution needs the text. The record stays on the machine where the session ran, and recordText set to metadata for a project replaces the text with its length and hash.
non-blocking · question.correlation · spec:cc-agents.coordination.record · Can a received entry be joined to the sender's sent entry?Decider: delegatedProvisional: No claim is made. Attribution may be unknown or ambiguous. Before a stronger claim is written, it is shown with two peers sending identical text, an ordinary agent message and a resumed session, and no identifier is inserted into any message.
non-blocking · question.auditGrade · spec:cc-agents.coordination.record · Does the owner need crash-proof durability, an audit-grade log?Decider: ownerProvisional: No. The record is observational with stated coverage limits, and a stronger write path waits until someone requires it.
non-blocking · question.language · spec:cc-agents.coordination.session-scanning · Should the scan's scripts stay in Python or move to the plugin's Node?Decider: delegatedProvisional: They stay in Python, on the standard library alone, because their tests exist and a port should change as little as it can. The plugin's own runtime stays Node.
non-blocking · question.pane · spec:cc-agents.coordination.view · Does the chain need a pane beside the chat?Decider: delegatedProvisional: No. The status line and the command are enough for a chain of a top and a few leads, and the existing pane stays about agents.

Where the slice meets the rest

Rests on (2)

Spec	Rung	Implementation binding	Joined members	Holds
Sessions that must message each other leave a record and a place in a chain `spec:cc-agents.coordination`	defined floor ready	none	refines: A scan reads a project's sessions and traces each direction to its outcome, Coordination switches on alone, and a project takes it up with one setting and its own boundaries, Messages between sessions this session saw are kept whole, with what is known of who sent them and what came of them, A lead states its parent once, and the chain is read from what leads stated, The person sees the chain and the traffic without asking a model	none
A second session exists only across a boundary one session cannot cross `spec:cc-agents.coordination.boundary-only`	defined floor ready	none	decidedBy: A lead states its parent once, and the chain is read from what leads stated	none

Rested on by (1)

Spec	Rung	Implementation binding	Joined members	Holds
The one tie between this repository's Specs and HQ's design `spec:cc-agents.hq-links`	defined floor defined	none	dependsOn: A scan reads a project's sessions and traces each direction to its outcome, Coordination switches on alone, and a project takes it up with one setting and its own boundaries, Messages between sessions this session saw are kept whole, with what is known of who sent them and what came of them, A lead states its parent once, and the chain is read from what leads stated	none

Verified by (0)

None.

Superseded by (0)

None.

Composing (0)

Composing needs the script.