What you'd have
The reasons, not only the code
A code history tells you what changed. This tells you why, which is usually the first thing lost when a company changes hands.
A structured record of intent
Product intents written as testable statements ("when this happens, the person experiences that") and company strategy decisions, each with an ID, status and history of who confirmed it.
What it gives you
A machine-readable map of what the product is meant to do, instead of reverse-engineering it from code.
What makes this version different
- Built for agents to query before they reopen a decision that was already made.
- Product intents
- 3,871
- Strategy intents
- 707
- Since
- Feb 2026
Measured 26 September 2026
Why each piece of work mattered
A written knowledge base of decisions, experiments and proposals, including a ledger that records, in plain language, why specific work was worth doing.
What it gives you
A shorter ramp-up for anyone new, human or agent.
What makes this version different
- Written as the work happened, not reconstructed afterwards.
- Documents
- 13,244
- Commits
- 618
- Session summaries
- 2,931
Measured 26 September 2026
Knowledge bases built from the founder’s judgment
Separate knowledge bases for different kinds of decision (product intent, steering agents, coaching principles, what has already been tried) that agents consult before asking the founder.
What it gives you
Agents can check an approach against the founder’s past judgment before taking up the founder’s time.
What makes this version different
- Built from years of the founder’s own conversations and decisions, which can’t be recreated without that history.
- Knowledge bases
- 9
Measured 26 September 2026