Human approval is a command boundaryEvery outbound action keeps actor, reason, target, source version, and previous state.
FO
FleetOps system conceptEvent operations architecture
Database is authoritative · Google Sheets remains the team interface
Operations dashboardInteractive React architecture
From fragmented fleet inputs to approved action.
Click any component, or advance the highlighted incident path to talk through how the system prevents a missed vehicle.
External sourceAuthoritative stateHuman controlObservability
LIVE SYSTEM MAPSources → operational truth → detection → approval → delivery
Scenario path activen8n coordinates work; it does not own operational state.Retries, dead letters, and channel delivery stay visible without turning the workflow engine into the database.
Every answer carries provenanceThe assistant exposes record source and freshness instead of sounding certain about stale data.
Misses are product input from day oneQuestions, unsupported answers, retries, and dead letters become an observable improvement queue.