Platform systems

Anatomy of a Form Submission: From Click to Customer Record The visitor sees a button and a half-second spinner; the system runs an assembly line — spam gate, server-side truth check, synchronous identity, archival storage, and a named-event announcement journeys trigger on. A trace, with the design choices defended.

How the Journey Engine Decides When to Send A journey looks like boxes and arrows; underneath it's a long-running program with one durable execution per person. Two doors in, three kinds of time, a wait-for-behavior node with a structurally required timeout branch, and explicit exits.

Building a Booking Availability Engine Availability isn't stored — it's the negative space surviving an intersection of hours, staff, bookings, buffers, capacity, and policy, discretized into honest slots and re-verified at confirmation. Why 'when can I come in?' is one of the hardest answers a platform computes.

What It Takes to Deliver Email at Scale A sent email is a claim; delivery is a verdict. Inside the machinery — bounce taxonomy, deliberate skips, sender reputation, and the feedback loop that makes wanted mail deliver better.