/**
 * Canonical memory-kind vocabulary — the single source of truth.
 *
 * The union type, the accepted-kind set in the frontmatter parser, the
 * hot/warm tier map below, `KIND_ORDER` in the reindex view, and the CLI
 * `--kind` help text all derive from this tuple. Adding a kind here is the
 * only edit required; TypeScript then forces `MEMORY_KIND_TIER` to cover it.
 *
 * unchanged. The 13 appended kinds were observed on disk with real values
 * that the index schema rejected (`peaks memory reindex` reported them as
 * `unrecognized kind value`). Accepting them moves those files into the
 * index; files with no kind field at all stay reported as unclassified.
 */
export declare const PROJECT_MEMORY_KINDS: readonly ["project", "rule", "decision", "reference", "feedback", "convention", "module", "lesson", "bug", "investigation", "technical-pattern", "project-rule", "design", "handoff", "session-handoff", "project-todo", "publish-closure", "project-closure", "slice-closure", "slice-pilot-findings", "sediment"];
export type ProjectMemoryKind = (typeof PROJECT_MEMORY_KINDS)[number];
/** Hot kinds keep their body in the always-available index; warm kinds are
 *  indexed with the same entry shape but read on demand. */
export type MemoryKindTier = 'hot' | 'warm';
/**
 * Hot/warm tier per kind. Insertion order IS the deterministic section order
 * used by the generated `MEMORY.md` (`KIND_ORDER` in `index/reindex.ts`),
 * so this object's key order is load-bearing — append new kinds at the end
 * of their tier block rather than reshuffling existing entries.
 *
 * The `Record<ProjectMemoryKind, MemoryKindTier>` annotation makes a missing
 * tier a compile error whenever `PROJECT_MEMORY_KINDS` grows.
 */
export declare const MEMORY_KIND_TIER: Record<ProjectMemoryKind, MemoryKindTier>;
export declare const HOT_MEMORY_KINDS: readonly ProjectMemoryKind[];
export declare const WARM_MEMORY_KINDS: readonly ProjectMemoryKind[];