Guarantees
What holds for every Startup at every autonomy level, under every operating model, enforced by the platform rather than by agent instructions.
These guarantees hold for every Startup at every autonomy level and under every operating model. No Setting, Mandate or agent version turns one off.
What every Startup gets
| Guarantee | Enforced by |
|---|---|
| Every Action records who acted, for whom, and under which Mandate or Permission. | Action accountability, Authenticated Actions |
| Authority is checked by the platform, the same way on every Interface. | Authenticated Actions |
| An Action over a Limit waits for an Approval. Nothing else needs a yes. | The Limit itself |
| A one-way Action passes review, then waits its delay window. | One-way Action windows |
| Nothing is deleted. A revert is a new Change. | Append-only records, Revert by query |
| No effect happens twice. An unknown result is settled before any retry. | Action completion |
| A new agent version passes its eval suite before it reaches a customer. | Agent definition evals |
| An agent never edits the Metrics, Evaluators or guardrails that grade it. | Agent definition evals |
| An agent acting as itself says it is an agent. | AI disclosure |
| Everything an agent sends in a person's name appears in that person's stream. | Delegated sending |
| Pause, cancel, revoke and brake take effect at once. | Watchers and brakes |
| Customers, revenue and Metrics come from the record. A Startup cannot show an invented customer, number or badge. | Outcome confirmation |
Why they hold
Each guarantee runs as platform code outside the agent. An agent cannot talk its way past one, and a prompt that tries to has no effect. Every Startup inherits them, and with them the controls its compliance rests on.
No Experiment randomizes the legal floor, consent, AI disclosure or refund rights. Those stay fixed while everything around them is tested.
Guarantees and outcomes
Guarantees bound how a Startup acts; they do not promise results. A customer who needs a promised result buys under an Outcome Contract: done, then accepted, then billed, with a remedy on a miss.
In practice
The founder of a b2b billing API lets an agent send up to 20 introduction emails a day from her own mailbox. The Mandate limits topics to integration partners. Each send shows in her stream, marked by the agent and for her.
At 9:02 she revokes the Mandate. The send queued for 9:03 is refused, and the record shows why.