Docs

Search and contents

Metering, budgets, service credit and ledgers

Reserve first, then execute, and keep real consumption apart from what users are billed; cash, service credit, entitlements, resource usage and contribution are five kinds of record, each managed in its own units and rights, and reconciliation finds what does not match.

In developmentNot availableVerified

Metering, budgets, service credit and ledgers diagram (A23) (open full-size figure)
MYRILUM architecture map v2.2 · A23 (public edition). Labels are in Chinese; every element is listed in English below. Select the diagram to open it at full size.

What this map shows

This is MYRILUM's target architecture. It does not mean everything on the map is live; whether a capability can be used today is stated in “Current availability”.

Reserve before executing, and keep real consumption apart from user billing; five kinds of record are managed with different units and rights.

Usage records real consumption; the contract decides the fee; the ledger records change; reconciliation finds inconsistencies.

Budgets and holding credit

Approved budget or entitlementTask ceiling, product policy and available licences
Atomic reservationSafe under concurrency; bound to a business action and a unit
Calls and in-flight holdsKeeps the necessary reservation while an external operation is unconfirmed
Reconcile and releaseSettles actual consumption; releases only what is confirmed unused

Turning raw usage into fees

Usage eventQuantity, unit, request identifier and time of occurrence
De-duplication and validationThe same event is never billed twice; late reports are traceable
Rating against a price snapshotBy contract, model or tool version and pricing unit
Entries and correctionsOld entries are never overwritten; errors are fixed through explicit correcting records

The five kinds of record, one by one

1 Cash, receivables and payablesRecorded by entity and currency, linked to external evidence of funds
2 Service creditCredits, grants, reservations, consumption, expiry and restoration
3 EntitlementsSeats, features, service counts and licence periods
4 Resource usageRaw consumption such as model volume, image count and processing time

Contribution and cross-record reconciliation

5 Contribution recordActions, evidence, attribution, confirmation and correction; independent of funds
Multi-party reconciliationUsage, prices, user bills, provider bills and the general ledger
Discrepancy queueDuplicates, gaps, unknowns, overruns and unit mismatches
Traceable closureEvery discrepancy has an explanation and an owner; the original record is kept after correction

Source

This page follows A23 of the MYRILUM architecture map v2.2 (public edition: restricted products and internal open items are left out). Related: “Commerce and the five ledgers”; “Agent runtime and failure recovery”; “Orders, payments, settlement and disputes”.

Was this page helpful?

MYRILUM platform architecture overviewSee how participants, the unified entry, business platform domains, the shared core, the agent layer, the execution network and infrastructure are layered, and how governance runs through all of them.Commerce and the five ledgersTransactions define commitments, metering records consumption and ledgers record changes in value; fulfilment and acceptance are never replaced by a successful payment.Agent runtime and failure recoveryAgent definitions, business tasks, run instances, attempts and external operations are modelled separately; long-running work relies on durable state, leases, idempotency and recovery, not on a chat window left open.Orders, payments, settlement and disputesThe platform's own accounts are kept apart from third-party marketplace commerce, and the real state of funds follows verified external records. An unclear state is reconciled first; refunds and settlement need authorization, receipts and journal entries, and nothing is booked on a model's answer.What is available now?What MYRILUM officially operates today: distinguish website browsing, the member store, scoped delivery and component records, and check availability for the region and account.
Sources and maintenance
Region
Global
Version
0.1.0
Publication
Published globally
Document status
Approved · Drafted
Authorization
Public information
Command authority
None
Type
Concept
Audience
Technical leads, Developers, Organization leaders, Integration partners, Agents
Safety class
Informational
Agent tasks
understand_platform_architecture
Owner
Web3Capital Documentation Steward
Last verified
2026-09-23
Review due
2026-10-23
Source commit
6b41cce4496d
Canonical authority
SRC-ARCHITECTURE-ATLAS-V2-2
Content digest
2ad8835626be2f5f
Stable citation
MYRILUM-DOC-ARCH-023@0.1.0:en#overview

Machine-readableMarkdownMetadataJSON-LDChunks

This documentation grants no execution, release, or production authority.

Sources and maintenance

Region
Global
Version
0.1.0
Publication
Published globally
Document status
Approved · Drafted
Authorization
Public information
Command authority
None
Type
Concept
Audience
Technical leads, Developers, Organization leaders, Integration partners, Agents
Safety class
Informational
Agent tasks
understand_platform_architecture
Owner
Web3Capital Documentation Steward
Last verified
2026-09-23
Review due
2026-10-23
Source commit
6b41cce4496d
Canonical authority
SRC-ARCHITECTURE-ATLAS-V2-2
Content digest
2ad8835626be2f5f
Stable citation
MYRILUM-DOC-ARCH-023@0.1.0:en#overview

This documentation grants no execution, release, or production authority.