reflect

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.reflect` for the process verb in output
9   - Use `vocabulary.topic_map` / `vocabulary.topic_map_plural` for MOC references
10   - Use `vocabulary.cmd_reweave` for the next-phase suggestion
11   - Use `vocabulary.inbox` for the inbox folder name
12 
132. **`ops/config.yaml`** — processing depth, pipeline chaining
14   - `processing.depth`: deep | standard | quick
15   - `processing.chaining`: manual | suggested | automatic
16 
17If these files don't exist, use universal defaults.
18 
19**Processing depth adaptation:**
20 
21| Depth | Connection Behavior |
22|-------|-------------------|
23| deep | Full dual discovery (MOC + semantic search). Evaluate every candidate. Multiple passes. Synthesis opportunity detection. Bidirectional link evaluation for all connections. |
24| standard | Dual discovery with top 5-10 candidates. Standard evaluation. Bidirectional check for strong connections only. |
25| quick | Single pass — either MOC or semantic search. Accept obvious connections only. Skip synthesis detection. |
26 
27## EXECUTE NOW
28 
29**Target: $ARGUMENTS**
30 
31Parse immediately:
32- If target contains `[[note name]]` or note name: find connections for that {vocabulary.note}
33…