Topic Hub
Curated insights and technical field notes on RTP.
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.
Your real-time rails settle in fifteen seconds. Your treasury org chart was built around an end-of-day cutoff. The gap between them is where the next reconciliation loss lives, and it shows up in three roles - cash positioning, exception ops, and intraday risk - long before it shows up in the tech stack.
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.
An $8M deal chopped into 16 payments because one bank used FedNow. With TCH-RTP at a $10M limit and FedNow at $500K, transaction size is quietly deciding which rail a corporate treasurer can use.