# Pilot readiness — first carrier, internal shared workspace (2026-10-01)

Scope: Carrier Dispatch (CD) and Carrier Driver (CT) interfaces, used by dispatchers, a Permitting Manager, Safety Officers and drivers. Stripe, paid routes, card on file and online permit ordering are excluded.

## How to read this

- **READY** deployed and proven by production records. **PARTIAL** works with limits. **NOT READY** missing or not functional. **NOT TESTED** exists, not verified on the deployed site.
- "Deployed" means `heavyhaulgbt.com`, which runs GitHub `origin/main` (commit `bd2a17f`). My 13 newest commits are on this Mac only and are not deployed.
- I could not sign in to the deployed site. Its login now has a security verification (reCAPTCHA) that rejects automated browsers, and I must not bypass it. Evidence below therefore comes from the production database (read-only), the deployed code, and local runs against the production database. Nothing here was clicked through on the deployed site by me, and nothing was tested on a real phone.
- Production today holds 3 trips, 12 permits, 0 chat messages, 0 alert rows, 0 Auto-Participant rules. Most features have never been exercised there.

## 1. Carrier Dispatcher Workspace

| # | Status | Answer | Blocks pilot? | Fix time |
|---|---|---|---|---|
| 1 | PARTIAL | Permits are optional at creation. A rate confirmation, origin, destination and commodity are required. Not clicked through on the deployed site. | No, unless they have trips with no rate con | Make rate con optional: 2 h |
| 2 | READY | Trips persist; permits and documents are added later from the trip's Docs tab. HH-779270157 received a fifth and sixth permit hours after creation. | No | — |
| 3 | PARTIAL | Several dispatchers can be on one trip, but a dispatcher cannot invite another dispatcher (invite rules allow driver, pilot, broker only). The only way in is a Company Auto-Participant rule, which applies to future trips only. | Yes | 2–3 h to let a carrier dispatcher add office colleagues |
| 4 | PARTIAL | Yes when the Permitting Manager is on the trip, with full dispatcher powers. They get on the trip only through a company Auto-Participant rule. | No, if rules are set before the first trip | — |
| 5 | PARTIAL | Yes for trips created after the company rule exists. Older trips are not back-filled. | No, if rules are set first | Back-fill button: 3–4 h |
| 6 | NOT TESTED | Deployed and verified locally against the production database with marked demo records (since removed). Zero rules exist in production. | Yes, must be proven once on the deployed site | 1 h test |
| 7 | NOT TESTED | By design yes: a company rule fires whenever any approved member of that company joins a trip, whoever created it. The person named in the rule must accept the request first. | Same as 6 | — |
| 8 | PARTIAL | Yes when a member of the carrier (a dispatcher) joins the broker's trip. Assigning the carrier company alone, with no person, adds nobody. | No | — |
| 9 | NOT READY | No company-wide trip list. Each person sees only trips they are a participant on. | No, if Auto-Participants works. Wanted by Safety. | 1.5–2 days |
| 10 | PARTIAL | A dispatcher can edit the trip, add permits and documents, invite and remove drivers, pilots and brokers. Cannot add office colleagues (see 3). | See 3 | — |

## 2. Permit Uploading and Shared Documents

| # | Status | Answer | Blocks pilot? | Fix time |
|---|---|---|---|---|
| 11 | READY | HH-779270157 holds NM, LA, MS, AL, IL on one trip. | No | — |
| 12 | READY | State was read on 11 of 11 processed permits. | No | — |
| 13 | PARTIAL | Any participant can open and download every permit on the trip. Not tested with these two roles on the deployed site. | No | — |
| 14 | PARTIAL | Visible to all participants with no sharing step. Other people's open screens do not refresh by themselves; they see it on the next page load. Nobody is notified. | No | Live refresh: 3–4 h |
| 15 | NOT READY | No replace action. A corrected permit is uploaded as a second permit for the same state; the old one stays. Nothing is deleted, so history exists, but nothing marks which one is current. | No | 1 day |
| 16 | PARTIAL | Office roles can upload supporting documents. Drivers have no upload control in the driver app. | No | See 28 |
| 17 | READY | The file is stored before it is read. HH-779270157 has a permit whose reading failed and whose PDF is still attached. | No | — |
| 18 | PARTIAL | No known case of a document vanishing alone or attaching to the wrong trip. Whole trips have disappeared (see 75), which takes their documents with them. | Yes, via 75 | — |

## 3. Driver Experience — Mobile

| # | Status | Answer | Blocks pilot? | Fix time |
|---|---|---|---|---|
| 19 | READY | Dispatcher adds the driver by email (phone is also required) in the wizard or the People tab. | No | — |
| 20 | NOT READY | No invitation email is sent. The dispatcher copies a link and sends it by text or email. | Yes | 0.5 day |
| 21 | NOT TESTED | Unproven. The sign-up form only records a request, and email-code sign-in works only for people who already have a profile. Google sign-up was deployed today by the other developer and is untested. A driver with no account may not be able to get in. | Yes | 0.5–1 day to test and close gaps |
| 22 | NOT TESTED | A dedicated driver app exists (`/ct-dashboard`, driver trip view). Never opened on a real phone. | Yes | 0.5 day with real devices |
| 23 | PARTIAL | Driver sees all permits. Supporting documents and the rate con are not listed in the driver app. | No | 3–4 h |
| 24 | NOT TESTED | "View permit" opens the PDF in the phone's viewer. Zoom and download depend on the phone. | Yes | Part of 22 |
| 25 | PARTIAL | Yes on next load or refresh. No push to an open screen, no notification. | No | — |
| 26 | NOT TESTED | Built and connected to the AI backend. Production has zero chat messages, so it has never been used there. | Yes | 1 h test |
| 27 | PARTIAL | Driver and office share one trip thread. It is an AI thread (see section 4). | See 31 | — |
| 28 | NOT READY | No upload or photo control in the driver app. Permission rules already allow it. | No | 0.5 day |
| 29 | NOT TESTED | Assignments are stored against the account, so they should persist. Not verified. | Yes | Part of 22 |

## 4. Shared Chat

| # | Status | Answer |
|---|---|---|
| 30 | PARTIAL | One thread per trip, visible to every participant. A sender can mark their own messages private. |
| 31 | NOT READY | Every message typed in the screen is sent to the AI and gets an AI reply. |
| 32 | NOT READY | Same. |
| 33 | NOT READY | They can type, but the AI answers too. |
| 34 | Yes | This is exactly what the chat is today: a shared AI conversation where participants see each other's questions and answers. |
| 35 | PARTIAL | The server already accepts a plain message with no AI reply. No screen uses it. |
| 36 | NOT READY | No attachments or document references in messages. |
| 37 | READY (by code) | Screens poll every 4 seconds. Not observed on the deployed site. |
| 38 | READY (by code) | Messages are stored against the trip. Zero exist in production. |
| 39 | READY (by code) | Dispatcher and driver screens read the same thread. |
| 40 | NOT READY | No email, in-app or push notification for chat. |
| 41 | — | 0.5–1 day: add "Message team" and "Ask AI" send modes to the dispatcher trip view and the driver app using the existing plain-message path, show who wrote each message, test with two accounts. Attachments are a further 1 day. Chat notifications a further 1 day. |

Blocks pilot: yes for 31–33 if the customer expects to talk to drivers inside HHA.

## 5. Permit Alerts and AI

| # | Status | Answer | Blocks pilot? | Fix time |
|---|---|---|---|---|
| 42 | PARTIAL | 11 permits read successfully. 2 are stuck waiting for a retry that never runs (see 80). | Yes | See 80 |
| 43 | PARTIAL | Of 11: length 11, weight 11, width 10, height 10. Values were not checked for accuracy against the paper permits. | No | Accuracy check: 2 h with real permits |
| 44 | PARTIAL | The comparison exists and is unit-tested (permit smaller than trip, per dimension). It is switched off. | Yes | See 45 |
| 45 | NOT READY | Still off. The production setting `WORKSPACE_DIMENSION_ALERTS_ENABLED` is not set. | Yes | 15 min to switch on, 1 h to test |
| 46 | NOT READY | The code checks expiry when a permit is read. In production it has stored nothing: the SC permit on active trip HH-201297026 expired 2026-02-03 and has no alert. | Yes | 0.5–1 day, cause not yet found |
| 47 | NOT READY | Same failure. LA (expires Oct 2) and MS (expires Oct 3) on HH-779270157 should each carry an "expiring" alert. Neither does. The window is 3 days. | Yes | Same fix |
| 48 | NOT READY | No cross-state or cross-document conflict detection. | No | 1–2 days |
| 49 | NOT READY | Structured curfews, restrictions and escorts: 0 of 11 permits. Available only by asking the AI. | No, but see next line | Backend work, not estimated |
| 49b | NOT READY | The dashboard "Curfew" and "Escort" columns and the driver's per-state checks show "Clear" / "No curfew recorded" for every trip because nothing feeds them. A Safety Officer will read that as verified. | Yes | 2–3 h to hide or relabel |
| 50 | NOT TESTED | Sources are shown when the AI backend returns them. | No | 1 h test |
| 51 | NOT TESTED | A confidence badge is shown on answers. | No | Same test |
| 52 | PARTIAL | Alerts show to every participant on the trip, driver included. None exist to show. | Via 46 | — |
| 53 | PARTIAL | Evaluated when the permit is read and when dimensions or a permit are edited. Results are not being saved (46). | Via 46 | — |
| 54 | NOT READY | No daily re-check. A permit valid on upload never turns "expired" later. | Yes | 0.5 day |
| 55 | NOT READY | No company alert page. Each person's dashboard flags only their own trips. | No | 1 day |
| 56 | PARTIAL | "Acknowledge" hides an alert for that one person on that one browser. The team cannot see that someone handled it. | No | 0.5 day |

**57. Alert types**

| Alert | State |
|---|---|
| Permit dimension smaller than trip (width, height, length, weight) | Built, switched off |
| Permit expired | Built, not being saved in production |
| Permit expiring within 3 days | Built, not being saved in production |
| Second valid permit for the same state suppresses the expiry alert | Built |
| Daily expiry re-check | Not available |
| Curfew, travel-time restriction | Not available |
| Escort requirement | Not available |
| Conflicts between states or documents | Not available |
| Missing permit for a state on the route | Not available |
| Permit not yet effective | Not available |

## 6. Notifications

| # | Status | Answer |
|---|---|---|
| 58 | PARTIAL | Only people added by an Auto-Participant rule get an "you were added" email. Nobody else is notified. |
| 59 | NOT READY | No. Manual link. |
| 60 | NOT READY | No notification on upload. Replace does not exist. |
| 61 | NOT READY | A dimension email exists but is switched off with the alerts. It goes to trip participants, not to a Safety role specifically. |
| 62 | NOT READY | No expiry email. |
| 63 | NOT READY | No chat notification. |
| 64 | NOT READY | No notification or alert feed. |
| 65 | — | Email only: sign-in codes, company relationship emails, Auto-Participant request and "added" emails. No in-app, push or SMS. |
| 66 | NOT TESTED | A preferences page exists and the sender honours categories. Security emails cannot be turned off. |
| 67 | — | Dimension alert emails are disabled by configuration. |

Blocks pilot: 59 yes. 62 yes for a safety pilot (0.5 day once 46 and 54 are fixed). The rest can follow.

## 7. Company Roles and Access

| # | Status | Answer |
|---|---|---|
| 68 | PARTIAL | Yes, through company Auto-Participants. Not by one dispatcher adding another (see 3). |
| 69 | PARTIAL | They do not need Company Admin. An admin creates one company rule and they join every future trip. There is no all-trips view, and they hold dispatcher powers. |
| 70 | NOT READY | Safety Manager is a company role, but on a trip it has full dispatcher powers. No read-only level. Blocks only if the customer insists on read-only. 1 day. |
| 71 | — | Each participant row already records the person's company role for that trip (`context_role_type`). Capabilities can be reduced by that value without adding a new trip role. |
| 72 | NOT TESTED | Yes, Company Admin manages company rules on the Auto-Participants settings page. Zero rules in production. |
| 73 | PARTIAL | Yes when a company member joins the trip. Not when only the company name is attached. |
| 74 | PARTIAL | Every trip page and API checks that the signed-in person is a participant, and trip numbers are random. One gap: an invitation link works for whoever opens it while signed in; it is not tied to the invited email. Blocks pilot. 2–3 h. |

## 8. Stability

| # | Status | Answer |
|---|---|---|
| 75 | NOT READY | No. Nothing in the app deletes trips. Only two maintenance scripts can. Who or what ran is unknown, and deletes leave no record. |
| 76 | NOT TESTED | The trips I know were lost were test and demo trips. I cannot prove no real trip was lost, and nothing has been fixed. |
| 77 | NOT READY | No. 13 commits are local only. GitHub has 1 commit from the other developer that I do not have. Awaiting your go-ahead to merge and push. |
| 78 | NOT READY | No. Two files are numbered 0049. Both are already applied in the database, so this is a rename, done with the merge. |
| 79 | NOT READY (deployed) | The deployed build still shows the fake pilot contact and demo figures. The fix is in the local commits. Production also holds 2 test trips, 2 mock purchases, 11 test logins and about 12 test companies, awaiting your decision. |
| 80 | NOT READY | No. Two permits have been waiting for retry since Sep 28 and Oct 1. |
| 81 | NOT READY | No real-device testing. |
| 82 | NOT TESTED | Depends on the Supabase plan. No restore has been tested. |
| 83 | — | Yes: the unexplained trip deletion; any trip delete silently removes its documents, messages and participants; no audit of deletes. |

## 9. End-to-end demonstration

Not performed. The deployed login rejected my automated browser ("Security verification failed"), and step 12 needs a real phone. Steps 16–17 (normal messages), 19 (dimension alert, switched off) and 20 (expired alert, not saved) would fail today regardless. I can run steps 1–11, 14–15, 18 and 21–23 locally against the production database after the fixes, and you or a tester would repeat them on the deployed site and on phones using a checklist I prepare.

## 10. Final Readiness Report

1. **Usable today as a reliable shared permit workspace?** No. Storing and reading permits works. Alerts, onboarding, colleague access and stability are not at a level for a real customer.
2. **Chat sufficient?** No. It is a shared AI thread. Human-to-human messaging needs 0.5–1 day.
3. **Alerts that work today?** None in production. Dimension alerts are off; expiry alerts are computed but not stored.
4. **What Safety and Permitting see company-wide?** Only trips they are participants on. With a company rule they are added to every future trip. No company list, no company alert page.
5. **Notifications missing?** Driver invitation, permit upload, expiry, dimension mismatch (off), chat message, and any in-app feed.
6. **Missing from the driver app?** Document and photo upload, supporting documents list, normal messaging, notifications, real-phone verification.
7. and 8. Blockers and time below.

### Mandatory before real customer access

| # | Blocker | Current evidence | Remaining task | Estimate |
|---|---|---|---|---|
| B1 | Local fixes not deployed | 13 local commits, 1 remote commit, duplicate 0049 | Merge, rename migration, test, push, deploy | 0.5 day |
| B2 | Fake pilot contact on deployed site | Fixed locally only | Ships with B1 | — |
| B3 | Purchase buttons would appear for this customer after B1 | Route locking is in the local commits | Pilot switch that hides route purchasing and Billing for this carrier | 2–4 h |
| B4 | Expiry alerts not saved | 3 expected alerts, 0 stored | Find cause, fix, back-fill existing permits | 0.5–1 day |
| B5 | No daily expiry re-check | No scheduled job | Daily job plus expiry email to dispatcher and permit manager | 0.5–1 day |
| B6 | Dimension alerts off | Setting unset | Switch on, test one mismatch | 1–2 h |
| B7 | "Clear" shown for curfew and escort with no data | Columns fed by nothing | Hide or relabel "Not checked" | 2–3 h |
| B8 | Dispatcher cannot add office colleagues | Invite rules | Allow it for carrier office roles | 2–3 h |
| B9 | No invitation email; link not tied to email | Code | Send email on invite; check email on accept | 0.5–1 day |
| B10 | Account creation for staff and drivers unproven | Sign-up records a request only | Test invite-to-first-login for a brand-new person; close gaps | 0.5–1 day |
| B11 | Human-to-human chat | UI always calls AI | Two send modes in dispatcher view and driver app | 0.5–1 day |
| B12 | Retry worker not running | 2 jobs stuck | Schedule the every-minute job on the server | 1–2 h, needs server access |
| B13 | Trip deletions unexplained, backups unverified | No delete audit | Record every delete in the database, lock the two scripts, confirm backups and do one test restore | 0.5 day |
| B14 | Never run on the deployed site or on phones | 0 chat messages, 0 rules, 0 alerts in production | Section 9 on the deployed site, iPhone and Android | 0.5–1 day |
| B15 | Test records in production | 2 trips, 2 mock purchases, 11 logins, ~12 companies | Your decision, then removal | 1 h |

**Total: about 5 to 7 working days**, plus your decisions on B3 and B15 and server access for B12.

### Can follow while the carrier is testing

| Improvement | Estimate |
|---|---|
| Company-wide trips list for admins, Safety, Permitting | 1.5–2 days |
| Company alert page with shared acknowledge and resolve | 1.5 days |
| Read-only capability for Safety | 1 day |
| Back-fill Auto-Participants onto existing trips | 3–4 h |
| Permit replace with marked history | 1 day |
| Driver upload of documents and photos; supporting documents in driver app | 1 day |
| Notifications for upload and chat; in-app feed | 2–3 days |
| Chat attachments | 1 day |
| Cross-state conflict detection | 1–2 days |
| Structured curfew, restriction and escort extraction and alerts | Backend developer, not estimated |
| Make rate confirmation optional at trip creation | 2 h |
