Current Build Proof¶
This page summarizes current MYConnect proof for customer and partner readers. It is intentionally curated: it shows what is real in the local build without turning the pitch site into a raw engineering evidence dump.
Proof Standard¶
A route is not treated as complete just because it exists in navigation. MYConnect uses a production-near standard:
- Route-specific UI.
- Real API or server integration.
- Database persistence.
- Auth, permission, tenant isolation, and denied-access behavior.
- Audit or support traces where required.
- Focused tests and browser smoke evidence.
- Documentation and evidence that agree.
Current Local Production-Near Slices¶
| Phase | Area | Current local proof |
|---|---|---|
| Phase 01 | Admin, auth, companies, drivers, vehicles, depots, customers, trailers, settings | Route-backed admin/resource slices with persistence, permissions, tests, and smoke evidence. |
| Phase 02 | Devices and telemetry | Device registry, provisioning, vehicle assignment, HTTP telemetry ingest, diagnostics, latest state, and health snapshots. |
| Phase 03 | Fleet visibility | /fleet and /fleet/live-map with latest state, replay, geofences, utilization, alerts, and evaluator readiness assets. |
| Phase 04 | Transport operations | /jobs, /jobs/{jobId}, /dispatch, /exceptions, and /billing-export with guarded APIs and persisted records. |
| Phase 05 | Driver POD | Driver mobile API slice, status updates, POD persistence, offline-style diagnostics, and /pod admin review. |
| Phase 06 | Customer visibility | Customer portal, portal admin, visibility rules, accepted POD/report access, signed downloads, and audit records. |
Current Gaps That Are Not Hidden¶
MYConnect still separates local product proof from production or pilot rollout proof. The following remain separate gates:
- Production/staging secrets and environment rollout proof.
- Captured CI/CD run URLs and deployment logs.
- Production monitoring imports and reviews.
- Production object-storage policy, retention, legal hold, and backup/restore execution proof.
- Real provider notification credentials, callbacks, sender configuration, rate-limit monitoring, and support readiness.
- Native mobile device or emulator proof for the driver app.
- Later modules beyond current local slices: safety, cold chain, cost/profit analytics, integrations, AI workflows, partner services, and controlled marketplace workflows.
The pitch site should be read as a customer-facing product overview with current local proof. It is not a claim that all production/staging acceptance gates are already complete.