Blog
Read everything your chief of staff was told
Chief of Staff asks for a strange kind of trust. You point it at a folder, and from then on it remembers your commitments, your projects, your people, and whatever you hand it. Before anyone agrees to that, they deserve a better answer than "trust us."
So we published the whole thing. How it works now explains, in plain language, what actually happens when you use it: what it writes down on its own, what it does with documents you share, how it treats sensitive information, and the one situation where it refuses to write anything at all. Every claim links to the rule behind it.
And the rules themselves are there too. Chief of Staff has no code; it is a folder of markdown files, and its entire rulebook, all of it, is rendered on the site exactly as it ships. The pages are generated from the same zip the download button serves, so they cannot say anything your copy does not say. When a release changes a rule, the pages change in the same moment, and a version stamp on every page tells you which release you are reading.
Nothing about this was hard to build. It was just unusual to want: most products describe their behavior in marketing copy and keep the real instructions private. Ours fit in a folder you can read on your own computer, which means they also fit on a website.
Start with the overview, or go straight to the capture rules, the file that decides what gets remembered. If you would rather hold the real thing, install it: it is the same text.