41. Toll

Decision

Toll is an optional economics Domain with two separated planes: a Counting House for quote handling and accounting, and an Irreversible Gate for one independently verified settlement effect. It is neither a mandatory wallet, global auto-payment interceptor, nor Agent authority.

HTTP 402, an invoice, or any provider quote is an untrusted proposal. It may describe terms; it cannot authorize signing, settlement, retry, identity, access, or a larger budget. x402, L402, Lightning invoices, Wallet Connect, Nostr Zaps, and future rails are distinct adapters, not aliases.

Remote casting and teaching a missing Spell are distinct purchased resources. They cannot share a quote or idempotency identity merely because one peer offers both. Payment satisfies neither peer authentication, task admission, teaching quarantine, publication, activation, nor authority.

Local credits first, rails later

The first practical topology is deliberately issuer-local. An operator may grant or sell MANA service credits, or charge an exact request through one conventional payment provider. MANA is an issuer-scoped entry in that issuer's durable Counting House ledger, not cryptocurrency, cash, a bearer asset, a global currency, a governance vote, or a claim on another issuer. An amount without its issuer is invalid. The initial profile is account-bound: unlike issuers' balances are not fungible, and no cash redemption, peer transfer, or cross-issuer conversion is implied. Changing any of those properties requires a separately admitted economic and legal contract, not a configuration toggle.

Tithe meters model-token usage, generated media, concurrency, queue weight, hardware time, and other resource consumption. The Counting House separately owns MANA balances, reservations, debits, credits, refunds, and reconciliation. Only an issuer-authorized accounting boundary—not an Agent, model, or ordinary tool—may issue, expire, or correct MANA. Every entry retains its authority and grant reason or exact external funding identity; corrections append compensating entries rather than rewriting history, while reservations prevent double-spend and negative available balance.

Only an independently verified settlement admitted under issuer policy may fund one exact local balance or settle one exact pay-as-you-go request. Funding atomically and idempotently binds the external-effect identity; a client claim, webhook alone, pending authorization, or ambiguous settlement cannot create reusable credit. A sale retains purchase asset, amount, rate, terms, expiry, and original funding identity. A required refund returns through its governed original route where possible; it is not a promise that MANA can freely cash out.

Toll remains rail-neutral but evidence-specific. Every quote, authorization, and receipt names the exact issuer, rail, asset, integer units, merchant, and network or external-effect identity where applicable. A conventional processor adapter and an x402 adapter are sibling rails: x402 is not a currency and does not require a project-native asset. Adapters translate exact evidence; they do not erase provenance or make unlike balances fungible.

The commitment before the signature

The Counting House may parse a versioned challenge, normalize integer monetary units, compare candidate costs, reserve a budget, and reconcile receipts. It holds no spend key. An authorization binds authenticated Principal and budget owner, merchant/service, method and canonical destination, request digest and purchased resource, asset/network, maximum amount including fees, expiry, redirect policy, and idempotency key.

The execution-road policy considers quotes only among roads that satisfy capability, privacy, policy, and resource feasibility. Toll owns judgment of the economic terms and reservation of their exposure; Dispatcher binds an already eligible capability. Policy rejects the quote, applies one matching bounded low-risk standing authority, or parks the Run for live Magus consent over the exact terms. Novel or significant spend requires HitL. Consent means this exact maximum, never whatever a later challenge asks.

Accounting reserves worst-case exposure before signing. The isolated Irreversible Gate revalidates the pinned authorization and live reservation, enforces per-effect and rolling caps, atomically consumes the reservation, signs once, submits once, and records a stable external-effect identity. Unknown version, scheme, network, destination, amount, fee bound, changed quote, or expired authority fails closed. No model or ordinary tool receives a wallet or general signing surface.

Two settlement rites

Local MANA consumes no wallet signature or external proof-bearing replay:

eligible request → quote → authorize and reserve local balance
→ execute → debit on the declared delivery condition / release / refund → reconcile

An external rail separately crosses the Irreversible Gate:

destination-pinned request → quote → validate and reserve → reject / standing authority / live consent
→ revalidate → sign and submit once → one proof-bearing replay → reconcile settlement and delivery

After independently authorized settlement, the original connector can make at most one proof-bearing replay to the same pinned destination; that replay cannot begin another payment. Payment and delivery are not atomic. A settled charge can yield no useful result, and a successful response does not make content true. Refund, credit, dispute, expiry, paid-but-undelivered, and ambiguous outcomes are durable, visible states. An unknown settlement is investigated and reconciled—never answered with a second signature.

Budgets, effects, and restore

Tithe records currency-neutral model-token usage, generated media, concurrency, queue weight, and hardware time against a stable Principal or service grant even with every payment adapter disabled. A paid quota grant cannot mint or widen a Sigil, expose memory or tools, bypass consent, or displace protected local work. Currency-free Legion work still needs quotas, reservation, attribution, and evidence.

Quote, reservation, authorization, submission, settlement, delivery, refund, expiry, and ambiguity form a durable idempotent receipt chain. Keys, signatures, bearer proofs, preimages, invoices, and wallet credentials never enter prompts, ordinary projected configuration, logs, traces, or artifacts. Oculus can observe redacted transitions and reconciliation lag; a trace is not the financial ledger. Restore cannot rewind money: spending stays closed until external rail state reconciles.

Extensions may add bounded quote parsers, rails, signers, and paid Portal connectors, but not arbitrary global middleware, unrestricted keys, rival ledger truth, or a bypass of host authorization. Every external adapter pins one exact provider or protocol profile and conformance corpus. The first delivered adapter need not be x402.

Deferred shared and sovereign settlement

x402, stablecoin settlement, cross-provider clearing, a native token, a validator network, and a sovereign L1 remain future candidates, not accepted dependencies or delivery promises. A native chain is not admitted merely by calling it another rail adapter. It requires later amendments to this and every affected Covenant after independent operators demonstrate a need that issuer-local credits and existing payment rails cannot satisfy, together with explicit consensus, custody, issuance, validator, upgrade, economic-security, privacy, recovery, abuse, and legal gates.

No MANA balance, contribution, usage receipt, test token, or participation creates any right to a future token allocation, conversion, airdrop, cash redemption, or governance claim. Economic balance, token ownership, and validator status cannot grant canonical-source selection or Evolution promotion authority; Packaging and Evolution retain those separately governed human-seat decisions.

Delivery and consequences

This Covenant is Designed, not payment capability. No Toll package, quote/budget ledger, reservation, authorization, signer, settlement path, safe 402 response, reconciliation, or budget enforcement ships. State of Work owns that public boundary; Toll owns operated doctrine.

Delivery proceeds through these steps:

1. Establish immutable financial identities and integer money types.
2. Verify quote, budget, reservation, and receipt accounting without money movement, then prove manually granted MANA through idempotent reservation, debit, release, and refund.
3. Build and verify the isolated, capped Irreversible Gate.
4. Admit one allowlisted conventional payment adapter in its provider's sandbox, with evidence for crash, replay, refund, chargeback, and ambiguous settlement.
5. Only then admit production pay-as-you-go, seller routes, x402, or other optional rails.

Toll makes economic consequence attributable, bounded, interruptible, and reconcilable, while requiring durable accounting, key custody, explicit parked/ambiguous caller states, and later marketplace, refund, dispute, legal, and abuse domains.