Pakt Lifecycle
How a pure draft becomes owner-approved authority and how that authority is disabled.
An agent may generate a candidate Pakt, but a draft changes no authority. Only the owner can activate or permanently disable its exact root with the account's enrolled, backed-up passkey.
Drafting Does Not Grant Authority
Drafting changes nothing. A Pakt becomes active only after the owner approves its exact root in the browser; disabling that account-and-root pair is permanent.
Draft
draft_pakt returns DRAFT_NO_SIDE_EFFECTS: source, canonical SSZ, root,
a human-readable ALLOWED / NOT ALLOWED summary, and sample actions with
their allow/refuse results. It stores and activates nothing.
Prepare Owner Review
prepare_pakt_activation stages the exact canonical Pakt under a random,
five-minute browser challenge bound to the authenticated account,
environment, and root. The MCP agent receives no key or signature material.
Activate in the Dashboard
The owner reviews the exact ALLOWED / NOT ALLOWED summary and approves with the already-enrolled backed-up passkey. Only then does the root become active authority for that account.
Disable Terminally
prepare_pakt_disable stages a distinct disable challenge. The owner
approves it in the dashboard with the same passkey. A disabled account/root
binding cannot reactivate.
The product's Get started flow owns passkey enrollment and wallet connection. The technical documentation starts from the resulting authority and does not reproduce that ceremony.