SkyeRouteX is the dispatch room. I wanted a place where a provider can post work, route contractors, freeze payment state, capture proof, and export an audit packet without duct tape.
Workforce dispatch · 🛻 pain first
SkyeRouteX
Workforce operations break when jobs, contractors, stops, proof, payments, and disputes live in different tools.
Founder note
Why Gray built this lane.
What it does
The practical operating layer.
Provider job board
This is not a brochure bullet. In the 0S, SkyeRouteX has to connect the user action to a route, a session, a receipt, or a handoff so the work can be trusted later.
Contractor routes and assignments
This is not a brochure bullet. In the 0S, SkyeRouteX has to connect the user action to a route, a session, a receipt, or a handoff so the work can be trusted later.
Payment-state ledger
This is not a brochure bullet. In the 0S, SkyeRouteX has to connect the user action to a route, a session, a receipt, or a handoff so the work can be trusted later.
Audit packets and House Command
This is not a brochure bullet. In the 0S, SkyeRouteX has to connect the user action to a route, a session, a receipt, or a handoff so the work can be trusted later.
Competitor stack
How it stacks up without lying.
The comparison is category-level on purpose. Specialist tools are not bad; they are often excellent at the narrow job. The 0S argument is ownership, proof, shared auth, payment activation, and cross-lane context.
| Jobber / Housecall Pro | Strong field-service tools. SkyeRouteX is broader workforce dispatch inside the 0S. |
|---|---|
| Uber-style dispatch apps | Purpose-built marketplaces. RouteX is operator-owned. |
| Spreadsheets/texts | Common but brittle. RouteX creates proof. |
Truth ledger
What we can say out loud.
✅ Runs as part of the 0S operating model, not as a loose side project.
✅ Uses the shared FS27/SkyGate/Free99 gate posture when mounted into the 0S.
✅ Needs proof receipts, owner visibility, and cost boundaries before it is sold as unlimited.
✅ Can be positioned strongly without pretending third-party primitives do not exist behind the scenes.
✅ Payment movement requires owner/provider gates.
✅ Concurrency locks must prefer 409 conflicts over over-assignment.
✅ Dispatch proof is a product, not a nice-to-have.
Proof and receipts
What backs the page.
🧾 Worker parity proof
SkyeRouteX is marketed as part of a receipt-driven system. The proof may be a live route, a worker test, a browser proof, a stress run, or a platform truth file.
🧾 Concurrency stress proof
SkyeRouteX is marketed as part of a receipt-driven system. The proof may be a live route, a worker test, a browser proof, a stress run, or a platform truth file.
🧾 Browser/E2E checks
SkyeRouteX is marketed as part of a receipt-driven system. The proof may be a live route, a worker test, a browser proof, a stress run, or a platform truth file.
🧾 SkyePay product lane
SkyeRouteX is marketed as part of a receipt-driven system. The proof may be a live route, a worker test, a browser proof, a stress run, or a platform truth file.