Reference

Error codes sit outside the MCP range.

The reserved JSON-RPC band from -32700 through -32000, and Reverta codes from -31801 through -31812 beside it.
Application codes sit outside the reserved band so a gateway can tell them apart.

JSON-RPC parse failures are -32700. A request that is not a 2.0 object is -32600. An unknown method is -32601. Missing MCP _meta is -32602. Application codes are outside -32768 through -32000, so they do not collide with MCP’s -32000 to -32099 band.

CodeNameWhen you see it
−31801AtpInvalidTransactionIllegal state edge, bad transaction id, empty plan, live replay requested, a cycle sealed as rollback.
−31802AtpPolicyDeniedA blast-radius rule denied the diff.
−31803AtpUnknownOutcomeThe effect cannot be confirmed, or abort was asked to guess.
−31804AtpCompensationFailedThe inverse failed and retries are exhausted. The hold waits for RETRY.
−31805AtpIrreversibleBlockedA live irreversible step cannot be undone. It is orphaned and the transaction waits.
−31806AtpReplayDivergenceA recorded transition is not a legal edge.
−31807AtpIdempotencyConflictThe same txId arrived with a different plan hash.
−31808AtpApprovalRequiredThe transaction is parked for a person.
−31809AtpManifestRejectedSignature, tool definition, or rule failed closed.
−31810AtpArgumentInvalidArguments failed the schema profile. The idempotency key had not been injected yet.
−31811AtpToolUnregisteredThe signed manifest has no such tool.
−31812AtpLedgerTamperedHash, previous link, or anchor check failed.
A finished rollback is not one of these codes. The JSON-RPC result succeeds and state is ROLLED_BACK. Argument validation covers type, enum, string length, numeric bounds, array bounds, items, required, and additionalProperties. It is a profile of JSON Schema 2020-12, not a complete validator.