Reality Gaps
Each gap is ordered by deterministic severity, deployment criticality, and evidence strength. Open a finding to inspect the exact sources behind it.
The pilot requires continuous ride updates, while drivers report material coverage gaps and the current architecture has no durable offline queue or reconnect synchronization.
Finance expects weekly transaction-level reconciliation, while current wallet records retain balances without immutable event or actor history.
Operations requires verified drivers, but the product has only a boolean flag and no traceable submission, review, rejection, or audit workflow.
The pilot is expected to expand quickly, but urgent incident ownership, after-hours coverage, severity levels, and response targets are not defined.
Management requires SMS onboarding and the technical design depends on a paid provider, but the approved pilot budget excludes SMS costs.
Riders expect cancellation, but requirements and service rules do not define permitted stages, reasons, or fees after matching.