Insights
The reference · updated August 2026 · 9,400 words
A working reference for architects deciding whether a distributed ledger belongs in a system, and what it costs to run one inside an enterprise. Written from delivery experience, including the parts that went badly.
The complete reference: which decisions to automate, how to prove a system behaved correctly, what integration actually costs, and the failure modes that appear six months after a successful pilot.
v2.1 · 9 hubs · 11,200 wordsA working reference for architects deciding whether a distributed ledger belongs in a system, and what it costs to run one inside an enterprise. Written from delivery experience, including the parts that went badly.
v3.0 · 8 hubs · 9,400 wordsWhat an agent may commit, under whose approval, against which limit, and how the action is unwound. The reference for putting agents inside a control environment rather than beside one.
v1.2 · 7 hubs · 8,600 wordsThe register, the restrictions, the redemption path and the reconciliation behind them. The engineering half of tokenizing an instrument, written for the team that has to operate it afterwards.
v1.4 · 8 hubs · 7,900 wordsLicensing software someone else operates under their own brand: the responsibility split, the upgrade path, the support posture, and the evidence a licensing buyer checks before a demo.
v1.1 · 8 hubs · 7,200 wordsWhat changed in the architecture of mlgblockchain.com, and why the old service pages now point here.
A test suite built from labelled history, run before anyone sees a demo — and an honest account of what a passing score does not prove.
A ceremony performed once, by the people who designed it, proves very little. Designing one an operations team can run without you is the deliverable.
Who can change the code, under what approval, and what that means to an auditor.
A working example: idempotency keys, reorg handling, and a documented break procedure.
When an instrument is redeemable against a physical reserve, the custody boundary and the reconciliation model are one design.
How an accounting system’s finality assumption decides the shortlist before throughput does.
A 3-of-5 signing policy looks conservative on the day it is designed. It is a headcount bet, and most institutions lose it within eighteen months — quietly, because nothing breaks until the day a signature is needed.
The build vocabulary as a machine-readable term set. 86 terms published of a 250-term target, each defined once and linked from every page that uses it.
All termsllms.txt, plus TechArticle and DefinedTermSet structured data throughout. Nothing here is gated or paywalled, and citation blocks are stable.
Search the library