Knowledge base
I want my AI officers to work as an extension of me, so each one gets specialized knowledge for its field. Its part of this library comes from sources I picked for that field, distilled into small files it can load and cite. Built in May 2026 and added to since.
How it's built
- It started as 1,297 saved files. Only the highest-value ones made it in: ideas and methods that aren't in a model's general knowledge. Those were distilled into small files, one idea each, grouped by topic.
- Ideas point back to the sources they came from, and a script checks those links: as of October 2026, 1,165 of them, none broken.
- A script builds each officer an index of everything it knows, straight from the files. Nobody edits it by hand.
- Each file holds one idea and has to make sense on its own, in 300 to 700 words and never more than 900, so an officer reads only what the task needs. A cheat sheet that only works whole can run longer.
- A line at the top of each file names the job it's for, and an officer finds it by the task in front of it.
- As of October 2026: 420 files across 16 topics, including 42 one-page frameworks, about 170,000 words in all.
- Distilled with Claude in Cowork, then checked by script.
Officers and how they use it
The officers who read it each own one field: revenue, finance, operations, AI, or chief of staff. They have their own page:
- Each idea lives in one place. If another officer needs it, its file points there instead of keeping a copy. Change the idea once, and the change reaches them all.
- For its everyday jobs, an officer already knows which files to load, and it checks its index for the rest. When nothing fits, it writes down what it was looking for, and that log tells me what to add next.
- Every officer works by the same rule: grab a sword, not a catapult.
- Every file is marked public, idea-only or locked, and nothing from it is published until its mark allows it.