Coordination roadmap
pack:cc-agents-coordinationspecs/coordination/coordination.pack.sdp.mdDownload this Pack as one file
Where the design stands
- 5 members in priority order; no unresolved members.
- No members held below their stated next rung.
- 5 members waiting only for their author's statement.
- 17 design entries and 11 pinned declarations.
- 5 open questions and no blocking questions.
- No members with an implementation binding.
- No members with a design reference.
- 2 outside Specs the Pack rests on; 1 outside Spec rests on the Pack; no outside Specs verify it; no outside Specs supersede it.
Maturity map
5 members at stated defined and floor ready: full member list.
Stated readiness by floor reached
Outlined diagonal: matches. Right of diagonal: floor above statement. Left of diagonal: statement above floor.
Maturity map as text
| Stated rung / floor reached | floor none | floor idea | floor scoped | floor defined | floor ready |
|---|---|---|---|---|---|
| stated idea | — | — | — | — | — |
| stated scoped | — | — | — | — | — |
| stated defined | — | — | — | — | 5 |
| stated ready | — | — | — | — | — |
stated defined, floor ready · 5 members
- A scan reads a project's sessions and traces each direction to its outcome ·
spec:cc-agents.coordination.session-scanning· defined floor ready - Coordination switches on alone, and a project takes it up with one setting and its own boundaries ·
spec:cc-agents.coordination.adoption· defined floor ready - 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· defined floor ready - A lead states its parent once, and the chain is read from what leads stated ·
spec:cc-agents.coordination.chain· defined floor ready - The person sees the chain and the traffic without asking a model ·
spec:cc-agents.coordination.view· defined floor ready
Mermaid source
Preferred syntax: block. Fixed categorical cells; membership appears in comments.
Framing
The order of delivery, first entry first, smallest valuable piece first. Session scanning comes first because it needs nothing else here and exists today, so moving it is a port and not a build. After it, each entry rests on the ones before it. The switch and the inbound check come first because they let coordination be on while the job runner is off, and they report the session's real inbound state at start; the first piece is the separate plugin and that accurate diagnostic, and it keeps nothing, since the record comes later. The record comes next because it needs no chain and gives readers every message at once. The chain follows, then the view that shows it. Nothing here is built.
Members
1. A scan reads a project's sessions and traces each direction to its outcomebehavior · defined floor ready · next rung ready: nothing blocks · 1 open, 0 blocking questions · implementation binding none · verifier binding none
spec:cc-agents.coordination.session-scanning
Next rung ready: nothing blocks; it waits only for the author's statement.
Design
No design entries · no pinned declarations
Open questions
- non-blocking · question.language
· line 25 · specs/coordination/session-scanning.sdp.md:25· 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.
Implementation binding: none
Design reference: none
Verifier binding: none
2. Coordination switches on alone, and a project takes it up with one setting and its own boundariesbehavior · defined floor ready · next rung ready: nothing blocks · 0 open, 0 blocking questions · implementation binding none · verifier binding none
spec:cc-agents.coordination.adoption
Next rung ready: nothing blocks; it waits only for the author's statement.
Design
4 design entries · 3 pinned declarations
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: none
3. Messages between sessions this session saw are kept whole, with what is known of who sent them and what came of thembehavior · defined floor ready · next rung ready: nothing blocks · 3 open, 0 blocking questions · implementation binding none · verifier binding none
spec:cc-agents.coordination.record
Next rung ready: nothing blocks; it waits only for the author's statement.
Design
7 design entries · 6 pinned declarations
Open questions
- non-blocking · question.clientText
· line 27 · specs/coordination/record.sdp.md:27· 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, andrecordTextset tometadatafor a project replaces the text with its length and hash. - non-blocking · question.correlation
· line 31 · specs/coordination/record.sdp.md:31· 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
· line 34 · specs/coordination/record.sdp.md:34· 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.
Implementation binding: none
Design reference: none
Verifier binding: none
4. A lead states its parent once, and the chain is read from what leads statedbehavior · defined floor ready · next rung ready: nothing blocks · 0 open, 0 blocking questions · implementation binding none · verifier binding none
spec:cc-agents.coordination.chain
Next rung ready: nothing blocks; it waits only for the author's statement.
Design
3 design entries · 2 pinned declarations
Decisions
Open questions
None.
Implementation binding: none
Design reference: none
Verifier binding: none
5. The person sees the chain and the traffic without asking a modelbehavior · defined floor ready · next rung ready: nothing blocks · 1 open, 0 blocking questions · implementation binding none · verifier binding none
spec:cc-agents.coordination.view
Next rung ready: nothing blocks; it waits only for the author's statement.
Design
3 design entries · no pinned declarations
Open questions
- non-blocking · question.pane
· line 27 · specs/coordination/view.sdp.md:27· 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.
Implementation binding: none
Design reference: none
Verifier binding: none
Boundary
Rests on (2)
| Spec | Stated rung | Implementation binding | Joined members |
|---|---|---|---|
Sessions that must message each other leave a record and a place in a chainspec:cc-agents.coordination | defined | none | refines: spec:cc-agents.coordination.session-scanning, spec:cc-agents.coordination.adoption, spec:cc-agents.coordination.record, spec:cc-agents.coordination.chain, spec:cc-agents.coordination.view |
A second session exists only across a boundary one session cannot crossspec:cc-agents.coordination.boundary-only | defined | none | decidedBy: spec:cc-agents.coordination.chain |
Rested on by (1)
| Spec | Stated rung | Implementation binding | Joined members |
|---|---|---|---|
The one tie between this repository's Specs and HQ's designspec:cc-agents.hq-links | defined | none | dependsOn: spec:cc-agents.coordination.session-scanning, spec:cc-agents.coordination.adoption, spec:cc-agents.coordination.record, spec:cc-agents.coordination.chain |
Verified by (0)
None.
Superseded by (0)
None.
Members with no verifier binding
The graph records bindings and never runs, so no page shows a run result. Decision records are left out: a decision never needs a verifier binding.
- A scan reads a project's sessions and traces each direction to its outcome ·
spec:cc-agents.coordination.session-scanning· stated defined - Coordination switches on alone, and a project takes it up with one setting and its own boundaries ·
spec:cc-agents.coordination.adoption· stated defined - 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· stated defined - A lead states its parent once, and the chain is read from what leads stated ·
spec:cc-agents.coordination.chain· stated defined - The person sees the chain and the traffic without asking a model ·
spec:cc-agents.coordination.view· stated defined
Findings
None.
Composing (0)
Composing needs the script.