The wiki is the repo.
There is no database copy of your knowledge. The knowledge base is your company's docs git repository, edited in the cabinet as a wiki. Every edit is a real commit. Agents read the same files you do, at the same commit.
Ideal customer: field-service teams of 10–200 seats with offline requirements. Buyer: operations lead. Trigger: a failed rollout of a general note app.
Read by: CEO, Marketing lead, Sales agent · last commit by founder · a91f2c0
A folder is a page
Create, rename and move folders from the cabinet. A move is one atomic commit that also rewrites the links pointing at it. Git stays in step; nothing dangles.
The wizard writes the first page
Your company setup is committed as wizard.md — with the cap table, third-party personal data and credentials redacted — so every agent knows the company from its first turn.
Agents read, founder writes
Agent teams and the CEO read the repo. The CEO can propose edits, held as a diff until you apply them. Your words are never overwritten silently.
Memory that outlives the model.
Session state is model-agnostic by design. Switch the CEO from one provider to another, or route a department to a local model, and nothing is forgotten. The same memory survives a change of ownership when a business is transferred.
memory_remember,memory_recall,memory_forget— available to the CEO and over MCP- Cross-session, per company, from the Free tier
- Knowledge compounds: every session makes the company smarter
memory_recall("launch date") → "Launch moved to Oct 20 (founder, Sep 12). Billing page is P1. Announcement owned by Marketing." memory_remember("SSO on billing is P1 for M3") ✓ stored · scope: company · ttl: none # CEO model switched glm-5.3 → claude-opus memory_recall("launch date") → identical. nothing lost.