Commerce and the five ledgers

Transactions define commitments, metering records consumption and ledgers record changes in value; fulfilment and acceptance are never replaced by a successful payment.

In developmentNot availableVerified

Commerce and the five ledgers diagram (A07) (open full-size figure)
MYRILUM architecture map v2.2 · A07 (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”.

Transactions make commitments explicit; metering records consumption; ledgers record changes in value; fulfilment and acceptance are never replaced by a successful payment.

Payment succeeded ≠ task completed; verification passed ≠ user accepted; contribution recorded ≠ cash or equity.

Products enter a commercial contract

Product versionSupported scope, inputs and outputs, licensing and after-sales
Offer and quotePricing unit, price version, tax fields and validity
Order and contractBuyer, seller, terms, currency and fulfilment link
Payment and entitlement checkExisting entitlements can satisfy a task directly; no new purchase is forced for every task

Fulfilment and value confirmation

Entitlement grant and reservationPurchase and usage rights are separate; actions still need authorization
Fulfilment requestScope, service period, delivery standards and budget
Delivery, acceptance and disputesAn authorized user decides; verification cannot replace acceptance
Billing, settlement and after-salesCharged as contracted; refunds and compensation each have their own status

Five kinds of records: stored apart, linked by reference

Cash, receivables and payablesActual funds recorded per party and per currency
Service creditsCredited, granted, reserved, consumed, expired and restored
EntitlementsMembership, seats, features and license terms; never administrative authority
Resource usageRaw consumption such as model volume, image count and processing time
Contribution recordsAttribution and recognition never automatically mean pay or equity

Settlement controls and business reconciliation

Actual usageRaw quantity, unit and provider call identifier
RatingTurns usage into charges using the price snapshot and the contract
Journal entries and correctionsIdempotent writes; different currencies or units are never added together directly
Multi-party reconciliationOrders, entitlements, usage, user bills and provider bills

Source

This page follows A07 of the MYRILUM architecture map v2.2 (public edition: restricted products and internal open items are left out).

Was this page helpful?

Sources and maintenance
Region
Global
Version
0.1.0
Publication
Published globally
Document status
Approved · Validated
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
882487dec08b
Canonical authority
SRC-ARCHITECTURE-ATLAS-V2-2
Content digest
5903ca6ac1d67a42
Stable citation
MYRILUM-DOC-ARCH-007@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 · Validated
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
882487dec08b
Canonical authority
SRC-ARCHITECTURE-ATLAS-V2-2
Content digest
5903ca6ac1d67a42
Stable citation
MYRILUM-DOC-ARCH-007@0.1.0:en#overview

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