Section B• Last verified November 2026

Understanding Mandates

The core primitive of financial authority: authorized budgets, per-tx limits, and lifecycle states.

What is a Mandate?

A Mandate is a legally and cryptographically binding contract between the user and the Mandate execution engine. It establishes the immutable financial perimeter within which autonomous agents are permitted to operate.

No agent, task, or objective can spend even a single yoctoNEAR without being attached to an active, non-expired mandate that has sufficient available budget.

Mandate Policy Parameters

Authorized Budget (total_budget)

The absolute maximum amount of NEAR the mandate can authorize over its entire lifetime.

Per-Transaction Limit (per_tx_limit)

The ceiling for any single transaction proposal. Any request exceeding this limit is rejected immediately.

Approval Threshold (approval_threshold)

Transactions below this execute autonomously. Transactions above this threshold are escrowed pending human review.

Recipient Allowlist (allowed_recipients)

An explicit set of approved NEAR addresses. Transfers to any other recipient result in policy DENIAL.

Mathematical Accounting: Spent vs Reserved vs Available

Mandate tracks balance state using strict integer math in yoctoNEAR (1 NEAR = 1024 yoctoNEAR). Budget availability is governed by the invariant:

Available = Authorized - (Settled_Spent + Active_Reservations)
Practical Example:
A user authorizes a 5.0 NEAR mandate.
• An agent completes a task, settling 1.0 NEAR.
• Another agent dispatches a task, creating a reservation of 0.5 NEAR.
Authorized: 5.0 NEAR | Spent: 1.0 NEAR | Reserved: 0.5 NEAR | Available: 3.5 NEAR

Mandate Lifecycle States

StateDescriptionCan Spend?
activeNormal operating state; available budget can be allocatedYES
pausedTemporarily suspended by user; no new transactions permittedNO
budget_exhaustedAuthorized budget completely consumed or reservedNO
expiredMandate expiration date elapsed; terminal stateNO
revokedExplicitly killed by user; all pending approvals canceledNO

The Financial Authority Model

Diagram 4: Immutable Financial Authority Hierarchy
Strict Invariant
ROOT OF AUTHORITY
Human User (Treasury Owner)
Signs Mandate, defines yoctoNEAR caps, approves plans
Full Control
POLICY LEVEL
Mandate Bounds & Restrictions
Total budget, per-tx limit, recipient allowlist, human thresholds
Deterministic
OBJECTIVE LEVEL
Objective Scope & Plan Hash
Can only spend within the mandate portion allocated to its plan
Sub-Budget
EXECUTION BOUNDARY
ExecutionBoundaryService + OutLayer TEE
Enforces nonces, rejects replays, signs in Intel SGX
Hardware Isolated
PROPOSAL LEVEL ONLY
Autonomous Agent (AI Swarm)
Can propose actions; zero keys, zero ability to self-authorize or raise limits
Zero Key Custody