## The Decision Index
Scanning a thousand entries every session would be slow and expensive. So we maintain an index at the top of the journal — last seven days, high-impact decisions only, in a si...
## The Archive Cycle
Journals grow. Large journals degrade performance. So the system archives on a three-day cycle. Entries older than 72 hours move to an archive file. The summary dashboard stays in the active journal. The decision index gets rebuilt from recent entries.
The active journal stays lean — usually under 2,000 tokens. History is preserved in archive files but never loaded unless someone explicitly needs it. This keeps prompt costs stable regardless of how long the system has been running.
## Cross-Franchise Memory
Each franchise maintains its own journal. The system journal captures cross-cutting decisions. Franchise journals capture domain-specific ones.
Franchises don't share memory directly. A tinker role reads all journals periodically and extracts patterns that cross boundaries. If the outreach franchise discovers something relevant to the content franchise, the tinker routes it through the bulletin board. No direct coupling between franchise memory systems.
[3/4]
Journals grow. Large journals degrade performance. So the system archives on a three-day cycle. Entries older than 72 hours move to an archive file. The summary dashboard stays in the active journal. The decision index gets rebuilt from recent entries.
The active journal stays lean — usually under 2,000 tokens. History is preserved in archive files but never loaded unless someone explicitly needs it. This keeps prompt costs stable regardless of how long the system has been running.
## Cross-Franchise Memory
Each franchise maintains its own journal. The system journal captures cross-cutting decisions. Franchise journals capture domain-specific ones.
Franchises don't share memory directly. A tinker role reads all journals periodically and extracts patterns that cross boundaries. If the outreach franchise discovers something relevant to the content franchise, the tinker routes it through the bulletin board. No direct coupling between franchise memory systems.
[3/4]
1