How Continuity Bridge loads lightweight catalogs at wake, then fetches specific content only when needed—the key to 94% token reduction.
The catalog system is why v0.3.0 uses 94% fewer tokens at wake than v0.1.0. Instead of loading all history, all decisions, all memory—the instance loads three lightweight indexes that tell it where to find things. When a user asks "what did we decide about X?", the instance checks the session_index catalog, finds the relevant session date, and loads only that specific file. The rest stays on disk until needed.