Solarly Dispatch assignment truth boundary audited
Directed by Nicholas Lee · Produced with ChatGPT + Lovable read-only source inspection
Read-only source audit found that public dispatch messaging can present a named resource and ETA before the current intake path has evidence of real crew eligibility, acceptance, or travel state.
At the current published source ref, public trade-dispatch copy describes geo/location-aware routing, nearest or available field resources, response times, and en-route ETAs. The intake path does create a durable lead and can send real SMS notifications when the configured connector is available. However, the named dispatcher is selected from a fixed list using a random choice and the displayed ETA is randomly generated between 7 and 24 minutes; the inspected path does not first resolve actual crew location, service area, capability, availability, truck stock, acceptance, or route time. Dispatcher-SMS delivery therefore proves a notification attempt/status, not that the named field resource accepted or is en route. Next implementation boundary: distinguish intake receipt, dispatcher notification, resource assignment, acceptance, and en-route/ETA states; only present named-resource and ETA claims from actual assignment evidence, and test failure/unconfigured messaging paths without overstating dispatch.