Company Context
Your business, readable by AI Your map and your company's know-how, set up so every agent you use reads them.
AI only works when it sees the business. We set up what it sees.
One source, many agents
Claude at a desk, the company agent in chat, a scheduled run. They all read the same map and give the same answer.
Loaded in order
House rules first. Then the map, to place the task in your company. Then only the pages the task touches.
Pointers, not copies
Context stays at the source. When the map changes, every agent sees the change on its next read.
Plus a knowledge base your agents can act on Your SOPs, playbooks, and the knowledge in people's heads, captured once and linked to your map.
Capture We write it with you: the knowledge that lives in people's heads today, organized against your operations map.
Maintain Agents draft updates as the work changes. Your people review. Nothing becomes truth without sign-off.
Compound Every page links to the workflows, systems, and apps it touches. Knowledge builds on itself instead of scattering.
Questions & answers
Where does the context come from?
Two places. Your operations map says how the company is put together, and your knowledge base says how the work is done. We set up both, and agents read both.
Do we have to write the knowledge base ourselves?
No. We capture it with you in working sessions, and agents do the tedious part afterward: drafting updates, fixing links, and flagging contradictions.
What happens when the business changes?
You change the source, and every agent reads the new version on its next task. There is no second copy to drift out of date.
What can agents actually see?
What you allow. Access follows your rules, reads are logged, and sensitive areas stay closed unless you open them.
Where does it live?
On your accounts, in plain files your team can open anywhere. No proprietary format, no lock-in.