Kinds of fix
| Kind | Who carries it out |
|---|---|
| Undo the update | Pagerless, through the host's API (rollback, older version or revision) |
| Restart | Pagerless, through the host's API |
| Add capacity | Pagerless, through the host's API (instances, replicas, compute) |
| Pause | Guided step, or your coding agent |
| Open a pull request | Your coding agent over MCP |
| Email customers | Guided step; always needs your approval |
| Data change | Never. Not even if you ask. |
Rules: alone, ask, never
Each kind is set to alone (runs without asking), ask (waits for a person) or never. Presets: careful, balanced and hands-off. Irreversible kinds can be at most ask. Data changes are always never.
Approvals
Approving an undo, a customer email or a data-related step needs a passkey with user verification: Face ID, Touch ID or a security key. Other approvals are a signed-in tap. An approval expires after 10 minutes.
After a fix
Pagerless watches the error rate for 5 minutes, up to 4 windows. If the errors stop, the problem closes. If they don't, the fix is left in place (never auto-reverted) and a person is woken.