Find health reports from the last 7 days

Runtime Configuration (Step 0 — before any processing)

Read these files to configure domain-specific behavior:

1. ops/derivation-manifest.md — vocabulary mapping, platform hints

   • Use vocabulary.notes for the notes folder name
   • Use vocabulary.note / vocabulary.note_plural for note type references
   • Use vocabulary.topic_map / vocabulary.topic_map_plural for MOC references
   • Use vocabulary.inbox for the inbox folder name
   • Use vocabulary.cmd_reflect for connection-finding command name
   • Use vocabulary.cmd_reweave for backward-pass command name
   • Use vocabulary.cmd_verify for verification command name
   • Use vocabulary.architect for the command name in output

2. ops/config.yaml — processing depth, pipeline chaining, automation settings

3. ops/derivation.md — original derivation record (the design intent baseline)

If these files don't exist, use universal defaults and warn the user.

EXECUTE NOW

Target: $ARGUMENTS

Parse immediately:

• If target names a specific area (e.g., "schema", "processing", "MOC structure"): focus analysis on that area
• If target is empty: run full-system analysis across all dimensions
• If target is --dry-run: run analysis but do not offer implementation

Execute these phases sequentially:

1. Locate system files and detect platform
2. Read derivation record for design intent
3. Analyze health data (recent report or live check)
4. Scan for friction patterns across operational surfaces
5. Consult research to ground evidence in specific claims
6. Generate 3-5 ranked recommendations with full evidence chains
7. Present to user and implement on approval