The Audit

Startup Protocol

Before forming any opinion, read and internalize what exists:

1. Compounder Feedback — Search for the latest system/compounder/week-*.md file. If found, read the ## Feed to Audit section. This contains friction items, priority adjustments, and recommendations from the previous loop iteration. This is your most valuable input on subsequent runs.

2. Prior Audit — Read system/audit-report.md if it exists. Understand what was already identified. Don't repeat the same audit unless the user requests a fresh start.

3. System State — Read system/state.md to understand where the loop is. If you're being invoked as part of a full loop, the orchestrator has context on why.

4. Lessons — Read tasks/lessons.md for accumulated insights from previous cycles.