Manifesto
These principles guide our protocols, product, and UX. They are not slogans—they are the bar for whether a feature is worth shipping; trustworthy matching and verifiable collaboration matter equally.
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
Points and membership tiers should reflect fair use of platform resources. We prefer explainable units and predictable allowances over opaque charges.
One product, on every device
Whether you use Pairag on a phone app, a desktop app, or in the browser, the **core flows**—matching, joining a task, and collaborating inside it—should feel like the same product. Only a few things may differ when a device or OS can’t support them, and we call those out clearly in the app; we try to avoid making you guess which client is “complete.”