An oversize load becomes a movement plan built to be legally defensible — every verdict carrying its statute, every gap named out loud.
Enter the load and two cities. Get per-state verdicts with citations, the permits and escorts required, fees at cost, an hour-by-hour schedule with the stops the law forces — and a readiness ladder saying exactly what still stands between the plan and a legal move. Point to point between any two US cities — or start from ten pre-authored corridors and adjust.
01 · The problem
Legal only inside the intersection of seven constraint sets.
Permit services file paperwork. Routing engines draw the route. Parking apps find a spot. ELDs count hours. Calculators price the permits and escorts — oversize.io and OSOWloads both compute a per-state intersection today, from $19–29/month. What none of them show you is the sentence the number came from. OSOWloads advertises "700+ state DOT documents and statutes" and cites not one of them: no statute number, no link, no per-answer attribution. Today the driver or the dispatcher is the integration layer — and the auditor of last resort, running it on phone calls and PDFs.
What the status quo costs
02 · The solution
Load + two cities → the plan.
Nothing on this card is authored. It is the engine's recorded answer for Cincinnati → Cleveland — verdicts, fees, hold and all — replayed from the repo's own contract fixtures, captured 2026-08-15. The numbers that are wrong on purpose (the fixture mileage, the fee ceiling) are printed in red, at the number.
Plan ready — not yet filable
Cincinnati, OH → Cleveland, OH · 150″W × 162″H × 636″L · 79,000 lb · non-divisible OH · PERMITEach block is a state's share of the fixture mileage, coloured by verdict. The red rule is where the law stops this truck: the Franklin County curfew holds it from 08:08 to 09:00.
“movement of all vehicles/loads in excess of twelve feet in width prohibited within the named counties between 6:30 a.m. and 9:00 a.m. and 4:30 p.m. and 6:00 p.m. Monday through Friday”
CORRIDOR_NOT_SURVEYED
No physical route survey exists and no machinery records one — the corridor is not a surveyed path, and no clearance, bridge or weight-posting data exists anywhere in this system. The route may be physically impossible for this load. The plan says so; the licensed OS/OW engine is the roadmap item that changes it.
03 · The demo
Real engine output. Captured, stamped, replayed.
The console plans any US city pair against the live engine — origin and destination as free text over a 31,523-place gazetteer, and a corridor built from our own graph, never a consumer routing API. What this page replays is three of those answers, recorded: a routine oversize width (Houston → Dallas), a metro curfew en route (Cincinnati → Cleveland), and an escort-tier load (Miami → Jacksonville). Every verdict, fee, citation and hold is the engine's own, from the repo's contract fixtures, captured 2026-08-15. The console itself is live — open it, type any pair point to point, or start from ten pre-authored corridors.
04 · Why it's right
Three rules the product cannot break.
The issued permit overrides the planner.
After issuance, the permit route is truth. Deviation handling is stop-and-amend, never silent reroute. A plan is a proposal; the permit is the legal document.
The deterministic engine is the only legal oracle.
Language models parse documents and draft sentences. They never decide whether your load is legal — that answer comes from rules a human can trace to a statute, with the citation attached.
Every datum cites its statute.
Source document, URL, retrieval date, effective date, verification tier — surfaced in every answer. Most also carry the operative sentence quoted verbatim; the ones that cite a document without quoting it are counted as such below, never smoothed over. Primary sources only; government fees at cost; no consumer routing APIs for OS/OW math.
Verification tiers — plainly
05 · The moat
A corpus competitors can copy the UI of — and nothing else.
The Turnpike doesn't take the state permit
236 miles of I-35/I-70/I-335/I-470 where the Kansas Turnpike Authority itself publishes that the KDOT permit is not required and its own narrower rules apply. A "state permit obtained" plan is wrong across Kansas's busiest corridor. Named, with a citation.
The rule was repealed; the conditions live in a PDF
Minnesota repealed its OS/OW rule in 2017. Limits and fees survived into statute; the operating conditions live in an unfiled agency PDF whose only version marker is a filename. Primary by every test, invisible to any register watcher.
Legal statewide, illegal through the tunnels
Colorado's legal height is 14′6″ — the tallest in the corpus — but the Eisenhower–Johnson tunnels bar anything over 13′11″. Legal statewide, illegal through the state's main east-west artery. Named, cited, not smoothed over.
Conflict register, measured 2026-09-02: 609 findings · 524 open — 161 permissive, 119 restrictive, 197 unknown, 47 structural — 85 resolved. Not a bug backlog: the corpus naming its own gaps with failure directions is what makes it auditable by an insurer or an acquirer. Four external code reviews (17, 9, 22, then 18 findings) — every finding reproduced before it was fixed, 54 of 66 closed, the remainder registered with failure directions.
06 · Market & buyer
The buyer is usually not the driver.
Segment by permitted-move frequency, not fleet size — two permitted loads a year is a different product from two a week. Drivers are critical users and veto stakeholders; the budget sits with the fleet owner, the ops or safety-compliance manager, the heavy-haul manager.
Owner-operators
Driver and buyer are the same person. Trigger: a costly delay, growing oversize volume.
Fleets
Owner / ops / safety-compliance hold the budget. Trigger: admin overload, inconsistent driver process.
Permit services
A buyer segment in their own right — the rules engine and dossier as their intake tool, not a competitor.
Brokers · 3PLs · insurers
Quoting OS/OW freight blind today; the dossier is the evidence package underwriting wants.
Three go-to-market paths, not one: driver-direct, fleet sales, and permit services as the third leg — which also reframes the routing-vendor conversation.
07 · Business model
Start free. Pay per move, per truck, or per corpus.
| 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 / diversified carrier | $15k–75k / year |
| Permit filing service fee | Carrier / permit service | $15–29 / jurisdiction |
| Superload coordination desk | Carrier / project customer | $1,500 / $3,500 / $7,500+ scope-gated |
| Rules-as-Code API | Third parties | $3k–15k / month |
Validation-stage pricing — structure with citations behind it, not yet field-tested by market research. Government fees pass through at cost — always, everywhere, never marked up; they are never inside the prices above, and permit filing is billed as its own service-fee line. Per-mile execution pricing is explicitly rejected: it punishes long simple moves, underprices short brutal ones, and buyers can't forecast it.
08 · Traction — what's real
Measured 2026-09-02. Nothing remembered.
Built and demonstrable
Not built — said plainly
The answer card on this page replays captured output, not a live engine. The console it was captured from is live.
09 · The ask
Three doors that move this from plan to permit.
Pilot carriers
Pilots with specialized carriers hauling real oversize lanes — real moves, real feedback, the corpus sharpened against your permits.
Routing licence
A signed ProMiles or Trimble OS/OW licence replaces the public-data graph with clearance-verified corridors.
Consultant engagement
The first consultant_signed data — the engagement letter that turns analyst-verified corpus into signed, defensible law.