Topic Hub
Curated insights and technical field notes on Architecture.
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.
What was the cash position at 11:47am? On a snapshot-based model the honest answer is an interpolation between two saved states. Real-time rails turned that guess into a liability, and the fix is to stop storing a position at all and fold an immutable event log into the answer. The event log is not free, and most teams have not put the bill on the budget.
The translator is ready, the mapping is tested, the structured fields are wired - and the project is still not on track, because the customer records are missing structured address data across KYC, core banking, and correspondent files. In November 2026, SWIFT, SEPA, and CHAPS start rejecting unstructured addresses, and most banks are framing the wrong problem.
Payment integration usually starts with a PDF, a sandbox that takes days to provision, and a support email that answers in 48 hours - and the third email is where patience dies and a competitor gets Googled. I built a self-service workbench to close the distance between what a platform can do and what a developer can figure out alone.