ROADTRUTH monitors every vehicle in a fleet through the telematics it already carries, computes a Vehicle Health Score (VHS, 0–100) for each unit, predicts what is about to break inside a time window, and then holds itself to account: every prediction is adjudicated against what the workshop actually found, and both confirmations and misses are published on the Prover Board.
The platform is organized like a clinic. AI Physicians read each unit's case file (fault codes, telemetry, service history) and draft prognoses; a human maintenance lead reviews and posts them; the shop's findings close the loop. Three honesty rules run through everything: simulated data is always labeled, cost figures are estimates and never quotes, and nothing posts to the board without a human confirming it.
ROADTRUTH is paired with ROADWORTHY, its driver-readiness sibling. Vehicle data flows to the driver's app; only a 0–100 readiness aggregate flows back. Driver health never crosses the wall.
2. The Floor
The Floor is the fleet at a glance — one card per unit.
VHS gauge and status. Green ≥ 85 (NOMINAL), amber (WATCH / ADVISORY), red (FAULT). Scores on provider-mapped units are computed every 15 minutes by the engine; demo units carry labeled simulated data.
WHY THIS SCORE. Every computed score shows its arithmetic: starting from 100, each penalty is named with its evidence — open fault codes (14-day window), active prediction risk (max confidence × 30), telemetry freshness (−5 if no rows in 24h). Every computation is also stored with its full basis in an audit history.
LIVE ELD badge and channels. Partner-mapped units render their actual telemetry rows (refreshed every 60 seconds). A freshly imported unit shows "awaiting first telemetry window" until the next 15-minute ingestion pass.
Alerts. When a unit worsens, the alert appears on its card with delivery status (sent to WhatsApp, or logged).
ROADWORTHY strip. Paired units show driver readiness and Lane Readiness — the lower of driver readiness and vehicle health.
Active prognosis. The open prediction with its interval, confidence, and issuing Physician.
3. Clinical Rounds
Rounds is the floor's conversation: the Physicians walking the fleet, challenging each other's readings, answering the Adversary. Use ASK THE FLOOR ⚡ to put a question to the live AI channel — "what's the risk on LAG-07 this week?" — and the floor answers from the actual case files.
4. The Prover Board
The board is the platform's public record. Every prediction appears with its type, interval, and status:
Status
Meaning
PENDING
Posted; the interval clock is running.
CONFIRMED
The shop's findings matched the prediction.
MISS
The findings refuted it. Misses stay on the board — they train the engine.
The ninth agent, powered by Claude. RUN AI FORECAST on any unit produces a 90-day outlook: per-item risk, expected window, recommended action, and a cost range grounded in your fleet's own logged invoices — plus a quarterly maintenance budget figure. Every figure is marked ESTIMATE · NOT A QUOTE, and each item states its basis. The more service records the Office logs, the sharper the cost grounding becomes.
6. The Office
The Office is the fleet maintenance desk. Sign in with your work email (we email you a one-time link; there is no password). You see only the fleets your email belongs to. Owners and admins of a fleet can run every desk below for that fleet; viewers can look but not change anything.
Fleet Registry
Install from the Motive App Marketplace — the carrier's admin approves access on Motive's own consent screen, comes back to ROADTRUTH, signs in with email, and becomes the fleet's owner. Tokens rotate automatically and the carrier can revoke from their own dashboard.
CONNECT / RECONNECT — owners and admins can renew the connection from the Office at any time.
CONNECT A GEOTAB FLEET — Geotab fleets create a read-only service user in their own MyGeotab (People → Users → Add, Service account user profile, View Only clearance, data access at the top-level Company Group) and enter the database name, user and password here. ROADTRUTH checks it with Geotab, stores the password encrypted and never shows it again. UPDATE GEOTAB LOGIN takes a changed password; deleting the service user in MyGeotab withdraws access.
MEMBERS & ALERTS — add teammates by email as owner, admin or viewer; set the alert WhatsApp number; list the shop WhatsApp numbers allowed to report teardowns.
IMPORT UNITS — pulls the carrier's vehicle list from its provider and creates the units pre-mapped. They appear on the Floor immediately and score on the next ingestion pass.
Badges — OAUTH CONNECTED / SERVICE USER CONNECTED / TOKEN SET / NOT CONNECTED show each fleet's credential state.
PILOT REPORT — compiles the validation report (units, VHS trajectories, full prediction record with precision, alerts, logged spend) as downloadable markdown, per fleet or across all fleets.
Driver pairing
Enter the driver's DoktorConnect ID (DC-XXXX-XXXX) against a unit and PAIR. The driver's "My Truck" card and Lane readiness strip light up in ROADWORTHY on their next open.
Service records
LOG WORK after every job — description, parts, odometer, hours, cost, currency. This is the Forecaster's cost reference base: the fleet's own invoices become the pricing truth.
Prediction Desk
AI PROPOSE ⚡ — the Physicians read the unit's real case file and draft up to two candidates with rationale. Thin evidence produces fewer candidates or none; that restraint is deliberate.
Review and edit — take a draft with USE THIS DRAFT, or write your own; adjust confidence and interval.
POST TO BOARD — the prognosis goes to the Prover Board as PENDING with the next P-#### id. Nothing posts without this human step.
7. Connecting a carrier, end to end
The carrier installs ROADTRUTH from the Motive App Marketplace, approves access, and signs in with email; a Geotab carrier signs in and uses CONNECT A GEOTAB FLEET with its read-only service user (or DoktorConnect adds the fleet and invites the owner by email).
IMPORT UNITS — trucks land on the Floor, pre-mapped.
Within 15 minutes the ingestion pass writes telemetry and fault codes; the engine computes each unit's first VHS with its basis.
Pair drivers to units by DC-ID; the ROADWORTHY lane strip goes live.
Give the shop the WhatsApp reporting habit (next section). From here the platform runs itself: score → predict → alert → confirm.
No hardware is installed on any vehicle at any step. Access is read-only, scoped, and revocable by the carrier at any time.
8. WhatsApp shop reports
After a repair, the mechanic sends one short WhatsApp message to the fleet's ROADTRUTH number from a shop number the fleet has registered under MEMBERS & ALERTS (messages from other numbers are politely refused): the prediction id (or the unit), what was found, and whether it matched — a photo helps. The AI parses the message, matches it to the open prediction, and flips the board to CONFIRMED or MISS. Example:
P-0147 LAG-07 — opened the alternator, rectifier diode pair burnt exactly as predicted. Replaced. Confirmed.
Report the misses with the same energy as the wins. A miss on the board is the engine learning; a miss kept quiet is the engine lying.
9. Data & privacy
Machine data only. ROADTRUTH ingests vehicle stats, diagnostic fault codes, and locations. It holds no personal health information.
The one-way wall. Driver health lives in ROADWORTHY under DoktorConnect's health-privacy practices. A paired driver's readiness crosses into ROADTRUTH only as a band: READY, CHECK IN or REST.
Carrier separation. Each carrier sees only its own fleet. The browser never reads the database directly; every view is checked on the server against the signed-in account.
Credentials. Carrier tokens and OAuth credentials are stored server-side only and never reach a browser. OAuth tokens rotate automatically.
Revocation. A carrier can disable its token or revoke the OAuth grant in its own provider dashboard at any moment; pilot data is deleted or returned on request.
10. Troubleshooting & FAQ
You see
It means
"Awaiting first telemetry window"
The unit was just imported; the next 15-minute ingestion pass will populate it.
NOT CONNECTED on a fleet
The fleet has no credential yet. An owner or admin chooses CONNECT.
A score changed after a repair
Correct behavior — the engine recomputes from current evidence. Adjudicating a prediction removes its risk penalty on the next pass.
DEMO label on output
An honest fallback: the underlying service or table isn't configured yet, and the platform says so instead of inventing data.
"Not your fleet" or a read-only Office
Your email is not an owner or admin on that fleet. Ask the fleet's owner to add you under MEMBERS & ALERTS.
No sign-in email
Check spam, and open the link on the same device. Links expire after an hour.
AI PROPOSE returns nothing
The case file was too thin to justify a prediction. Wait for more telemetry or fault evidence.
11. Support
Josmol Group Inc. · Joseph@josmolgroup.com · 915-478-8807 · 4816 N. Mesa St, El Paso, TX 79912