Glossary
Canonical Pakt terms used throughout the documentation and MCP protocol.
These terms have precise meanings in the Pakt protocol. Use them consistently when reporting a result to an owner or integrating an MCP client.
Authorization Is Not Settlement
Authorization, submission, and settlement are three different events. A Pakt receipt establishes the first one only.
Pakt : A typed, canonical SSZ artifact containing the constraints evaluated before authority may be released.
Pakt root
: The SSZ hash_tree_root derived from canonical Pakt bytes. It identifies the artifact, not account ownership by itself.
Approved agent : A delegated agent the owner has authorized for the account. Approval permits proposals; it does not bypass the active Pakt or proof gate.
Drafting agent : An optional agent that helps generate a candidate Pakt. It may be different from the approved action agent and receives no lifecycle authority.
Dual readback : The complete ALLOWED and NOT ALLOWED rendering of a compiled Pakt, including each term's trust basis.
Authenticated state : Decision inputs whose provenance is verified, such as balances, positions, prices, fees, and venue evidence.
Activation : The owner's passkey-backed approval that binds one exact Pakt root to an account and deployment environment.
Authorization : A proof-backed decision about one exact prepared request. Authorization may release a wallet signature but does not submit the request.
Approval stamp : A signature from the secure approval boundary over one exact wallet-provider request. The wallet provider requires it before signing, but venues do not accept it as a transaction signature.
Receipt credential signature : Separate evidence that the secure boundary authorized the exact artifact recorded by an allowed receipt. The browser checks it against a pinned public key.
Wallet signature : The venue-valid signature produced by the wallet provider after authorization. This is the signature returned to the approved agent for unchanged submission.
Refusal : A proved policy result that releases no approval stamp or wallet signature. It is a successful safety outcome, not an infrastructure error.
Receipt : The durable record of a proof-backed allow or refusal, re-verifiable in the browser against pinned trust anchors.
Submission : Sending a signed request to Hyperliquid or Ethereum. The approved agent's existing venue client performs this step unchanged.
Settlement : The venue's final external outcome. It is not established by Pakt authorization alone.