stats

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
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.inbox` for the inbox folder name
10   - Use `vocabulary.notes_collection` for semantic search collection name
11 
122. **`ops/config.yaml`** — processing depth, automation settings
13 
14If no derivation file exists, use universal terms (notes, MOCs, etc.).
15 
16---
17 
18## EXECUTE NOW
19 
20**Target: $ARGUMENTS**
21 
22Parse immediately:
23- If target contains `--share`: output compact shareable format after full stats
24- If target is empty: output full stats display
25- If target names a specific category (e.g., "health", "growth", "pipeline"): show only that category
26 
27**START NOW.** Collect metrics and present them.
28 
29---
30 
31## Philosophy
32 
33**Make the invisible visible.**
34 
35The 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.
36…