Statuses and Errors
The stable state vocabulary returned by Pakt MCP tools.
Every status states what Pakt completed and which effects have occurred. Read the complete status name; similar-looking states have different authority.
Read the Entire Status
Staged is not approved, signed is not submitted, and submitted is not settled. A proved refusal is a normal result; an infrastructure fault is not a refusal.
Authoring and Owner Approval
| Status | Meaning | Authority changed? |
|---|---|---|
DRAFT_NO_SIDE_EFFECTS | Canonical draft and review artifacts were produced | no |
BROWSER_PASSKEY_APPROVAL_REQUIRED | Activation is staged for owner review in the dashboard | no |
BROWSER_PASSKEY_DISABLE_REQUIRED | Terminal disable is staged for owner review in the dashboard | no |
ACCOUNT_AUTHORIZATION_LIFECYCLE | Verified account Pakt summaries were read | no |
Browser completion activates or disables the exact root. Confirm the resulting
lifecycle_status with list_pakts; do not treat a staged challenge as the
completed lifecycle change.
Authorization Jobs
| Status | Proof | Wallet signature | Submitted |
|---|---|---|---|
AUTHORIZATION_PENDING | not yet complete | no | no |
SIGNED_NOT_SUBMITTED | yes | yes | no |
REFUSED_NOT_SIGNED | yes | no | no |
Refusal Versus Fault
A refusal is a normal, proved policy result returned as a successful MCP tool result. A fault is a validation, dependency, persistence, or infrastructure failure returned as an MCP error. Do not report a fault as though the Pakt evaluated and refused the action.
If a fault reports that a signing credential was already released, Pakt may already have authorized a wallet signature. Do not restart the operation. Reconcile the receipt and external venue state first.