Decision log
What was decided, when, by whom, and the reason. The note that settles "wait, why did we do it this way" in ten seconds, a year later.
Early on, the founder IS the knowledge base: every decision, every investor conversation, every reason-why lives in one skull and a thousand tabs. It works until the first hire, the first handoff, or the first month you are stretched too thin to remember why March-you decided anything.
Write decisions where your AI can read them and your future hires will inherit them. A note per investor, a note per big call, a running product log. Your assistant drafts into the vault as a side effect of working, so the memory builds itself while you build the company.
When hire number one arrives, onboarding is a folder, not a week of your calendar.
What was decided, when, by whom, and the reason. The note that settles "wait, why did we do it this way" in ten seconds, a year later.
A note per relationship: what they asked last time, what you promised, what to open with next time. Your AI preps you from it before every call.
The running story of what shipped and why. Doubles as the changelog, the onboarding doc, and the honest history when you write the retrospective.
When you delegate a lane, you share a folder, set one access rule, and the context moves WITH the responsibility.
Solo today, five people next year: the vault does not care, and nothing needs migrating when you grow.
Keep reading: Memava for product teams mixing AI tools · Memava for research teams · How to give AI agents a real, shared memory