← ClaudeAtlas

wiki-tierlisted

Inspect and manage the memory-tier system: view the active/archived/frozen distribution, preview a threshold change before committing, update SCHEMA.md thresholds, and pin manual tier overrides on specific pages.
litianyi-007/kata · ★ 0 · AI & Automation · score 73
Install: claude install-skill litianyi-007/kata
# wiki-tier Manage the wiki's three-tier memory system. Raw content and wiki pages are bucketed into `active | archived | frozen` by age, and most query skills default to `--tier=active`. This skill is how you inspect that distribution, adjust the thresholds, and pin individual pages that shouldn't follow the automatic rule. > **Why tiers:** old sources don't just become irrelevant — they become > _noise_. Filtering them out of the default query surface is how the wiki > keeps compounding without diluting. Frozen content is not deleted; it's > just parked. ## Model - Tiers are **computed on-the-fly** from a date field per `SCHEMA.md` `memory_tiers:` block. They are **not** stored as frontmatter — that would silently drift whenever a threshold changes. The filesystem is the only source of truth; the tiers are always in sync with the current config. - **Driving field:** per SCHEMA.md, typically `published_at` with a fallback to `ingested_at` when `published_at` is missing. - **Wiki-page inheritance:** a wiki page's tier is **the most recent tier across its cited sources** — any one active source pulls the whole page into active. This keeps synthesis pages on the hot path as long as fresh sources back them. - **Manual override:** a page may set `tier_override: frozen` (or `active`, `archived`) in its frontmatter to bypass the automatic rule. Lint and digest respect pins. ## When to use - "Show me the tier distribution" - "Push the active window out to 2 y