| Budget | One funded ceiling - a Control ledger record, an escrow deposit, or a credit card authorization - fanned out into streams. The parent object of a session |
| Stream (allowance) | A capped, revocable, per-second child allowance of a budget, aimed at exactly one service node. Streams delegate recursively; a subtree can never outspend its parent's cap |
units | The metered quantity. Deliberately payload-neutral: tokens, words, bytes, calls, minutes - the protocol prices work, whatever the work is |
| serviceNode | A payee: the address work streams to. Also deliberately payload-neutral |
| Rate envelope | The per-second accrual bound on a stream. Allowance accrues at rate × elapsed; a tick that outruns it fails closed |
| Voucher | A monotonic EIP-712 record of cumulative billed work, signed by the stream's scoped session key. Billing truth is the last SIGNED voucher |
| Session key | The scoped signing key behind one stream's vouchers. Leak blast radius = that stream's remaining cap |
| Allowance credential | An offline-verifiable JWS proving a live, capped allowance aimed at a specific service node - the request-path material gateways verify in-process |
| Checkpoint | Submission of the last signed voucher to the settlement layer (an on-chain settle or a ledger entry; on the credit card rail a ledger settlement that a later capture covers) |
| Finality | The settlement state after which funds are the payee's. Reached when the holdback window closes (or per chain confirmations) |
| Refund | Money returned to the payer under objective terms a developer chose to offer and the user accepted before use; AI inference itself carries no refunds, and Dynamo never decides one. Unspent budget returning at close is not a refund |
| Holdback | The per-stream window during which settled funds stay reachable for rule-based refunds. On the verified runtime the default is CORE_HOLDBACK_DEFAULT_SECONDS (300 unless set) or, for a stream under catalogue terms, its longest term window plus 900 seconds; on contract version 2 it is also fixed on chain, at most 90 days |
| Verified runtime | The verified-value settlement layer (holdback dial, anomaly envelopes, objective terms, refunds, fee netting), turned on in a core with CORE_VERIFIED=1; off by default |
| Break-point | The attested instant from which degraded/failed units stop being payable. Refunds clip the settlement envelope from the break-point |
| Control Mode | The no-money funding mode: full enforcement machinery over a ledger backend. The recommended starting point for every integration |
| Escrow | The on-chain funding mode (usdc): the budget cap deposited in the vault contract, settled per voucher, released at close. Two contract versions run side by side; a budget stays on the version it opened on |
| Contract version 2 | The second escrow vault (BudgetVaultV2): relayed settlement, held value released in tranches, refunds on attested terms breaches, a grace window after the cut-off, user-owned budgets |
| Grace window | On contract version 2, the 7 days after a stream's cut-off during which vouchers signed at or before it can still settle |
| Relayer | A gas-only key that submits contract version 2 settles and releases for payees. It pays gas and moves no value; a relayer equal to a stream's payee is refused |
| Card authorization-backed budget | The credit card funding mode: one manual-capture authorization is the ceiling; captures follow vouchers; the remainder releases at close |
| Mandate | What a budget's root funder allows: categories, maximum delegation depth and, from owner-api 1.4.0, limits, payee lists, time windows and approval thresholds; later versions add a minimum payee identity level (minPayeeAssurance) and a minimum agent verification level (minAgentVerification). A child's mandate can only narrow its parent's; a budget opened without one gets the safe default |
| Own hops | Each delegation hop signed by its delegator's own key (a hop intent, sent as delegation) together with the payee's signed offer. Required by default in money modes (CORE_OWN_HOPS) |
| Payee offer | A payee's signature over the categories it accepts work in and the time it is valid, sent as payeeOffer when a stream opens to it |
| Pay-consent | A signed-in person's click in the console, recorded instead of a key signature for the root hop of a credit card payment. Accepted at the root only |
| Authority record | A signed, hash-linked record the core writes for every budget, hop, freeze, thaw, emergency stop, amendment, revocation and approval. The authority head is the signed count and last hash of a budget's records, which makes an evidence file complete |
| Revocation | Instant, structural termination of a stream and its whole delegated subtree. From owner-api 1.3.0, signed work in the subtree is settled first, then the halt applies; a settlement failure never holds the halt |
| Freeze | A resumable pause of a stream or branch (thaw resumes it). Signed claims stay settleable |
| Emergency stop | Stopping a whole budget at once (POST /owner/v1/budgets/{id}/stop). Signed claims stay settleable |
| Main switch | One control that pauses new metered work across every budget of a deployment or tenant, and resumes exactly what it paused |
Hard stop (wire: HaltError / budget.halted) | A fail-closed stop with an objective reason code (cap, rate, anomaly, sla, revoked, exposure, stopped, …). A stopped action bills nothing |
| Reservation | A two-phase meter: units are held (reserve), then billed (confirm) or released (cancel). Holds older than the deployment's reservation TTL are released by the scheduler |
| Task Allowance | A budget for one piece of work with milestones: the payee signs a delivery claim, and the claimed units are paid on acceptance (or silence) inside a window, or returned on rejection or expiry |
| Objective facts | Measurable, signed, reproducible quantities (latency, error rate, availability, unit counts, completion, acceptance events). The only signals settlement acts on |
| Oracle attestation | A signed statement of objective facts about a stream's service window, ingested fresh and in-band; missing or stale attestations fail closed |
| Verified-value settlement | Settlement conditioned on objective-fact attestations against declared SLA thresholds - throttle, hard stop, break-point, refund |
| Fee netting | Recovery of reversed fees from the payee: settled balance first, then negative-balance IOU against future settlements |
| Evidence bundle | A portable, offline-verifiable export with a digest manifest. evidence/1.0.0 covers one session; evidence/1.1.0 to 1.4.0 cover a whole budget with its signed authority records and head. Its signatures verify offline; it proves billing only together with the on-chain settlement or the engine-signed payment records |
| Σ proof | The re-derivable inequality chain: Σ child settlements ≤ funded ceiling, fee rows explicit, finality states per unit range |
| x402 | The HTTP 402 payment-challenge convention: a machine-readable challenge answered by an X-PAYMENT header, in exact (discrete) or dynamo-allowance (streaming) scheme |
| Session | The reconciled aggregate of one budget's lifetime: per-stream totals, settlement records, refunds, fees - engine equal to settlement layer, to the unit |
| Reconciliation | The end-of-session equality check between engine accounting and settlement-layer truth. Every demo prints it; a mismatch exits non-zero |
| Tenant | One account on a multi-tenant deployment (CORE_TENANCY=multi), with its own stores, signer, keys, limits, events and dashboard session |
| Scoped credential | A long-lived bearer secret limited to one role: a payee (its own /payee/v1/* routes and meters), a gateway hook or a delegator. Refused outside its scope (credential_scope) |
| Live (status) | Usable today in Control Mode, Stripe TEST mode, or on a local or test chain |
| Preview (status) | Built, but behind a switch that is off by default |
| Release-gated (status) | Needs real money, live credit card keys or operator-mode ramps; off in this release. Live credit card keys and live ramp-provider keys refuse to boot; a stablecoin mode on a real-money chain is not refused in code, but starts only when the operator allows it and the vault's owner and fee collector are Safe multisigs |