Project knowledge in claude.ai shrank from seven syncing files to one thin pointer at disk — every session now opens with a recon ritual instead of a paste-sync.
Three commits this morning. 217bddd updated BLOG_RULES.md and JOURNAL_RULES.md to spec version 4.0 — sky-blue inline style on ✍️ blog cross-references locked, execution workflow rewritten to the inline courier pattern, MEMORY.md pointer added so counter values stop drifting between rules and live state. d772ad3 replaced hardcoded counter values and blog post lists in OPERATING_INSTRUCTIONS.md and MEMORY.md with pointers to a single source of truth — the counter lives in MEMORY.md, the rules files reference it, no copy gets stale. af8f6be ported Sat Singh's entity profile and the Brand Design System from the retired CANONICAL_MANUAL.md into MEMORY.md.
Project knowledge in claude.ai went from seven syncing files to one thin CLAUDE.md pointer at disk. Rules, memory, operating instructions, voice, and brand identity all live in ~/sunshine-fm now. Claude Project sessions read them by asking Claude Code to paste live state back into chat at the start of each session. No more two-copy drift between project knowledge and disk.
The pattern proved out the same day. This entry's session opened with three recon couriers before any draft hit the page. The first caught an unstaged April 26 PROJECT_LOG.md edit — a one-line todo close-out about JOURNAL_BUILD_SPEC.md → JOURNAL_RULES.md naming — that would have been overwritten without a fresh read. The second confirmed the Mirage homepage card didn't auto-remove on May 1 as planned: id="mirage-card" is still live in index.html, surfaced as a separate bug with the open item left in place in PROJECT_LOG.md. Neither finding was knowable from session memory alone.
Disk-canonical isn't SunshineFM-specific. AICV, the AI Lobbying Tracker, future projects all inherit the same pattern: rules and memory on disk, project knowledge as thin pointer, recon before prescription.