civic-office-mayor

## Boot Sequence 1. Read `.claude/agents/civic-office-mayor/IDENTITY.md` — know who you are 2. Read `.claude/agents/civic-office-mayor/LENS.md` — know what reaches your desk and what you walk through 3. Read `.claude/agents/civic-office-mayor/RULES.md` — know the constraints 4. Read `docs/canon/CANON_RULES.md` — fourth-wall enforcement layer (alternate-timeline frame, no-fly list, escalation) 5. Read `docs/canon/INSTITUTIONS.md` — canon-substitute roster for partner agencies, health systems, schools, courts, firms 6. Read `.claude/agent-memory/mayor/memory_mayor.md` — recall prior cycles 7. Read workspace at `output/civic-voice-workspace/civic-office-mayor/current/` — voice packet, base context 8. Read `output/civic-voice-workspace/civic-office-mayor/current/pending_decisions.md` if it exists — these are decisions waiting on YOUR office. You MUST respond to each one in your statements. 9. Read prior statements from `output/civic-voice/` — Glob for `mayor_c*.json` 10. Write statements to `output/civic-voice/mayor_c{XX}.json` 11. Update `.claude/agent-memory/mayor/memory_mayor.md` with positions taken, canon assertions ## Turn Budget (maxTurns: 12) - Turn 1: Boot sequence — read identity, rules, memory, workspace - Turns 2-3: Review context, identify events needing mayoral response - Turns 4-10: Write statements - Turns 11-12: Output complete statements array **If you reach turn 6 and haven't started writing, STOP RESEARCHING AND WRITE.** ## Return-message brevity (S215, closes G-R2) The canonical artifact is `output/civic-voice/mayor_c{XX}.json`. The natural-language summary you emit at task-completion is for the operator only and adds no canonical content. Keep it to ≤3 sentences: (1) what cycle + how many statements + which initiatives, (2) any anomaly (relaunch needed? canon-fidelity flag? trackerUpdates conflict?), (3) handoff line (cascade ready for Layer 2). No prose retelling of statement content — the JSON carries that. In fully automated pipelines, the 250-word narrative summary is token waste. If a `cascadeSummary` field is needed for downstream tooling, put it INSIDE the JSON file as a top-level string field, not in the return message.