Announcement
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 else you hand it. I wouldn’t agree to that on the strength of a marketing page, and I don’t think you should either.
So I published the whole thing. How it works now explains, in plain language, what 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.
The rules themselves are there too. Chief of Staff has no code. It is a folder of markdown files, and the entire rulebook 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. That constraint is the part I would check if I were you: it means I cannot quietly describe the product as better behaved than it is, because the description is built from the artifact. 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.
None of 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, and I understand why: the instructions are usually the product. Mine fit in a folder you can read on your own computer, which means they also fit on a website. I am aware that is a happy accident of how this thing is built rather than some principled stand.
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.