For the complete documentation index, see llms.txt. This page is also available as Markdown.

Rules & Permissions

ASPAN Account is designed around owner-defined spending, investment, and liquidity rules. These permissions are separate: allowing an agent to pay a provider does not authorize it to invest the account balance.

Status: this page describes the intended control model. The current prototype's approvals are simulated; production enforcement remains to be implemented and reviewed.

Spending rules

An owner should be able to authorize named agents, payment assets, recipients, per-payment limits, total budgets, and an expiry time. Policies should also define which actions need fresh approval, such as adding a recipient or exceeding a routine threshold.

Committed payments must count against the relevant budget. Splitting a payment across transactions or agents must not bypass an account-level limit.

Investment rules

An investment mandate should specify permitted strategies and protocols, maximum exposure, any restrictions on leverage or cross-chain activity, and the actions the agent may execute without further approval.

Native ASPAN DeFi requires the same explicit admission as an external strategy. A strategy's displayed yield or ownership by ASPAN does not override the mandate.

Liquidity rules

Owners should specify a minimum liquid reserve, known payment dates, and the latest acceptable withdrawal timing. The account must consider both immediate spending and commitments that have already been approved.

The shortfall policy should explain whether to defer an action, seek owner input, or take a previously authorized alternative. An AI estimate cannot guarantee that funds will arrive by a deadline.

Independent enforcement

The AI manager may propose decisions and execute within an approved mandate. Deterministic checks must validate the agent, action, asset, destination, amount, current exposure, and permission expiry before execution. Enlarging the mandate requires owner authorization.

Production releases must state where each rule is enforced, what signing and custody dependencies exist, and how policy updates, failures, and recovery are handled. These details are not established by the current demo.

Pause, revoke, and review

The owner should be able to pause new delegated activity and revoke authorization. Previously settled payments remain final according to their route, and existing positions retain their withdrawal terms.

The activity record should link an action to the policy version and approval that permitted it. It should distinguish proposed, approved, submitted, confirmed, failed, and cancelled actions so the owner can see what actually happened.

See ASPAN Account for the balance model and Smart Contract Security for audit scope.

Zuletzt aktualisiert