For the HHA Brain CTO · From the HHA Workspace CTO

For the HHA Brain CTO — From the HHA Workspace CTO — October 15, 2026, 10:12 AM ET — Questions and decisions

Name and address. The HeavyHaul Factory is now called the Brain and moves to its own subdomain, brain.heavyhaulagent.com. The Workspace moves to heavyhaulagent.com.

Short answer to W1: yes. Every Workspace path that imports or displays Synchron route text handles both the new 3-line list and the old single string. No pushed Synchron order failed or showed bracketed text since October 12. From the Workspace side, B1 does not need to be paused.

1. The Workspace's answers

W1 — Yes. Every Workspace path handles both the 3-line list and the single string. Nothing on the Workspace side needs B1 paused.

PathHandles list and string?Why
Synchron order import (the import scripts used for the 957 Synchron trips and the developer's backfill)Yes, unaffectedIt never reads route text. From each route it reads only the map link (route_url) and the approval status.
Synchron order messages to /api/webhooks/synchron (order.created, permit.attached)Yes, unaffectedThese messages carry no route text.
The Brain's permit reading (route_texts in states_info)Yessrc/lib/adapters/flask.ts accepts a list (joined into one line), an object (routing_from, routing_to, via) and a single string. A list and an object are covered by tests.
ScreensYes, unaffectedNo Workspace screen displays Synchron's route text. The route description exists only inside the stored reading.
Trip copy sent to the BrainYes, unaffectedIt sends Workspace records and doesn't carry Synchron route text.

Why

Checked in the code and in production today. This is the answer to Nash's condition 3 for B1 on the Workspace side.

Since October 12: no failed imports and no bracketed text.

No Synchron order reached the Workspace since October 12 (0 trips created or updated, 0 Synchron documents), so nothing could fail to import. One permit was uploaded in the Workspace on October 13; its reading failed with "extraction unavailable", unrelated to route text. Across all 3,819 stored permit readings, none contains a route description in list form with brackets.

Why

Read-only checks of the production database today.

One small safety fix will be added on the Workspace side.

If the list ever arrives as a single string that looks like a list (for example "[\"Houston, TX\", \"Dallas, TX\", \"I-45 N\"]"), the reader would keep it as-is and the brackets would show. This hasn't happened in any stored reading. The Workspace will parse such a string as a list. It is about 30 minutes of work for the Workspace developer and is being added to his task list.

Why

It closes the only way the new format could show wrongly in the Workspace, without waiting to see it happen.

For your information: five trip-copy calls to the Brain failed on October 13–14.

Workspace to Brain trip sync failed on October 13 at about 11:42 AM ET, and four times on October 14 between about 3:29 and 3:30 AM ET. Each failed with an error status and no error code. The Workspace retries trip sync, so no data is lost, but the cause is on the Brain side of the call.

Why

These fall in the days B1 and the Brain deployment were happening, so they may help you confirm the deploy time (question 2).

2. Questions for the Brain CTO

Please type each answer in its box, then save the page or print it to PDF and send it back.

  1. Could you resend your October 13, 8:43 AM ET letter (items W2–W5)?

    Why we askThis file says W2–W5 of that letter are still open, but the Workspace CTO never received it, so they haven't been answered.

    What we are trying to understandWhich questions W2–W5 are, so the Workspace can answer them in its next file.

    The HHA Brain CTO — answer to question 1
  2. Can the Brain check what refused the five trip-copy calls (October 13, about 11:42 AM ET; October 14, about 3:29–3:30 AM ET)?

    Why we askThey failed with no error code, and they fall in the days of the B1 deployment.

    What we are trying to understandWhether they were caused by the deploy, by B1, or by something else, and whether the Brain needs anything changed in the trip copy.

    The HHA Brain CTO — answer to question 2
  3. Does the Brain ever send route_texts to the Workspace as a single string that contains the list?

    Why we askThe Workspace handles a real list, an object and a plain string. The safety fix above covers a list written into a string.

    What we are trying to understandWhether that case can happen today, or the fix is only a precaution.

    The HHA Brain CTO — answer to question 3