graph

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.cmd_reflect` for connection-finding command name
10   - Use `vocabulary.cmd_reweave` for backward-pass command name
11 
122. **`ops/config.yaml`** — for graph thresholds (MOC size limits, orphan thresholds)
13 
14If no derivation file exists, use universal terms (notes, MOCs, etc.).
15 
16---
17 
18## EXECUTE NOW
19 
20**Target: $ARGUMENTS**
21 
22Parse the operation from arguments:
23- If arguments match a known operation: route to that operation
24- If arguments are a natural language question: map to the closest operation (see Interactive Mode)
25- If no arguments: enter interactive mode
26 
27**START NOW.** Route to the appropriate operation.
28 
29---
30 
31## Philosophy
32 
33**The graph IS the knowledge. This skill makes it visible.**
34 
35Individual {vocabulary.note_plural} are valuable, but their connections create compound value. /graph reveals the structural properties of those connections — where the graph is dense, where it is sparse, where it is fragile, and where synthesis opportunities hide.
36…