next

## Runtime Configuration (Step 0 — before any processing) Read these files to configure domain-specific behavior: 1. **`ops/derivation-manifest.md`** — vocabulary mapping, domain context - Use `vocabulary.notes` for the notes folder name - Use `vocabulary.inbox` for the inbox folder name - Use `vocabulary.note` for the note type name in output - Use `vocabulary.topic_map` for MOC references - Use `vocabulary.cmd_reduce` for process/extract command - Use `vocabulary.cmd_reflect` for connection-finding command - Use `vocabulary.cmd_reweave` for backward-pass command - Use `vocabulary.rethink` for rethink command name 2. **`ops/config.yaml`** — thresholds, processing preferences - `self_evolution.observation_threshold` (default: 10) - `self_evolution.tension_threshold` (default: 5) If these files don't exist, use universal defaults and generic command names. ## EXECUTE NOW **INVARIANT: /next recommends, it does not execute.** Present one recommendation with rationale. The user decides what to do. This prevents cognitive outsourcing where the system makes all work decisions and the user becomes a rubber stamp. **Execute these steps IN ORDER:** --- ### Step 1: Read Vocabulary Read `ops/derivation-manifest.md` (or fall back to `ops/derivation.md`) for domain vocabulary mapping. All output must use domain-native terms. If neither file exists, use universal terms (notes, inbox, topic map, etc). --- ### Step 2: Reconcile Maintenance Queue Bef...