Step-by-step guide for the wiki synthesis layer: how to compile new insights, update existing pages, run health checks, and integrate the wiki into the standard source ingestion pipeline.
The knowledge wiki is the synthesis layer above raw source texts. It is maintained through three Claude Code skills and integrates with the existing publication pipeline. This guide covers everything from daily use to the full ingestion-to-wiki workflow.
Source texts (knowledge/sources/)
│
▼
Wiki synthesis (knowledge/wiki/) ← new layer
├── entities/ — who/what
├── concepts/ — ideas and themes
└── connections/ — cross-tradition comparisons
│
├──→ @import in .claude/CLAUDE.md ──→ ambient in every Claude Code session
│
└──→ RAG retrieval (Upstash Vector / Open WebUI)
│
▼
Cosmo AI responses
The wiki index is always in Claude Code's context via a single directive at the bottom of .claude/CLAUDE.md:
@knowledge/wiki/index.md
Claude Code expands @path references inline at session start — the entire wiki index becomes part of the starting context before any message is sent. This is what makes it ambient: Claude doesn't look it up, it simply knows it.
Important distinction: A regular markdown link
[wiki](../wiki/index)is navigational only — it does not cause the file to load. The@prefix is the loading mechanism..claude/CLAUDE.mdneeds both: a link in Essential Files (for human navigation) and the@directive at the bottom (for ambient loading). If either is missing, the other alone is insufficient.
From the wiki index, Claude Code sees a structured table of contents: entity summaries (e.g., "Plato: Athenian philosopher; 12 dialogues; justice, the Good, the soul"), concept summaries (e.g., "impermanence: Buddhist anicca, Taoist flux, Whitman's cycles, Nietzsche's eternal recurrence"), and cross-tradition connections. This gives full corpus orientation — shape, not depth — without loading any source documents.
Full architecture: docs/architecture.md § Cosmo's Session Context
| Skill | When to use |
|---|---|
/knowledge-compile | After learning something durable — compile it to the wiki |
/knowledge-review | Periodic health check — orphans, staleness, symmetry, open questions |
/knowledge-lookup <query> | Before deep domain work — see what the wiki already knows |
The cardinal rule: compile when you learn something, not on a schedule.
When a conversation surfaces a cross-tradition synthesis worth keeping:
/knowledge-compile convo
Claude will extract the durable insight, check whether a relevant wiki page already exists, and either update it or create a new one.
Good candidates for compilation:
Not worth compiling:
The full pipeline is now: stage → groom → publish → wiki-update
1. Stage
pbpaste > knowledge/incoming/my-text.md
2. Groom (format the raw text)
/groom knowledge/incoming/my-text.md
3. Publish (frontmatter generation + corpus indexing)
pnpm knowledge:publish knowledge/incoming/my-text.md --role source --domain <domain>
4. Wiki update (synthesize into wiki)
/knowledge-compile log
Step 4 scans recent CURATION_LOG entries and updates the wiki pages affected by the new source document. For a new Platonic dialogue, for example, it would:
wiki/entities/plato.md to add the dialogue to synthesizesRun monthly or before a major synthesis session:
/knowledge-review
The review identifies:
last_reviewed > 90 days agoBefore a deep domain conversation with Cosmo, check what the wiki already knows:
/knowledge-lookup impermanence
/knowledge-lookup what does plato say about the good
/knowledge-lookup cosmology origin universe
This returns pre-built synthesis pages, key claims, and connections — so Cosmo's response can build on existing wiki knowledge rather than re-deriving it from raw sources.
speculative → medium → high → superseded (if contradicted)
| Status | Meaning | Promotion criteria |
|---|---|---|
speculative | Interesting synthesis, not yet confirmed | — |
medium | Supported by 2-3 sources, defensible | 3+ synthesizes entries |
high | Well-established, contradictions documented | 4+ synthesizes entries + documented contradictions |
superseded | Contradicted by new evidence | Add failure_reason note; create replacement page |
archived | No longer relevant to corpus | — |
To promote manually: edit the confidence field in frontmatter and append to knowledge/wiki/log.md:
2026-04-12 PROMOTED wiki/concepts/logos-and-tao.md (speculative → medium; added theaetetus reference)
If you want to add a wiki page without running a skill:
entities/, concepts/, or connections/{slug}.md (kebab-case, no domain prefix — the wiki has its own namespace)---
title: "Page Title"
role: wiki
domain: <primary domain or cross>
confidence: speculative|medium|high
status: active
synthesizes:
- sources/path-to-source.md
last_reviewed: YYYY-MM-DD
tags: [tag1, tag2]
---
knowledge/wiki/index.mdknowledge/wiki/log.mdWiki pages do NOT use the {domain}-{slug} convention from source files. The wiki is a different namespace:
entities/plato.md ✓
entities/philosophy-plato.md ✗ (don't prefix with domain)
concepts/impermanence.md ✓
concepts/buddhism-impermanence.md ✗ (it's cross-tradition)
connections/cosmology-comparison.md ✓
One exception: if two entities share a name, use {tradition}-{name}.md to disambiguate.
knowledge/commentary/.knowledge/reference/. Wiki pages synthesize across multiple sources.confidence: speculative is not a flaw — it's the system working as intended.