Manifesto
10-6-2026 · 4 min
The deck that maintains itself
Founders shouldn't update three artifacts to ship one update. One brain, every surface follows.
productmanifesto
Notes from the shop floor — architecture, access model, the graph-as-CRM thesis, why provenance is load-bearing.
Founders shouldn't update three artifacts to ship one update. One brain, every surface follows.
One person, many relationships, many vessels. The cross-vessel signal a per-vessel tool literally cannot see.
Permissions aren't code. They're a row in `grant_templates`. Edit, and the resolver responds.