Draft and Review a Pakt

Drafting is the safe place to iterate. The drafting agent may be the same agent that later proposes actions, a different agent, or no agent at all. A draft has no authority until the owner approves it in the dashboard.

Ask the MCP Client

Give the client the outcome and boundaries you want, not a preselected trade:

Draft a Pakt for a Hyperliquid agent that may trade BTC and ETH perpetuals.
Cap leverage at 2x and each trade at $100. Assume the whole account is no more
than $500. Require cross margin, at least
1.3x maintenance-margin health, and a 30% liquid reserve. Do not activate it.
Explain each rule plainly and give me examples Pakt would refuse.

The agent should:

1. Call list_pakt_templates to inspect the available starting points.
2. Follow its authoring_intake: unless already stated, ask how much the user intends to allocate to this Pakt and what risk appetite they want.
3. Propose exact leverage, trade-size, collateral-outflow, and account-buffer limits. Explain the numbers and let the user revise them. Allocation is authoring context, not a required deposit or maximum-balance constraint.
4. Compile the closest preset to obtain its editable source.draft_json, then call draft_pakt with that customized JSON. An explicitly requested unchanged preset may be compiled directly, but its values remain examples rather than a personalized recommendation.
5. Return the complete review artifact without activating it.

Require the Safe Result

The response must report:

status:     DRAFT_NO_SIDE_EFFECTS
mutability: PURE_NO_SIDE_EFFECTS

Every effects value must be false. The response contains review data only: it changes no account, wallet, Pakt, proof, signature, or venue state.

Review What Is Actually Committed

Start with these fields:

• pakt.root
• pakt.review
• pakt.comprehension_quiz

pakt.review names each market and states the rule and refusal boundary in ordinary dollars, percentages, and time. Predict each sample action's result before reading Pakt's allow/refuse answer.

The response also includes source.draft_json, pakt.canonical_ssz, pakt.technical_details, and pakt.dual_readback. Those are for reproducing the artifact or performing an advanced configuration and trust audit; they do not need to be narrated in an ordinary demo.

If an allowed action surprises you, a refusal contradicts your intent, or a trust basis is unacceptable, ask for a new draft. Every change to a committed term creates a new root for review.

Continue With Owner Review

When the artifact matches the owner's intent, ask the agent to call prepare_pakt_activation with the exact pakt.canonical_ssz. The owner then reviews and approves the staged Pakt in the dashboard; the agent never handles the passkey.