next

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, domain context
6   - Use `vocabulary.notes` for the notes folder name
7   - Use `vocabulary.inbox` for the inbox folder name
8   - Use `vocabulary.note` for the note type name in output
9   - Use `vocabulary.topic_map` for MOC references
10   - Use `vocabulary.cmd_reduce` for process/extract command
11   - Use `vocabulary.cmd_reflect` for connection-finding command
12   - Use `vocabulary.cmd_reweave` for backward-pass command
13   - Use `vocabulary.rethink` for rethink command name
14 
152. **`ops/config.yaml`** — thresholds, processing preferences
16   - `self_evolution.observation_threshold` (default: 10)
17   - `self_evolution.tension_threshold` (default: 5)
18 
19If these files don't exist, use universal defaults and generic command names.
20 
21## EXECUTE NOW
22 
23**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.
24 
25**Execute these steps IN ORDER:**
26 
27---
28 
29### Step 1: Read Vocabulary
30 
31Read `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).
32 
33---
34 
35### Step 2: Reconcile Maintenance Queue
36…