reweave

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.reweave` for the process verb in output
9   - Use `vocabulary.topic_map` / `vocabulary.topic_map_plural` for MOC references
10   - Use `vocabulary.cmd_verify` for the next-phase suggestion
11 
122. **`ops/config.yaml`** — processing depth, pipeline chaining
13   - `processing.depth`: deep | standard | quick
14   - `processing.chaining`: manual | suggested | automatic
15   - `processing.reweave.scope`: related | broad | full
16 
17If these files don't exist, use universal defaults.
18 
19**Processing depth adaptation:**
20 
21| Depth | Reweave Behavior |
22|-------|-----------------|
23| deep | Full reconsideration. Search extensively for newer related {vocabulary.note_plural}. Consider splits, rewrites, challenges. Evaluate claim sharpening. Multiple search passes. |
24| standard | Balanced review. Search semantic neighbors and same-{vocabulary.topic_map} {vocabulary.note_plural}. Add connections, sharpen if needed. |
25| quick | Minimal backward pass. Add obvious connections only. No rewrites or splits. |
26 
27**Reweave scope:**
28 
29| Scope | Behavior |
30|-------|----------|
31…