The Journal
Essays on architectural decisions, engineering trade-offs, and the thinking behind the systems.
Q2 2026
Why Extracted Obligations Never Activate Themselves
From the Contract Lifecycle Engine system
Why the PO Resolver Has Five Strategies, Not One Algorithm
From the Invoice Reconciliation Engine system
Why Anomaly Detection Can't Block the Ingestion Pipeline
From the Sensor Telemetry Engine system
Stripe Said Past Due. The State Machine Said No. Both Were Right.
From the Subscription Lifecycle Engine system
Why I Compute Every Appointment Slot from Scratch on Every Request
From the Clinical Scheduling Engine system
The Compliance Problem That Disappears When You Stop Updating Rows
From the Financial Compliance Ledger system
I Spent a Week Securing Webhook Ingestion. The Real Attack Surface Was Delivery.
From the Webhook Ingestion Engine system
Building a DAG Orchestrator That Rewrites Its Own Execution Plan
From the Workflow Automation Engine system
Why I Designed the Whole System Around Kafka and Then Deployed Without It
From the Event-Driven Notification Hub system
Q1 2026
I Built a Knowledge Graph Into the Retrieval Pipeline and Then Dropped It in Production
From the Multi-Agent RAG Platform system
The Matching Problem No One Talks About
From the Transaction Reconciliation Engine system
How a 58-Table Subscription Crashed the Entire Replication Cluster
From the Centralized Property Intelligence Hub system
Why the Pricing Algorithm Has Two Completely Different Strategies for Rank 1
From the Idealo Price Optimization Platform system
Why I Split Minutes Prediction Into Two Models Instead of One
From the NBA Scenario Engine system
Why I Run the Entire Pipeline Twice to Match Products
From the Solar Pricing Engine system
Get Notified
New system breakdown? You'll know first.