Blog · PG-20
Engineer-authored explainers
Four to six posts a month, organised by the same topic clusters as the rest of the site. Argument and evidence, not announcements.
Topic hubs
Ledger infrastructure
What a headless ledger is, how it differs from a traditional accounting API, and why the data layer is the bottleneck under AI-native finance.
From the calendar: What is a scenario dimension in a ledger? · Plan vs actual in one ledger (without ETL) · Air-gapped accounting: running the ledger where the data lives
Temporal & lifecycle
Provisional vs final, bitemporal reads, and what “the number as we believed it” means for a close calendar.
From the calendar: Provisional entries explained: the lifecycle most ledgers can't express · Why you can't edit a finalized journal entry · Bitemporal ledgers: balance-now, balance-then, believed-then
Immutability & compliance
Hash chains without blockchain, OCEL 2.1 for finance, and what an auditor can verify without trusting the vendor.
From the calendar: OCEL2 for finance: object-centric provenance, explained · What will your ledger refuse to book? Compliance packs explained · Post-quantum readiness for financial records
Agent-native ledgers
Governed MCP write paths, materiality tiers, and how to audit what an agent did — from evidence, not logs.
From the calendar: How to audit what an AI agent did in your financial system · Row-level access for agent writes: token→scope→row · Accounting MCP server: what a governed write path actually looks like
Reconciliation & FP&A
N-sided reconciliation and the FP&A consumption contract: what changes when the close and the forecast read the same ledger.
From the calendar: Reconciliation by relationship: one number from billing, terminals, channels and bank · N-sided control totals explained: why matching only two sides fails · Forecast on numbers you can verify: quality-gated FP&A · Variance on one ledger: drill from board number to posting
Editorial calendar — the first 16 posts
The planned sequence, gap-lane topics first. Titles are working titles and every row’s status is planned: no dates are shown because none are committed, and nothing below is published. A title moves only when its draft passes the editorial rules at the foot of this page.
| # | Working title | Cluster | Lands on | Status |
|---|---|---|---|---|
| 1 | What is a scenario dimension in a ledger? | Ledger infrastructure | /scenario-dimension | Roadmap planned |
| 2 | Plan vs actual in one ledger (without ETL) | Ledger infrastructure | /scenario-dimension#plan-vs-actual | Roadmap planned |
| 3 | Provisional entries explained: the lifecycle most ledgers can't express | Temporal & lifecycle | /provisional-lifecycle | Roadmap planned |
| 4 | Why you can't edit a finalized journal entry | Temporal & lifecycle | /immutable-ledger#corrections | Roadmap planned |
| 5 | OCEL2 for finance: object-centric provenance, explained | Immutability & compliance | /provenance-ocel2#faq | Roadmap planned |
| 6 | How to audit what an AI agent did in your financial system | Agent-native ledgers | /ai-agent-audit-trail#how | Roadmap planned |
| 7 | Row-level access for agent writes: token→scope→row | Agent-native ledgers | /mcp-server#governance | Roadmap planned |
| 8 | What will your ledger refuse to book? Compliance packs explained | Immutability & compliance | /platform#api | Roadmap planned |
| 9 | Bitemporal ledgers: balance-now, balance-then, believed-then | Temporal & lifecycle | /provisional-lifecycle#as-of | Roadmap planned |
| 10 | Air-gapped accounting: running the ledger where the data lives | Ledger infrastructure | /self-host | Roadmap planned |
| 11 | Post-quantum readiness for financial records | Immutability & compliance | /self-host (crypto section) | Roadmap planned |
| 12 | Accounting MCP server: what a governed write path actually looks like | Agent-native ledgers | /mcp-server | Roadmap planned |
| 13 | Reconciliation by relationship: one number from billing, terminals, channels and bank | Reconciliation & FP&A | /reconciliation#n-sided | Roadmap planned |
| 14 | N-sided control totals explained: why matching only two sides fails | Reconciliation & FP&A | /reconciliation#assertion-edges | Roadmap planned |
| 15 | Forecast on numbers you can verify: quality-gated FP&A | Reconciliation & FP&A | /fp-and-a#maturity | Roadmap planned |
| 16 | Variance on one ledger: drill from board number to posting | Reconciliation & FP&A | /fp-and-a#variance | Roadmap planned |
Deferred beyond this list (post-launch): the definitional and category-hub explainers, ledger-vs-ERP ingestion, Continuous close and the data-layer boundary, and the payment-ledger-vs-accounting-ledger piece — the last is answered today as a FAQ unit on the Formance comparison. RSS at /blog/rss.xml ships with the first published post.
Case studies — held pre-launch
Three case-study skeletons are held in the repo, each marked PRE-LAUNCH and carrying the field template below. No skeleton publishes before its outcome fields are filled and approved, no customer is named or counted before written consent, and none of the three is indexed. They exist now so the first design-partner write-ups land in a checked format.
Platform builder: embedded ledger per tenant
PRE-LAUNCH · skeleton held · noindex
Persona line (PA-5): “Invariants below you: double-entry, immutability, governance — as an API and an MCP server.”
- Trigger & estate — to capture: industry and source systems.
- Deployment — to record: self-host, air-gap or VPC, and the agent surface in that deployment.
- Workstream — the lifecycle, scenario, provenance and access-control requirements in play.
- Measured outcome — published only if measured, with method and date.
- Quotes — name and title only with written approval.
- Reviewer notes — what they found hard, published as-is.
Enterprise finance: consolidation sink under a legacy estate
PRE-LAUNCH · skeleton held · noindex
Persona line (PA-1): “Zero-day truth without weakening the audit trail: provisional numbers today, provable numbers forever.”
- Trigger & estate — to capture: the ERP and sub-ledger estate the sink sits under.
- Deployment — to record: self-host or air-gap, and residency requirements.
- Workstream — ingestion receipts, multi-entity consolidation, close gates and corrections.
- Measured outcome — published only if measured, with method and date.
- Quotes — name and title only with written approval.
- Reviewer notes — what they found hard, published as-is.
External auditor: verification tooling, read-only
PRE-LAUNCH · skeleton held · noindex
Persona line (PA-3): “Verify immutability instead of trusting it — run the chain check yourself, without ledger access.”
- Trigger & estate — to capture: engagement type and the evidence requested.
- Deployment — to record: where the verifier ran, and against which export.
- Workstream — chain verification, OCEL 2.1 export and typed-correction evidence.
- Measured outcome — published only if measured, with method and date.
- Quotes — name and title only with written approval.
- Reviewer notes — what they found hard, published as-is.
Editorial rules
- Every published number is reproducible from the docs or the repo; every third-party fact links its source and a verification date.
- Posts inline-link at least two glossary terms, and glossary terms link back to the posts that use them.
- No autoplay media, no gated posts, no AI-spun filler: if a post cannot cite, it does not ship.
RSS ships with the first post.
Get the first posts
Waitlist members get explainers first, and the changelog digest alongside them.