HaulPilot console — proposal, not a permit

Offer	Buyer	Price
Free feasibility	Anyone	$0 — unlimited
Per-move	Occasional OS/OW owner-operator	$39 / move
Solo / Pro subscription	Frequent OS/OW owner-operator	$99–199 / month
Small fleet platform	Fleet owner	$999–1,499 + $49 / truck
Enterprise	Specialized carrier	$15k–75k / year
Permit filing service fee	Carrier / permit service	$15–29 / jurisdiction
Superload coordination desk	Project customer	$1,500 / $3,500 / $7,500+, scope-gated
Rules-as-Code API	Third parties	$3k–15k / month

Load feed — the board, screened

Every posting goes through the same engine this console asks for a plan — parsed dimensions, legality, fees, the calendar days the law forces — and the list is ordered by what the move clears per day, not by the rate printed on it. Loads that cannot be screened or cannot be priced are shown in their own groups with the reason, never mixed in and never dropped.

Compliance calendar

The obligations that arrive whether or not a truck moves — registrations, returns and renewals with statutory deadlines, each carrying the sentence it came from. A fact left unstated comes back undetermined, naming the input, because an obligation left off a calendar looks exactly like one already satisfied.

Corpus status

Every verdict on this board carries the verification tier of the data behind it, and the coverage gaps are printed on the rows they affect — no coverage and not in corpus are answers here, never blanks. The counts live where they are computed, in the repository’s own gates, not on this page where they would go stale.

Verification tiers — plainly

unverified means dev/test only, and any answer built on it is flagged. analyst_verified means an AI analyst re-derived the datum from the primary document — it is not a human consultant’s signature. No datum has reached consultant_signed, so nothing here reads better than plan only, and that gate closes with an engagement letter, not more encoding.

The move

Origin

Destination

Type two letters of any US city and pick it from the list. The names people write work as well as the ones the Census files — Boise, Nashville, St Louis — and the page says which record answered.

Or start from a known corridor

Loading the corridors the routing port can answer for…

Paste a load posting

Deterministic extraction, no AI: a number is proposed only when an explicit label or weight unit names its field and the conversion is exact. Everything else is shown below, never filled in.

Width (in)

Height (in)

Length (in)

Gross wt (lb)

Front OH (in)

Rear OH (in)

Depart (local)

Non-divisible load

Securement (min)

392.9 recheck (min)

Parking buffer (min)

Every dimension is an integer — inches and pounds, never floats. The engine rejects a fractional inch at the boundary so it can never become a rounding argument at a permit counter. The three budgets are YOUR estimates, in whole minutes — zero means not modelled, never "takes no time". Where the securement rechecks fall is 49 CFR 392.9 and the plan cites it; how long they take is whatever you declare here. There is no weather field: a contingency invented without a forecast feed would be fiction, and the timeline names the zero instead.

Economics — advisory

Offered rate (all-in $)

Escort day rate ($/day)

Type the all-in rate you were offered and the answer gains a net-of-compliance panel — advisory arithmetic over this plan's own fees, escorts and calendar days, never a legality answer. Dollars and cents, two decimals at most, no negatives; whole dollars are fine. The escort day rate is your number, echoed into the answer — this system never suggests one. There is no per-mile rate field: this system's mileage is an upper bound, and multiplying an offer across it would inflate revenue.

Compliance calendar

The obligations that arrive whether or not a truck moves — registrations, returns and renewals with statutory deadlines. Everything below is computed by the same engine that answers the legality questions, from primary documents, and every line carries the sentence it came from. Nothing here files or pays anything.

As of

Horizon (days)

Base jurisdiction

Loading the credentials the corpus holds…

Leave a fact blank to see what the engine does with it: an unstated weight or filing frequency comes back undetermined, naming the input, rather than being quietly decided. That is the whole point — an obligation left off a calendar looks exactly like one already satisfied.

09:41LTE ▾ ▮

The same answer, compressed to the wheel. This card is the plan the planner holds — not a second computation — cut down to what a driver needs while moving: the next place the law stops the truck, the days, the fees, and the dossier hash that lets a scale house verify the full document offline.

Same palette, same words as the planner, on purpose: an operator should not have to learn two screens. Change the lane or the load on the planner and this card follows; when the planner holds a refusal, this card holds nothing rather than an older answer.

Nothing on it is authored — every figure is the engine’s, and the one sentence that is always true stays printed at the top: a plan is a proposal, and the issued permit overrides it.

Jurisdictions encoded	49 — the contiguous 48 + DC, complete
Provenance-carrying rule data	802, each citing a primary document by name, URL and retrieval date — of which 665 quote the sentence and 137 cite a document without a quoted span
Verification tier	794 analyst_verified · 8 unverified · 0 consultant_signed
Routable places	31,523 — US Census gazetteer, committed
Conflict register	551 findings · 488 open — 446 carry a failure direction, 42 are structural entries where a direction does not apply
CI quality gates	16, every one green on Ubuntu
External code reviews	3 (17, then 9, then 22 findings) — each reproduced before it was fixed, all closed

HaulPilot — for investors

The ask — three doors

What is real

What is not built — said plainly

Business model

Why the register is an asset

Load feed — the board, screened

Compliance calendar