How DwellGuard Works
The delay happened. The plan kept moving.
Spoken Constraint Relay & Sequential Authority Architecture
Freight delay tools frequently stop at sending an alert or placing an uncoordinated call. DwellGuard establishes a strict sequential authority chain powered by the Spoken Constraint Relay: the driver's spoken boundary visibly rewrites the dock request before call two is placed, and the dock's commitment returns as the same versioned plan on the driver's phone.
- Dispatcher Limits: The dispatcher freezes acceptable arrival times, maximum allowable accessorial fees, and a hard 2-call budget.
- Driver Verification: CALL-E calls the late driver to verify their actual workable check-in window and asks if they authorize automated scheduling inside that interval.
- Interval Reshaping (Plan Rail): The driver's verified window is mathematically intersected with dispatcher limits. Impossible times fade on the Plan Rail, and the dock request is rewritten with the real overlap.
- Dock Commitment: CALL-E calls the receiving dock to confirm an explicit time and designated door within the driver's approved range, verifying fee boundaries.
- Causal Appointment Proof & Driver Handoff: When confirmed, a deterministic, privacy-safe Causal Appointment Proof (with SHA-256 hash and matching display ID) is generated. The official appointment pass is delivered directly to the driver's mobile page for tap acknowledgment.
Truthful Outcomes
- Plan Confirmed: Both parties verified explicit slot inside approved boundaries.
- Driver Received: Driver tapped acknowledgment on scoped mobile handoff link.
- Dispatcher Needed: Fee exceeded, driver refused permission, or times conflicted. Never false green.
Real vs. Simulated Replay
The public /demo replay executes the full production domain state machine, interval math, and validation engine using an in-memory fixture transport. It cannot dial or consume telephony credits.
Live deployment connects to official @call-e/calle server SDK when credentials are configured.