> ## Documentation Index
> Fetch the complete documentation index at: https://please.xyz/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Policy and approval

> How bounded policy authority differs from independent human approval.

please is designed around explicit authority. Understanding a request, generating a plan, and simulating it are separate from authorizing a payment or transaction.

<Warning>
  The current public service is read-only. It has no approval, signing, submission, broadcast, or execution tool.
</Warning>

## The authority boundary

In a transaction-capable version of please, a request may proceed only under one of two forms of authority:

* an explicit, pre-authorized capability with a bounded budget, scope, route, and expiry; or
* independent human approval bound to the exact request and plan.

Material, unfamiliar, above-threshold, or changed actions must ask. A prompt, assistant response, plan, quote, simulation, notification, or previous approval never grants authority by itself.

If a material parameter changes or the plan expires, the previous policy decision and approval no longer apply.

## Review checklist

Before approving an exception or material action, verify:

* **Agent and purpose:** Which agent is asking, and why?
* **Funding source and policy:** Which funding source, policy version, and budget apply?
* **Action:** Is this the operation you intended—transfer, swap, bridge, supply, withdraw, deposit, or another action?
* **Asset and amount:** Are the token, decimals, and amount correct?
* **Network:** Are the source and destination networks correct?
* **Recipient or beneficiary:** Is the complete address correct? Do not rely only on the first and last characters.
* **Protocol and contracts:** Do you recognize the protocol and the contracts or permissions involved?
* **Minimum received or slippage:** Is the worst acceptable outcome clear?
* **Fees:** Review network costs, protocol fees, bridge fees, and any service fees separately.
* **Permissions:** Avoid unlimited approvals unless you understand and intentionally accept the exposure.
* **Warnings and expiry:** Resolve warnings and confirm that the quote or simulation is still current.

## If something changes

Stop and request a fresh plan when:

* the asset, amount, network, recipient, protocol, or route changes;
* the quote or simulation expires;
* the displayed fees or minimum received move outside your limit;
* the wallet shows calldata, permissions, or contracts that the review screen did not explain; or
* the interface reports stale data, configuration requirements, or a failed simulation.

<Tip>
  When uncertain, reject the transaction. A legitimate action can be reconstructed and reviewed again.
</Tip>

## After authority is used

Authority must be single-use or explicitly scoped for a bounded reusable period. Every use should update the budget and audit record atomically. Public blockchain transactions may be irreversible; please generally cannot cancel, recover, or modify a transaction after submission through a wallet, rail, or third-party service.