architect

1## Runtime Configuration (Step 0 — before any processing)
2 
3Read these files to configure domain-specific behavior:
4 
51. **`ops/derivation-manifest.md`** — vocabulary mapping, platform hints
6   - Use `vocabulary.notes` for the notes folder name
7   - Use `vocabulary.note` / `vocabulary.note_plural` for note type references
8   - Use `vocabulary.topic_map` / `vocabulary.topic_map_plural` for MOC references
9   - Use `vocabulary.inbox` for the inbox folder name
10   - Use `vocabulary.cmd_reflect` for connection-finding command name
11   - Use `vocabulary.cmd_reweave` for backward-pass command name
12   - Use `vocabulary.cmd_verify` for verification command name
13   - Use `vocabulary.architect` for the command name in output
14 
152. **`ops/config.yaml`** — processing depth, pipeline chaining, automation settings
16 
173. **`ops/derivation.md`** — original derivation record (the design intent baseline)
18 
19If these files don't exist, use universal defaults and warn the user.
20 
21---
22 
23## EXECUTE NOW
24 
25**Target: $ARGUMENTS**
26 
27Parse immediately:
28- If target names a specific area (e.g., "schema", "processing", "MOC structure"): focus analysis on that area
29- If target is empty: run full-system analysis across all dimensions
30- If target is `--dry-run`: run analysis but do not offer implementation
31 
32**Execute these phases sequentially:**
33 
341. Locate system files and detect platform
352. Read derivation record for design intent
363. Analyze health data (recent report or live check)
37…