Ledger Event

#How It Works

Each Ledger Event carries a dual classification. The event type names the accounting action; the business classification names what the movement is in business terms — a fixed cost, an offering cost of goods, a shared cost of goods, or routed contract-split revenue. Both axes are recorded on the event and are never inferred later. Beyond that, an event carries an amount, a timestamp, and mandatory directional Node references, and it can also point at the originating contract and a milestone.

Because the stream is append-only, an event is authoritative the moment it is recorded and is never modified or deleted. When something needs correcting, the fix is a new compensating Ledger Event — leaving the original intact and letting every derived view recompute from the corrected history.

#Statements

These statements fix what a Ledger Event is and the append-only correction model.

Definition and append-only nature

• A Ledger Event records a financial fact.
• A Ledger Event is append-only.

Event payload

• A Ledger Event has an event type, business classification, amount, and timestamp.
• A Ledger Event can reference from-node, to-node, contract, and milestone.

Correction model

• A Ledger Event correction uses a compensating Ledger Event.
• A derived financial view is rebuilt from Ledger Events.

#Operations

Ledger operations are the only way value movements enter financial history. Recording a Ledger Event captures a financial fact; correcting one never edits or deletes the original but adds a compensating event instead. That keeps the ledger append-only and lets every derived view — wallet balances, P&L — be rebuilt from the event stream.

Record Ledger Event writes an immutable financial fact, carrying the amount, timestamp, event type, and business classification that place the movement in the dual-classification model. Correct Ledger Event does not touch the original: it records a compensating Ledger Event that preserves the prior record and adds the correction as a new financial fact, so history only ever grows.

Record Ledger Event

• Record Ledger Event records a financial fact.
• Record Ledger Event uses amount, timestamp, event type, and business classification.

Correct Ledger Event

• Correct Ledger Event records a compensating Ledger Event.
• Correct Ledger Event preserves the original Ledger Event and adds the correction as a new financial fact.

#Financial View

Ledger Events are the source of truth behind every derived financial view. A Wallet balance is the running result of its events; a Node P&L view is the result of those events combined with the organization's configuration policy over an explicit period. Classification is what lets a flat stream resolve into a readable P&L: fixed-cost events add to a Node's fixed-cost total, offering cost-of-goods events name the Offering whose P&L receives the cost, shared cost-of-goods events pool at Node level for later allocation, and contract-split events route value to a receiving Node as period revenue.

For the cross-cutting derivation rules see:

• Source Truth — full source-of-truth contract for every derived financial view.
• Financial Classification — how event type and business classification feed downstream views.
• Period Scope — the explicit time windows every view runs against.
• Shared Cost Allocation — how shared cost-of-goods pools spread across offerings in derived views.
• Recurring Periods — how recurring payment streams materialize as Ledger Events.

#Why It Matters

Ledger Events are the financial bedrock of the standard. Wallet balances, P&L views, and every other financial view are derived from them rather than stored independently — so the ledger is authoritative, not a balance field. Making the stream append-only is what keeps that history trustworthy: nothing is silently changed after the fact, the same period can be recomputed at any time and still produce the same result, and every line in every view resolves back to the events that fed it.

#Related

• Wallet — balances derived from the Ledger Event stream.
• Contract — the agreements that generate Ledger Events.
• Node — the directional references every event carries.
• Cap Table — the ownership surface that lives alongside the ledger.
• Offering — what offering cost-of-goods events attribute to.
• Milestone — the reviewable checkpoints an event can reference.