Company memory
Company memory is the durable store the CEO loads on every session. It holds owner-supplied facts (brand voice, ICP, current goals, tool inventory), specialist-supplied lessons (what shipped, what failed, why), and product-supplied playbook tuning (which prompts work for this owner). Without memory, every session would start from scratch.
In one breath
- Three layers: owner facts, episodic lessons, playbook tuning.
- Specialists access memory only through CEO-curated brief slices.
- Versioned and auditable — the owner sees every change.
What memory contains
Three layers. Owner facts: brand voice, ideal customer profile, current quarter goals, connections, autonomy preferences. Episodic lessons: each completed task records a one-line lesson — what worked and what to avoid next time. Playbook tuning: per-owner adjustments to playbook briefs based on accepted vs. rejected drafts.
How specialists access it
The CEO reads memory, picks the slices relevant to the current task, and includes them in the brief. Specialists do not have direct memory access — they get only the slice the CEO hands over. This keeps memory consistent and prevents specialists from guessing about facts they were not given.
Where it lives
Memory currently writes to per-tenant files under the tenant config directory. The Supabase migration moves it to a typed table with audit history; both representations stay versioned so the owner can see exactly what changed and when.