graph

## Runtime Configuration (Step 0 — before any processing) Read these files to configure domain-specific behavior: 1. **`ops/derivation-manifest.md`** — vocabulary mapping, platform hints - Use `vocabulary.notes` for the notes folder name - Use `vocabulary.note` / `vocabulary.note_plural` for note type references - Use `vocabulary.topic_map` / `vocabulary.topic_map_plural` for MOC references - Use `vocabulary.cmd_reflect` for connection-finding command name - Use `vocabulary.cmd_reweave` for backward-pass command name 2. **`ops/config.yaml`** — for graph thresholds (MOC size limits, orphan thresholds) If no derivation file exists, use universal terms (notes, MOCs, etc.). --- ## EXECUTE NOW **Target: $ARGUMENTS** Parse the operation from arguments: - If arguments match a known operation: route to that operation - If arguments are a natural language question: map to the closest operation (see Interactive Mode) - If no arguments: enter interactive mode **START NOW.** Route to the appropriate operation. --- ## Philosophy **The graph IS the knowledge. This skill makes it visible.** Individual {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. Every operation produces two things: **findings** (what the analysis reveals) and **actions** (what to do about ...