01
LIVE
Observe
Follow every agent, workflow branch, external action, and human decision in one live context.
Engineering case study / Handle
A voice-driven insurance workflow that recovers safely.
Sapnix FlightDeck turns a live browser conversation into a validated commercial fleet renewal, produces three synthetic estimates, and demonstrates what happens when one carrier workflow changes mid-execution.
Design hypothesis
Detect
Contain
Resume
Independent prototype Built for two Handle roles Synthetic carrier outputs
Browser intakeFleet renewal Context captured
Voice risk profile17 gate fields validated
CASE STUDYHANDLE / 0042
NorthwindDRIFT
SummitCOMPLETE
HarborlineRUNNING
Rescue roomREVIEW
Portal contract changedOne branch paused. Two branches continue safely.
Approve correction
Prepared forHandleIndependent interview case study
Target rolesSenior Software Engineer+ Forward Deployed Engineer
Prototype scopeLive voice, controlled executionReal intake · synthetic carrier estimates
THE PROTOTYPE / LIVE ENTRY + SIMULATED CARRIERSFrom voice intake
From voice intake
to safe recovery.
The signed-in demo creates a case only after a complete browser voice interview and explicit approval. It prices three synthetic carrier estimates, then injects a disclosed recovery test to demonstrate containment and idempotent replay.
Start live demoLIVE EXECUTIONSynthetic estimate orchestration
Northwind AssuranceBrowser portalqueued
Summit MutualBrowser portalqueued
Harborline InsuranceEmail adapterqueued
01 / WHAT IT DEMONSTRATESFour behaviors behind
Four behaviors behind
the polished interface.
The interface is evidence for an execution model: observable state, isolated failure, checkpointed recovery, and an auditable external-effects record.
02
Contain
Isolate a failing carrier integration without stopping safe work elsewhere in the case.
03
040506
Recover
Correct the integration once and resume from the last trusted checkpoint.
04
Prove
Replay the complete workflow and verify that no external action was duplicated.
02 / BEHAVIOR UNDER TESTOne case.
One case.
Every handoff preserved.
This is the production behavior the prototype explores: voice is the entry point, while every validated field, branch, external action, failure, approval, and recovered estimate remains attached to one operational context.
Inspect the proposed boundariesListen
A browser conversation becomes structured operational context.
Understand
Validated fleet, operations, losses, controls, and terms resolve into one canonical case.
Execute
Carrier adapters run in parallel with explicit safety boundaries.
Contain
A changed portal pauses only the branch that can no longer proceed safely.
Recover
A human correction is versioned and replay begins at the last checkpoint.
Prove
The final comparison includes a complete, replayable execution record.
03 / ENGINEERING DECISIONThe question is not “can it retry?”
The question is not “can it retry?”
It is “can it recover safely?”
TRADITIONAL AUTOMATIONWorkflow stopped
- 01 Retries without understanding the failure
- 02 Stops unrelated work in the same case
- 03 Risks duplicate external submissions
- 04 Leaves operators searching through logs
PROTOTYPED APPROACHSafe work continues
- 01 Classifies the failure before retrying
- 02 Isolates only the affected branch
- 03 Resumes with stable idempotency keys
- 04 Presents evidence and a versioned repair
04 / PROPOSED SYSTEM DESIGNProduction-minded.
Production-minded.
Intentionally simulated.
This prototype does not connect to Handle or any carrier. It maps the boundaries I would propose: browser-only interaction stays in the browser, secrets stay server-side, and shared operational state remains observable.
Explicit server boundaries Durable replay Human approval
01Browser voiceVapi Web SDK
02Validated intakeServer boundary
03Canonical caseConvex data
04Durable workflowCheckpointed steps
05Carrier adaptersParallel execution
06Human rescueExplicit approval
07Flight recorderRealtime audit
05 / ROLE ALIGNMENTWhy I built this
Why I built this
for these Handle roles.
SENIOR SOFTWARE ENGINEERING
Own the execution model.
The demo makes architecture visible: durable orchestration, state transitions, idempotent effects, observability, failure isolation, and typed boundaries.
- Durable orchestration
- Idempotent external actions
- Failure isolation
- Typed server boundaries
INDEPENDENT INTERVIEW PROTOTYPE
Start with your voice.
Inspect every decision.
Sign in with a one-time email code, complete the fleet-renewal intake in your browser, and follow the validated case through synthetic pricing, failure containment, human rescue, and safe replay. No phone number or carrier credentials are required.