Topic Hub
High-level system design, edge compute patterns, database scaling, and technical decisions behind enterprise applications.
Current note
The newest published argument and its visual artifact lead the page.
Read the noteEditorial posture
The library is organized around decisions that keep recurring in payment architecture, AI systems, and Doric product work. New notes lead by publish date, while topic lanes connect related arguments without turning the index into an archive wall.
Decision frame
Recommendation, rejected paths, and the operating proof behind the call.
Visual proof
Diagrams and original artifacts stay near the argument they explain.
Source posture
Public claims stay tied to released work or cited material.
Large-bank modernization programs increasingly put orchestration, ledgers, and customer-master capabilities around existing cores. That sequence can reduce conversion risk. Without explicit retirement ownership and dates, it creates another permanent layer and extends dual-running cost.
Lead essay
The current Doric argument leads the index ahead of the chronological archive.
Read the noteNo field notes yet.
01 / Payments
Merchant-of-record decisions, checkout ownership, billing operations, settlement, reconciliation, and risk boundaries.
02 / AI tooling
Agentic commerce, multi-agent orchestration, model fine-tuning, runtime governance, and production deployment.
03 / Build notes
The design, architecture, and operating decisions behind Doric Stack products as they move from prototype to public release.
Teams treat cloud like a faster data center instead of a different computing model. Banking workloads are not web apps - and lift-and-shifting a mainframe to the cloud buys you cloud costs with mainframe complexity.
The BIS just blueprinted a tokenized unified ledger and JPMorgan put a deposit token on a public chain - in the same week. The hard part for banks was never the blockchain. It is retrofitting core banking to carry programmable money without a big-bang migration.
Fiserv, Bottomline, and a core banking system each work fine alone. Wiring them into one payment chain is where projects go to die - and the difference between the ones that survive and the ones that become expensive lessons is a handful of boring resilience patterns.