| name | knowledge-compilation |
| description | Tactic for compiling research findings into vault pages — orchestrates page creation, updates, edge linking, and index maintenance. Minimum yield ≥3 page operations per invocation. |
| execution | tactic |
| dependencies | {"sops":["wiki-add-edge","wiki-compile-page","wiki-edge-audit","wiki-graph-query","wiki-ingest-source","wiki-lint-fix","wiki-search"]} |
Knowledge Compilation
Compile research findings into structured vault pages. Triggered after each strategy completes, or when CC judges accumulated information density warrants compilation.
Available SOPs
wiki-search — check for existing pages before creating duplicateswiki-ingest-source — write immutable source pageswiki-compile-page — create/update wiki pages with edgeswiki-add-edge — create typed relationships between pageswiki-lint-fix — run lint in report mode at end
Guiding Principles
- Assess before acting. Scan incoming material. Identify what's new vs what updates existing pages.
- Deduplication first. Always search before creating. Near-duplicates should be merged, not added.
- Edges are first-class. Every new page should have at least one edge connecting it to the existing graph. Orphans are failures.
≥3 page operations per invocation (any combination of: create page, update page, add edge).
If incoming material cannot produce 3 operations, accumulate and defer.
