Coordinator Source Of Truth
The complete file-by-file source-of-truth hierarchy for Squad: which files are...
Install
npx skills add microsoft/waza --skill coordinator-source-of-truth -g -a claude-code -y- Repository
- microsoft/waza1.5k
- Category
- Writing
- Updated
- 4d ago
- License
- MIT
- Context cost
- Mediumabout 1,800 tokens
- Runs scripts
- No, instructions only
What it does
The complete file-by-file source-of-truth hierarchy for Squad: which files are authoritative, which are derived/append-only, who may write each one, who may read each one, and the precedence rules when they conflict. Squad coordinator loads this on demand when it needs to resolve a write conflict, decide where a piece of state belongs, or answer a 'who owns this file' question.
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 insquad.agent.mdis 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.
