Procurement Wallet
Handles paid data requests, merchant verification, and route fingerprinting. Designed for machine commerce.
How it works
Agents propose.
Constitutions authorize.
A constitutional runtime sits between agent cognition and economic execution. Sovereign separates cognition from authority.
Core principle
The separation of cognition and authority.
An agent can reason, plan, and request. The wallet only acts after the runtime validates a typed intent against an active constitution.
This is not a permission gate bolted on top. The constitutional runtime is the evaluation path. There is no direct route from agent cognition to wallet execution.
Every wallet carries a compiled constitution: a set of rules that govern which merchants can be paid, how much can be spent, what risk is acceptable, and what evidence the agent must provide.
Agent ↓ EconomicIntent ↓ Intent Normalizer ↓ Constitutional Runtime ↓ Wallet Profile Budget Engine Merchant Trust Risk Policy Evidence Checks ↓ DecisionPacket ↓ Execution Adapter ↓ Audit · Journal · Provenance · Memory
01 — Intent
EconomicIntent replaces raw wallet access.
Instead of handing agents a signing key or a wallet adapter with open-ended methods, Sovereign exposes a single typed intent surface. Agents declare what they want to accomplish: which wallet, which merchant, which route, what data they need.
The intent is normalized, validated for schema completeness, and passed to the runtime evaluator. The agent never interacts directly with the execution layer.
EconomicIntent — SDK call
await client.proposeIntent({
walletId: "wallet_procurement_demo",
agentId: "akasha_agent",
kind: "mcp.paid_data_request",
merchantId: "merchant_akasha_market_data",
routeId: "route_eth_snapshot_v1",
taskId: "eth_market_cycle_001",
idempotencyKey: "eth_snapshot_001"
});02 — Wallets
Wallet profiles carry different authority.
Not all wallets are equal. Each profile type carries its own constitution, budget limits, permitted merchants, and risk tolerances.
Trading Wallet
Governs paper execution from risk-checked trade plans. Live trading denied by default unless explicitly escalated.
Treasury Wallet
Holds system-level authority for fund management. Restricted by the most conservative constitutional rules.
03 — Authorization
DecisionPackets scope approval.
When the runtime approves an intent, it issues a DecisionPacket. The packet is scoped to the specific action, carries a short expiry, includes a nonce, and is signed by the runtime.
The execution adapter verifies the packet before acting. An expired packet is rejected. A replayed nonce is rejected. The packet cannot be used for a different action than what was approved.
DecisionPacket fields
- → intentId (bound to original request)
- → walletId and agentId
- → actionKind (scoped, not generic)
- → expiresAt (short window)
- → nonce (replay protection)
- → signature (runtime-signed)
- → budgetReservationId
04 — Execution
Execution stays adapter-bound.
Adapters translate approved DecisionPackets into specific protocol actions. No adapter can act without a valid packet.
Mock x402
Simulates machine-readable payment protocol for demo flows.
Paper Broker
Executes paper trades without real money. Risk-gated by trade plan.
Base / CDP
Placeholder adapters for real on-chain execution. Not enabled.
05 — Memory
Records make actions legible.
Every executed action produces structured records that connect the agent decision, the wallet approval, the merchant route, and any downstream artifacts.
Audit Events
Append-only log of every runtime decision, approval, denial, and escalation.
Accounting Journal
Double-entry-style records for every settled action. Exportable as CSV.
Provenance Links
Artifact graph connecting data to the decision that funded it and the plan that used it.
Ready to run it?
The demo proves every step of the flow locally in under five minutes.