Topic Hub
Curated insights and technical field notes on Treasury management.
Reader guide
Start with the newest decision note, then follow the topic lanes when you need payments, AI systems, or product architecture depth.
Decision notes
Clear recommendation, rejected paths, and proof trail.
Systems maps
Visual artifacts sit near the section they explain.
Source posture
Public claims stay tied to released work or cited material.
A bank buys a modern payment platform and keeps the 2019 team structure, the same escalation matrix, the same three-person on-call rotation. The platform ships daily. The governance model says 90 days. Most modernization failures are operating-model failures, and the org chart defeats the architecture every time.
Lead essay
Start here when you want the current Doric argument instead of a 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.
From March 2026, Nacha standardizes the ACH Company Entry Description as PAYROLL or PURCHASE for those payment types. It sounds trivial, but a free-text field becoming a dependable category is what finally lets reconciliation automation stick on a rail that still moves tens of billions of payments a year.
Since October 2025, euro credit transfers run a Verification of Payee check before they settle, and a name-IBAN mismatch triggers an alert. It hits US treasuries paying EUR vendors and payroll as hard as it hits EU banks, and the same name checks are a fair bet to reach FedNow and RTP next.
The API worked. The books did not. A clean REST interface with pretty JSON still leaves accounting stitching exports for three days to answer one question - what happened to this payment across every rail and every failure path. ERP-grade APIs treat the contract as a shared language with finance.