Work the exception.
Keep the whole story.

Use a new reference each time. All carriers and external delivery are simulated. The durable backend and customer portal are real within your authorized demonstration workspace.

1. Open the interactive public demo and select Start fictional demo. An isolated workspace with one synthetic record is created; private Operations remains available for signed-in use. Select Customer portal preview, choose New shipment, and save a fictional machine-parts load. The default delivery deadline is in the past to expose a late-arrival exception.
2. Switch to Manager / owner. Open Readiness and record a synthetic authority, insurance and identity review for Copperline, with an official reference, explanatory note and future expiry. This is a fictional review, not a real carrier lookup. On Carriers, propose Copperline and approve its award with a reason. On Events, record a delay with the default three-hour-old timestamp. Run exception check from Overview.
3. On Carriers, propose Copperline again, then reject it because the plan cannot recover the delivery window. Record Summit Relay’s synthetic review on Readiness, then propose Summit Relay and approve its faster plan after reviewing the $275 premium.
4. On Events, submit the same event key twice. The duplicate is ignored. Add a location event older than the delay; it is retained as historical without replacing the latest observation.
5. On Updates, edit the generated exception draft. Test provider failure, then approve and publish it. Customer portal preview shows only approved portal updates. Premium OpenAI reasoning and transcription remain disabled pending access and revised budget validation. The deterministic guide remains available.
6. Record a Delivered event with the current ISO timestamp. Run exception check: missing proof of delivery is flagged. Try Prepare billing packet; it remains blocked. On Documents, verify a fictional receiver signature and download the private receipt.
7. On Overview, Prepare billing packet, then Complete shipment. On Readiness, prepare and inspect the immutable finance review packet JSON, then inspect Audit. No invoice or payment is transmitted. Reload the page to verify persistence. The customer portal contains the final state, receipt and approved updates.
8. On Service, submit a customer change or damage incident request. It saves a scoped request and automatically creates an internal follow-up unless paused. Owner review of a change does not itself overwrite a deadline. Record a fictional appointment window and attendance; departure clears its follow-up on the next check. Work holds desk assignments, task progress and history.
9. Control tower summarizes saved customer requests, active handoffs, last checks and integration state. The contextual guide explains the selected shipment, opens controls and confirms an exception check only after you approve it. Microphone dictation is optional; type instead when unavailable.
10. Owner controls can pause/resume automation, save issue notes and export workspace records. Dispatch calendar displays saved review times and delivery deadlines. Search can filter persisted records by reference, route, status and UTC deadline date.
11. Updates also contains disabled email, calendar and Twilio fixture jobs. Queue a fixture, test a failure, run it successfully, and record its separate delivery receipt. Repeated receipts are idempotent. No external action is taken.