Coordination without invisible orchestration.

Status: preparation evidence complete. Protocol, security-boundary and reproducible runtime preparation evidence exists, but there is no public/live runtime qualification and the project is not production-ready.

The problem

Parallel agents and people cannot rely on one another's transient context. Without explicit coordination, silence becomes ambiguous, work is duplicated and handoff or authority is inferred from chat behavior.

Responsibility

Make cross-session work legible through participant attribution, bounded claims, observable conflict, typed signals, evidence references and explicit handoff.

Authority boundary

Coordination records and transports coordination facts. Messaging, acknowledgement, timeouts, workspace roles or coordinator recommendations never grant execution or accepted-state authority by themselves.

Public contracts

• Presence: which participant is active, idle, blocked or gone without making presence authoritative.
• Claims: which bounded work a participant currently claims, including observable concurrent conflict.
• Signals: progress, question, answer, review request and verdict as typed coordination events.
• Evidence refs: portable references to commits, runs, fixtures and decisions rather than private reasoning.
• Handoffs: explicit transfer with accepted boundaries instead of guessing from silence or elapsed time.

How it interacts

Accepted-state implementations provide reviewed delivery context. MCP supplies capability/evidence semantics. Buzz, Matrix, IDEs or other human-agent workspaces may become replaceable interaction surfaces, but they must not redefine Yukh claims, authority or handoff semantics.

Next direction

Keep the semantic kernel small while qualifying external workspace and transport surfaces. Publication/live runtime qualification remains separate from protocol correctness, and replacing UI or messaging machinery should not require changing Yukh-visible coordination contracts.