stats

## Runtime Configuration (Step 0 — before any processing) Read these files to configure domain-specific behavior: 1. **`ops/derivation-manifest.md`** — vocabulary mapping - 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.inbox` for the inbox folder name - Use `vocabulary.notes_collection` for semantic search collection name 2. **`ops/config.yaml`** — processing depth, automation settings If no derivation file exists, use universal terms (notes, MOCs, etc.). --- ## EXECUTE NOW **Target: $ARGUMENTS** Parse immediately: - If target contains `--share`: output compact shareable format after full stats - If target is empty: output full stats display - If target names a specific category (e.g., "health", "growth", "pipeline"): show only that category **START NOW.** Collect metrics and present them. --- ## Philosophy **Make the invisible visible.** The knowledge graph grows silently. Without metrics, the user cannot tell whether their system is healthy, growing, stagnating, or fragmenting. /stats provides a snapshot that makes growth tangible — numbers that show progress, health indicators that catch problems, and trends that reveal trajectory. The output should make the user feel informed, not overwhelmed. Metrics are evidence, not judgment. "12 orphans" is a fact. What to DO about ...