coordinate-project-relay

Coordinate project relay

Use the MCP as a shared operational memory, not as a generic note store.

Start safely

1. Detect the repository root and project marker without modifying files.
2. Resolve the known project id and call project_association_check before any project knowledge tool.
3. Stop without reading or writing shared context when the result is not associated and active.
4. Ask the user before registering, activating, splitting, merging, or archiving a project. Call project_register only after explicit approval and set approvedByUser: true only when that approval actually occurred.
5. Call participant_register for the effective human and agent after explicit approval. Record model, specialties and capabilities using unknown rather than guessing. Reuse an identical registered profile instead of creating aliases.
6. Start collaboration with session_start for each actor before meaningful editing, and keep sessions alive with session_heartbeat.

Synchronize work

1. Call knowledge_query with afterRevision when a project cursor is available; otherwise query the relevant terms, services, components and constraints.
2. Surface newer revisions and overlapping scopes before changing related components. Use active_sessions and heartbeat signals to reason about in-flight work from other actors.
3. Identify relevant projects, services, connections, rules and modification considerations.
4. Re-synchronize before modifying a shared contract or a scope claimed by another session.

Preserve causality

For each meaningful modification, capture:

• observed problem or requested outcome;
• cause and certainty: observed, hypothesis, confirmed, refuted, or unknown;
• rules, limits and invariants that must remain true;
• services or cross-project connections imposing constraints;
• affected paths, components, interfaces and environments;
• risks if the behavior changes again;
• evidence and checks actually performed;
• pending work and review conditions.