actorThe person sees the chain and the traffic without asking a model
spec:cc-agents.coordination.viewNext rung ready: nothing blocks; it waits only for the author's statement.
Packs: pack:cc-agents-coordination
Design: 3 design entries · no pinned declarations · no decisions
Findings: no errors, no warnings
specs/coordination/view.sdp.md
1 open question and no blocking questions; implementation binding none, verifier binding none, and expected-outcome oracle none.
Intent
- The person watching one session that belongs to a chain.
problem- Coordination is invisible: a lead goes quiet, a message is held or refused, and the person learns it only by asking Claude.
outcome- The person sees where the session stands in its chain, is told when a message arrives or cannot, and can print the chain on demand.
value- A quiet lead, or a session that cannot receive, is noticed by the person within a glance and without spending a turn.
Open questions
- non-blocking ·
question.paneline 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.
Behavior
rule.noModelTurnline 33 ·specs/coordination/view.sdp.md:33- Every view is drawn by the mod and costs no model turn.
no example exercises it
rule.quietUnlessUsefulline 34 ·specs/coordination/view.sdp.md:34- The status line shows only what is true now and useful: the session's place in its chain, or the inbound state when it is
holdorrefuse, labelled as read at start unless it is read again when drawn. It is empty otherwise.no example exercises it
rule.arrivalToastline 35 ·specs/coordination/view.sdp.md:35- A message from another session raises a toast naming its part or short id where the record establishes one, otherwise the peer as the host gave it, or
unknown peer, and it never shows its text.no example exercises it
rule.chainCommandline 36 ·specs/coordination/view.sdp.md:36- The chain command prints the chain of this session as a tree: each session's full id, whether it is top or lead, its part, when it was last heard, and whether a lead has sent its parent a message since it joined, not counting the notice that joining sends: yes, no, or unknown where the record cannot resolve the peer. The mark says only that a message was sent, never that the lead reported or finished.
no example exercises it
rule.readOnlyline 37 ·specs/coordination/view.sdp.md:37- No view changes the chain or the record.
no example exercises it
0 unkeyed rules.
Verification · manual
criteria- With the inbound setting at hold and then at refuse, the status line carries that state from the first prompt, and with it unset or accept it carries none.
- A lead sends its parent a message, and the parent shows the toast without the text and
/chainshows the lead's last heard time. Before that message,/chainshows the lead as having sent nothing although its join notice reached the parent. - Run
/chainand compare usage before and after. No model turn was used.
mode- manual
UI
statusLineline 41 ·specs/coordination/view.sdp.md:41- one line under the prompt, for example
lead of <short id>: <part>,top: 2 leads, orinbound: hold (as read at start). arrivalToastline 42 ·specs/coordination/view.sdp.md:42message from <part or short id>, without text.commandChainline 43 ·specs/coordination/view.sdp.md:43/chain, listed with the descriptionShow this session's chain, which prints the tree without starting a turn.
Verification
Verifier bindings
No verifier binding recorded.
Design view
Requirement drawing
- Declared verifying examples: no declared verifying example.
- Satisfying or referencing units: no recorded binding.
- Test or oracle bindings: no recorded binding.
Arrows: refines (declared).
The diagram as text
- spec:cc-agents.coordination.view: The person sees the chain and the traffic without asking a model · declared Spec · no satisfying binding
- spec:cc-agents.coordination: Sessions that must message each other leave a record and a place in a chain · declared Spec
- spec:cc-agents.coordination.view refines spec:cc-agents.coordination · declared — what the person sees of coordination
Mermaid source
Copyable source; the Studio draws static SVG.
Preferred and chosen syntax: requirementDiagram; exact refines, satisfies and verifies, with claim words in nodes and per-edge comments.
Decisions
No decision record named.
Runtime
No implementation neighborhood recorded.
Runtime observation: not tracked.
Evidence
Runtime observation: not tracked.
Build attestations: not tracked.
Deployments: not tracked.
Bills of materials: not tracked.
Impact
The diagram as text
- spec:cc-agents.coordination: Sessions that must message each other leave a record and a place in a chain
- spec:cc-agents.coordination.chain: A lead states its parent once, and the chain is read from what leads stated
- 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
- spec:cc-agents.coordination.view: The person sees the chain and the traffic without asking a model
- 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.view refines spec:cc-agents.coordination · declared — what the person sees of coordination
Mermaid source
Copyable source; the Studio draws static SVG.
Preferred syntax: flowchart. Chosen syntax: labelled flowchart, preserving exact relations, claims and folds.
Rests on
- refines · spec:cc-agents.coordination · stated defined, floor ready
- dependsOn · spec:cc-agents.coordination.chain · stated defined, floor ready
- dependsOn · spec:cc-agents.coordination.record · stated defined, floor ready
Rested on by
No Spec rests on this Spec.
Relations
| Relation and direction | Other end | Claim | Reason | Exercised keys |
|---|---|---|---|---|
| dependsOn · outgoing | A lead states its parent once, and the chain is read from what leads statedspec:cc-agents.coordination.chain · resolves | declared | the view draws the chain | None |
| dependsOn · outgoing | Messages between sessions this session saw are kept whole, with what is known of who sent them and what came of themspec:cc-agents.coordination.record · resolves | declared | the view reads entries to say what was heard and when | None |
| refines · outgoing | Sessions that must message each other leave a record and a place in a chainspec:cc-agents.coordination · resolves | declared | what the person sees of coordination | None |
Bindings
Implementation binding: none
Design reference: none
Verifier binding: none
Expected-outcome oracle: none
Runtime observation: not tracked.
Run results: not recorded in the graph.
Findings
None.
Composing (0)
Composing needs the script.