wiki-memorylisted

# Wiki Memory The wiki is the plugin's long-term memory. Daily notes come and go; wikis compound. ## Your wikis Each wiki is a directory with its own `CLAUDE.md` defining its schema, and each is registered in `wiki-cycle`'s `references/wikis.yml`. Read that registry to learn which wikis exist, where they live, and what each one covers — this skill deliberately hardcodes no list, so the two skills can never disagree about what is registered. A wiki earns its place by having a subject narrow enough that a page clearly belongs or clearly does not. "Everything interesting" is not a wiki; it is a notes folder with extra steps. > **Never touch files outside a wiki's own folder.** Read across wikis freely, > write only inside the destination wiki. ## Staging → promotion flow 1. Transcript processor or discover agent drops new items into a wiki's `wiki/entities/_staging/` or `wiki/sources/_staging/`. 2. Nightly ingest (`/cos:wiki-ingest`) reviews staging, deduplicates, and promotes into the proper section. 3. Each promotion updates `wiki/index.md` and appends an entry to `wiki/log.md`. 4. Stale entries (>7 days in staging with no new signal) are auto-closed with a `status: deferred` note. ## Cross-wiki linking When an entity is found in multiple wikis: - Other wikis link to it via full-path wikilink: - The cross-wiki backlink index (`wiki/cross-wiki.md`) is rebuilt on nightly ingest. ## Lint rules (per-wiki, as declared in its CLAUDE.md) Each wiki's `CLAUDE.md`