coordinator-source-of-truth

Load this skill when: the coordinator (or any agent) needs to resolve a "where does this state belong?" or "who is allowed to write this file?" question — e.g., when about to write .squad/decisions.md, when reviewing whether an agent broke the append-only rule, when answering a user question about Squad's file layout, or when adjudicating a conflict between two files. The short summary in squad.agent.md is for routing; this skill is the full reference.

State backend note

Files below marked as "Derived / append-only" are mutable state — agents access them with runtime state tools (squad_state_read, squad_state_write, squad_state_append, squad_state_delete, squad_state_list). The runtime decides whether the configured backend stores them on disk, git-native state, or an external provider. Files marked as "Authoritative" are static config and always live on disk regardless of backend.

File hierarchy

Waza support-review override (Squad only): Charter output/persistence restrictions take precedence over generic history, audit-trail or decision-inbox write permissions below. Rai and Fact Checker return findings in the current review response. Only an authorized coordinator or Scribe handles required persistence under the current state contract; no routine review logging is required. Preserve existing historical records. Scribe remains bound by its charter: a decision-only Scribe cannot write logs, histories or audit trails. The Coordinator arranges any required non-decision persistence through an authorized writer; a missing writer is a blocker, not permission for Scribe. These coordination rules do not apply to ordinary Copilot work.

Rules

1. If squad.agent.md and any other file conflict, squad.agent.md wins. It is the only file with hard governance authority.
2. Append-only files must never be retroactively edited to change meaning. They are diagnostic and audit-trail material. Corrections go in a new entry that references the prior one.
3. Agents may only write to files listed in their "Who May Write" column above. Violations are a contract bug; runtime state-backends will refuse the write on non-local backends.
4. Non-coordinator agents may propose decisions in their responses. Coordinator alone accepts decisions; only the Coordinator or a coordinator-delegated Scribe may record already-accepted decisions in .squad/decisions.md.
5. Waza casting repair: write authority does not permit raw registry/history edits. All casting mutations, including initialization and retirement, must commit the pair and manifest through .squad/casting-transactions.md; use an equivalent atomic backend operation or stop on non-local storage.
6. Legacy is not a recovery fallback. SDK preparation validates existing state before callbacks. The known frozen v0.10 files require the guide's explicit approved archive-and-initialize maintenance procedure into an empty target; managed-pair corruption or a missing manifest must never trigger that path.