mirror of
https://github.com/shareAI-lab/analysis_claude_code.git
synced 2026-03-22 02:15:42 +08:00
105 lines
3.8 KiB
Markdown
105 lines
3.8 KiB
Markdown
# s10: Team Protocols
|
|
|
|
`s01 > s02 > s03 > s04 > s05 > s06 | s07 > s08 > s09 > [ s10 ] s11 > s12`
|
|
|
|
> *"Same request_id, two protocols"* -- one FSM pattern powers shutdown + plan approval.
|
|
|
|
## Problem
|
|
|
|
In s09, teammates work and communicate but lack structured coordination:
|
|
|
|
**Shutdown**: Killing a thread leaves files half-written and config.json stale. You need a handshake: the lead requests, the teammate approves (finish and exit) or rejects (keep working).
|
|
|
|
**Plan approval**: When the lead says "refactor the auth module," the teammate starts immediately. For high-risk changes, the lead should review the plan first.
|
|
|
|
Both share the same structure: one side sends a request with a unique ID, the other responds referencing that ID.
|
|
|
|
## Solution
|
|
|
|
```
|
|
Shutdown Protocol Plan Approval Protocol
|
|
================== ======================
|
|
|
|
Lead Teammate Teammate Lead
|
|
| | | |
|
|
|--shutdown_req-->| |--plan_req------>|
|
|
| {req_id:"abc"} | | {req_id:"xyz"} |
|
|
| | | |
|
|
|<--shutdown_resp-| |<--plan_resp-----|
|
|
| {req_id:"abc", | | {req_id:"xyz", |
|
|
| approve:true} | | approve:true} |
|
|
|
|
Shared FSM:
|
|
[pending] --approve--> [approved]
|
|
[pending] --reject---> [rejected]
|
|
|
|
Trackers:
|
|
shutdown_requests = {req_id: {target, status}}
|
|
plan_requests = {req_id: {from, plan, status}}
|
|
```
|
|
|
|
## How It Works
|
|
|
|
1. The lead initiates shutdown by generating a request_id and sending through the inbox.
|
|
|
|
```python
|
|
shutdown_requests = {}
|
|
|
|
def handle_shutdown_request(teammate: str) -> str:
|
|
req_id = str(uuid.uuid4())[:8]
|
|
shutdown_requests[req_id] = {"target": teammate, "status": "pending"}
|
|
BUS.send("lead", teammate, "Please shut down gracefully.",
|
|
"shutdown_request", {"request_id": req_id})
|
|
return f"Shutdown request {req_id} sent (status: pending)"
|
|
```
|
|
|
|
2. The teammate receives the request and responds with approve/reject.
|
|
|
|
```python
|
|
if tool_name == "shutdown_response":
|
|
req_id = args["request_id"]
|
|
approve = args["approve"]
|
|
shutdown_requests[req_id]["status"] = "approved" if approve else "rejected"
|
|
BUS.send(sender, "lead", args.get("reason", ""),
|
|
"shutdown_response",
|
|
{"request_id": req_id, "approve": approve})
|
|
```
|
|
|
|
3. Plan approval follows the identical pattern. The teammate submits a plan (generating a request_id), the lead reviews (referencing the same request_id).
|
|
|
|
```python
|
|
plan_requests = {}
|
|
|
|
def handle_plan_review(request_id, approve, feedback=""):
|
|
req = plan_requests[request_id]
|
|
req["status"] = "approved" if approve else "rejected"
|
|
BUS.send("lead", req["from"], feedback,
|
|
"plan_approval_response",
|
|
{"request_id": request_id, "approve": approve})
|
|
```
|
|
|
|
One FSM, two applications. The same `pending -> approved | rejected` state machine handles any request-response protocol.
|
|
|
|
## What Changed From s09
|
|
|
|
| Component | Before (s09) | After (s10) |
|
|
|----------------|------------------|------------------------------|
|
|
| Tools | 9 | 12 (+shutdown_req/resp +plan)|
|
|
| Shutdown | Natural exit only| Request-response handshake |
|
|
| Plan gating | None | Submit/review with approval |
|
|
| Correlation | None | request_id per request |
|
|
| FSM | None | pending -> approved/rejected |
|
|
|
|
## Try It
|
|
|
|
```sh
|
|
cd learn-claude-code
|
|
python agents/s10_team_protocols.py
|
|
```
|
|
|
|
1. `Spawn alice as a coder. Then request her shutdown.`
|
|
2. `List teammates to see alice's status after shutdown approval`
|
|
3. `Spawn bob with a risky refactoring task. Review and reject his plan.`
|
|
4. `Spawn charlie, have him submit a plan, then approve it.`
|
|
5. Type `/team` to monitor statuses
|