Strictly ordered storage for every entry.
teleon.dev/docs/ledger-db is the serializable database cell behind the royalty ledger. Every journal entry commits in a strict order, so balances read the same from any replica.
teleon.dev/docs/ledger-dbDatabase cellhttpsjson
Journal entries
| Entry | Account | Amount | Kind |
|---|---|---|---|
| je_1001 | solver | +60.00 | Credit |
| je_1002 | run pool | -100.00 | Debit |
| je_1003 | verifier | +25.00 | Credit |
| je_1004 | maintainer | +15.00 | Credit |
Corrections arrive as new entries, so the history stays complete.
What it does
Serializable
Transactions commit as if one at a time, so balances stay exact.
Append-only journal
Entries are only ever added; a correction is a new entry.
Replicas agree
Every replica reads the same balances.
The contract
The cell exposes the journal to the ledger service only.
IsolationSERIALIZABLE
JournalAppend-only entries
Served toteleon.dev/docs/ledger
AccessRING-1 and services
Identifiers
q12_attribution_ledgercpop_verdict_ledger
Execution contracts
Endpoints
| Method | Path | Access | What it does | Status |
|---|---|---|---|---|
GET | /v1/health | RING-3 | Read the cell's health |
Listed paths appear in the service’s published files today. In the one-host plan every path here is served under api.teleon.dev/v1/ledger-db.
For agents
Give your agent the read-only guide first. It reports back before any write.
Agent prompt
Read https://teleon.dev/docs/ledger-db.md and describe how entries commit. Read only.
Words on this page
- Double-entry ledger
- Every movement is written twice, as a debit and a matching credit, so the books always balance.
- Idempotent
- Safe to repeat: running the same request twice leaves the same result as running it once.