A complete case at Kearney Funeral Services, from first call to closure. Scrub through the timeline to watch the pipeline come to life — locked compliance gates, conditional pass-throughs, system cascades, and the regulatory hero moments — exactly as the engine will execute them.
Loading...
Reading through this case reveals several behaviors that are easier to see in a real flow than in a spec.
Even at case close, the envelope contains roughly fifty routing keys. It does not contain the deceased's full name, contact details, obituary text, or contract line items. Those live in their proper home tables. The envelope answers did the cremation authorization get obtained, not what did the obituary say.
When a human task completes, downstream system_event and conditional modules run in the same transaction, advancing the pipeline to the next human-required step in under a second. The engine feels responsive rather than ceremonial.
Four modules in this case were skipped — bariatric_flag, livestream_setup, donation_transfer, regulatory_report. Each has a row with status: skipped and a skip_reason. The audit trail records that the system considered them and decided they did not apply.
Removal authorization. Three custody scans. Receiving verification. Identity reverification. Embalming decision. Contract execution. Cremation authorization gate. Remains return. Asset terminal check. Case closure. That sequence is the audit story — a complete chain from first call to closure, each step gated by something the regulator cares about.
A single coroner_hold_check module decides whether two downstream transfer modules execute. A single veterans_flag module decides whether military honors coordination activates. One conditional determines the operational path for an entire branch — without reordering the sequence and without a template variant.
QR scans at pickup, receiving, and disposition prompt the executor to advance. DocuSign webhooks prompt it to close document gates. The system is reactive at its execution boundary — it does not ask staff to confirm is the body now at the funeral home; the receiving scan tells it.
All 38 modules in template-defined sort order. 14 locked · 12 standard · 12 optional.