coordination-memory

Coordination Memory

Follow the Coordination Memory protocol in AGENTS.md at the repository root (the section between the coordination-memory markers).

Key rules:

• completed_gate_passed is not accepted truth; only an integrator accept_event makes work accepted.
• Always claim_assignment before working, and pass the current base_revision on mutating calls.
• Discover with list_workspaces, then use get_workspace_detail (workspace_id) for compact teams and assignment counts. Choose one team and pass its required team_id to get_team_board, list_pending_reviews, get_snapshot, list_contracts, and get_attention_board before high-volume reads; there is no pagination.
• Use get_event_detail, get_assignment_detail, get_run_detail, or get_contract_detail only after choosing a specific ID from a compact read.
• get_team_board returns only assignment_id, title, and status. get_team_board.status is an optional, one exact status filter; omitting it excludes accepted, rejected, cancelled, and superseded. Call get_assignment_detail for the full task contract.
• Only these eleven Ack tools return a compact acknowledgement without a payload echo: append_event, submit_handoff, heartbeat_run, checkpoint_run, raise_attention, record_run_binding, request_intervention, respond_intervention, review_event, accept_event, and reject_event.
• claim_assignment and actor/workspace/team/assignment/contract mutations retain their existing responses; keep using active_run_id from claim_assignment.
• For loop-dispatched work, treat the assignment as the task contract: read metadata.context_refs, obey allowed_paths and acceptance_criteria, and use metadata.session_bind.target_actor_id as the intended worker binding before any run exists. Keep run communication metadata current with record_run_binding after the conversation starts.