03.3 / Yukh system / Coordination
A shared room for work that happens in separate minds.
Sessions are isolated. Delivery is not. Coordination provides a neutral channel for ownership, questions, evidence, review and explicit handoff.
Status: preparation evidence complete. The protocol, security boundaries and reproducible OCI evidence exist, but there is no public or live runtime and the project is not production-ready.
The problem
Parallel agents and people cannot see one another's transient context. Silence becomes ambiguous, work is duplicated and handoffs decay into inference.
Responsibility
Make cross-session activity legible through open presence, bounded claims, typed signals, evidence references and explicit transfer of work.
Authority boundary
Coordination transports and records signals. It does not grant capability, accept project mutations, supervise participants or convert message delivery into authority.
Public contracts
- Presence: who is active, idle, blocked or gone.
- Claims: which bounded outcome a participant currently owns.
- Signals: progress, question, answer, review request and verdict.
- Evidence: immutable references to commits, runs, fixtures and decisions.
- Handoffs: explicit transfer without guessing from silence or elapsed time.
How it interacts
Projects supplies durable delivery context. MCP supplies governed capabilities and execution evidence. Coordination connects participants to those systems without becoming either one.
Next direction
Authorize and qualify publication and a live runtime separately, then complete the end-to-end multi-session proof. Preparation and protocol conformance remain independent from deployment readiness.