Cross-Repo Coordination And Overseer Playbook — {{repo.name}}

Status: Coordination doc — process, not product. Explains where work happens, how repos stay in sync, which boundaries must not be crossed, and how to hand the overseer chat off without losing cross-repo context.

Related:

• {{docs.roadmap_path}} — phase control + build status
• {{docs.handover_path}} — living, always-current filled handover block
• {{docs.standing_decisions_path}} — Standing Decisions (ADR) log + decision authority tiers
• policy/tiers.yaml, policy/model-labels.yaml, policy/test-tiers.yaml — machine-readable policy

Simple summary

Governance habits (handover, roadmap, testing discipline, merge authority, model labels) must stay consistent across connected repos. This page is the map: where each kind of change goes, what must never break, and how one chat hands the baton to the next so the overseer view is reconstructable from durable docs — not chat scrollback.

Technical summary

VCS regime for this repo: {{vcs.regime}} (canonical: {{vcs.canonical}}). Coordination uses: (1) a clear ownership/decision table, (2) per-repo VCS discipline, (3) explicit non-overstep boundaries, (4) a canonical-document map, and (5) an overseer handover protocol with a paste-able state snapshot.

Version control (this repo)

Shared rules: never work directly on {{vcs.git.main_branch}}; feature branch per task; never commit secrets or ignored paths. Say "Muse commit" vs "Git commit" explicitly when both histories apply.

Regime-specific hard stops

Cross-repo Muse safety: when driving Muse from an agent, always use explicit muse -C <absolute-repo-root> <command> and confirm branch + HEAD before any cross-repo operation.

Boundaries we do not overstep

• Review-before-write for durable knowledge changes.
• No secrets across repo boundaries — tokens, keys, and private content never in adapters, logs, or shared procedures.
• Canonical-first ordering — do not wire a consumer before the surface it reads exists.
• Governance sync (SD-17) — update {{docs.roadmap_path}} + {{docs.handover_path}} before session end.

Canonical documents map (this repo)

The overseer role and handover protocol

Overseer chat tracks state, decides what goes next, and guards boundaries. State must always be reconstructable from durable docs, not chat history.

Durable state of record:

1. {{docs.roadmap_path}} — phase truth + build status.
2. {{docs.handover_path}} — living filled handover block (single paste source).
3. {{docs.standing_decisions_path}} — tiers + ADR log.
4. This doc — boundaries + decision table (when docs.coordination is configured).

Docs-first ordering: (1) update durable docs to match reality, (2) regenerate {{docs.handover_path}} from those docs, (3) emit/paste the NEXT block. Never hand-write the block from memory ahead of the docs.

Handover snapshot shape (filled into {{docs.handover_path}}):

OVERSEER HANDOVER — <date/time>
Initiative + current step: <step-id>
Build order / next action: <action>

Per-repo state:
- {{repo.name}}: branch <feat/...>  last <vcs> <sha>  dirty? <y/n>

Open gates / blockers: <list>
Boundaries to honor: <list>
Links: {{docs.roadmap_path}}; {{docs.handover_path}}

Decision authority (three tiers)

Machine-readable copy: policy/tiers.yaml.

Commit rule: committing on a feature branch is Tier 1. Pushing to staging or merging to {{vcs.git.main_branch}} is Tier 3. Leaving durable doc edits uncommitted is the worse state.

Recommended Flow: Overseer handover

Scope: session end, chat switch, or multi-repo state in flight. Docs-first. Use the installed kit (ok status, ok governance-sync) — do not maintain a parallel hand-rolled handover script.

Model-split handover protocol (SD-3)

When the roadmap Model column for NEXT contains →, see {{docs.standing_decisions_path}} and policy/model-labels.yaml. Emit {step}a then {step}b — not one combined prompt.

Seven-tier test contract (RULE #0)

Every Build phase that adds code ships all seven tiers. See policy/test-tiers.yaml for the machine-readable matrix and what each tier must prove.