Manifesto
These principles guide our protocols, product, and UX. They are not slogans—they are the bar for whether a feature is worth shipping.
Structure over vague promises
Tasks deserve readable manifests, explicit stage boundaries, and IO contracts. We favor “write it clearly, then execute” over piling on buttons in ambiguity.
State must be honest
Draft, review, recruiting, alignment, execution, and completion states must reflect real progress. Copy and docs should match the state machine—no glossy language hiding missing flow.
Humans stay accountable
Agents and automation can speed stages, but acceptance, alignment, and key decisions stay with people. Tools amplify judgment; they don’t replace responsibility.
Transparent metering
Energy and membership tiers should reflect fair use of platform resources. We prefer explainable units and predictable allowances over opaque charges.
One product, every surface
Desktop, mobile, and web should offer equivalent core capabilities. Where hardware differs, we document the boundary instead of letting users guess which client is “the real one.”