One route file. One proof packet. One approval decision. Catalyst-Q gives freight teams a readable approval layer around the next route decision, with open-solver challenge rows and honest connector readiness.
CSV intake is live today. Customer-system access requires tenant approval, credentials, field mapping, and pilot validation before any TMS, API, webhook, telematics, or route-platform connector is used.
Every route recommendation must beat, match, or explain the dispatcher baseline, OR-Tools, PyVRP, VROOM, and relevant incumbent/API references before rollout.
The moat is not another route screen. It is the repeatable proof pipeline behind every approved or rejected change.
Runs candidate search, verification, objective deltas, hostile baselines, replay ids, and signed evidence without exposing simulator internals to the buyer.
Keeps tenant-scoped assumptions, accepted records, rejected recommendations, approval history, and recurring failure patterns available for the next review.
Turn route files into missing-data checks, reviewer briefs, approval packets, and follow-up actions so the record is repeatable instead of a one-off analysis.
The record is the product: a compact, exportable approval artifact that shows inputs, constraints, baselines, candidate deltas, risks, approval, rollback, replay, and signature.
Stable id for the decision under review.
Files, exports, fixtures, or APIs used to build the comparison.
Hard and soft constraints the recommendation must respect.
Dispatcher, heuristic, open-solver, or incumbent rows used as opposing evidence.
Catalyst-Q recommendation with metrics and reason codes.
Cost, distance, lateness, capacity, vehicle, fuel, or emissions proxy change vs baseline.
Operational risk movement, including route changes and rollback exposure.
Named approval state before any production operation changes.
How the customer returns to the incumbent plan if the candidate is rejected.
Replay handle for reproducing the evidence packet.
Digest or signed packet reference for tamper checks.
Buyer and reviewer output formats.
Catalyst-Q has to beat, match, or explain the alternatives before the pilot expands. No route changes should require faith in a black box.
Opposing solver floor. Catalyst-Q must beat, match, or explain this row before any rollout expansion.
Live in the Cloudflare benchmark container and returning feasible RouteOps comparison rows.
Opposing solver floor. Catalyst-Q must beat, match, or explain this row before any rollout expansion.
Live in the Cloudflare benchmark container and returning feasible RouteOps comparison rows.
Opposing solver floor. Catalyst-Q must beat, match, or explain this row before any rollout expansion.
Pinned VROOM CLI is live in the Cloudflare benchmark container and returning feasible RouteOps comparison rows.
The page is deliberately precise: live means live, planned means planned, and customer data access requires approved setup.
CSV intake is live today.
Freight CSV template and preview API validate the live intake surface.
API import/export is pilot-ready once customer fields are mapped.
Structured proof APIs exist; customer import mapping is completed during the paid pilot.
Webhook handoff is planned and pilot-scoped, not live.
Webhook delivery is a planned connector target after shadow-mode replay.
TMS mapping is customer-configured during the pilot.
Catalyst-Q can compare exported route files; each customer TMS mapping is configured during pilot onboarding.
Samsara is a planned connector target, not live.
Named as a connector target only.
Geotab is a planned connector target, not live.
Named as a connector target only.
OptimoRoute is planned and pilot-scoped, not live.
Named as a connector target and comparison reference only.
Route4Me is planned and pilot-scoped, not live.
Named as a connector target and comparison reference only.
Onfleet is planned and pilot-scoped, not live.
Named as a connector target and comparison reference only.
The onboarding motion minimizes buyer effort: start with a route file, replay history, then decide what deserves production integration.
Upload or export one route file with orders, vehicles, time windows, and the current plan.
Baseline replay packet with row counts, constraint coverage, and approval owner.
Choose CSV, TMS export, API import spec, or planned connector target for the pilot path.
Connector readiness record and field map.
Pick public or historical cases where dispatcher tradeoffs are painful.
Beat, match, or explain comparison packet.
Confirm accepted recommendations, rejected recommendations, and verified cost metrics.
Finance-ready pilot closeout packet.
Human-readable pages and machine-readable APIs point at the same proof surface.
Read the buyer-safe proof story and connector posture.
Open artifactInspect baseline rows, deltas, pricing offer, and open-solver gates.
Open artifactInspect signed benchmark evidence and replay ids.
Open artifactInspect the artifact-first technical review path.
Open artifactCompare evidence scope against competitors and open solvers.
Open artifactThis JSON is the buyer-agent readable manifest used by the well-known route and API.
{
"ok": true,
"routeops_proof_room": {
"id": "catalyst-q-routeops-hostile-proof-room-v1",
"vertical_id": "freight-field-routing",
"updated_at": "2026-05-31",
"positioning": {
"category": "RouteOps Decision-Proof Layer",
"summary": "Catalyst-Q works with your TMS, route tools, CSV exports, and dispatcher workflow to prove the next route decision before anyone changes operations.",
"claim_boundary": "Catalyst-Q is not a TMS replacement, dispatch system, driver app, telematics platform, ELD, or carrier visibility network. It produces a human approval proof packet around a route recommendation.",
"buyer_promise": "One route file. One proof packet. One approval decision."
},
"route_decision_record": {
"schema_version": "route-decision-record-v1",
"sample_record_id": "rdr-freight-routeops-mini-v1",
"required_fields": {
"record_id": {
"required": true,
"description": "Stable id for the decision under review.",
"example": "rdr-freight-routeops-mini-v1"
},
"input_sources": {
"required": true,
"description": "Files, exports, fixtures, or APIs used to build the comparison.",
"example": [
"orders.csv",
"vehicles.csv",
"dispatcher baseline export"
]
},
"constraints": {
"required": true,
"description": "Hard and soft constraints the recommendation must respect.",
"example": [
"capacity",
"time windows",
"driver hours",
"route stability"
]
},
"baselines": {
"required": true,
"description": "Dispatcher, heuristic, open-solver, or incumbent rows used as opposing evidence.",
"example": [
"dispatcher_baseline",
"nearest_neighbor_baseline",
"catalyst_routeops_v0"
]
},
"candidate_plan": {
"required": true,
"description": "Catalyst-Q recommendation with metrics and reason codes.",
"example": "catalyst_routeops_v0"
},
"objective_delta": {
"required": true,
"description": "Cost, distance, lateness, capacity, vehicle, fuel, or emissions proxy change vs baseline.",
"example": "42.206% objective improvement vs feasible heuristic baseline"
},
"risk_delta": {
"required": true,
"description": "Operational risk movement, including route changes and rollback exposure.",
"example": "2.5 route changes in urgent-order replan"
},
"human_approval": {
"required": true,
"description": "Named approval state before any production operation changes.",
"example": "dispatcher approval required"
},
"rollback_plan": {
"required": true,
"description": "How the customer returns to the incumbent plan if the candidate is rejected.",
"example": "retain current TMS route export as rollback baseline"
},
"replay_id": {
"required": true,
"description": "Replay handle for reproducing the evidence packet.",
"example": "routeops-replay-freight-mini-v1"
},
"signature": {
"required": true,
"description": "Digest or signed packet reference for tamper checks.",
"example": "9d0b7c6b3f92e2e0a4f8a6d15d052d9e42a4d7c3f2b8f051b58d38ab4a921b06"
},
"export_formats": {
"required": true,
"description": "Buyer and reviewer output formats.",
"example": [
"json",
"pdf",
"csv"
]
}
},
"export_formats": [
"json",
"pdf",
"csv"
],
"sample": {
"record_id": "rdr-freight-routeops-mini-v1",
"input_sources": [
"orders.csv",
"vehicles.csv",
"dispatcher baseline export"
],
"constraints": [
"capacity",
"time windows",
"driver hours",
"vehicle count",
"route stability"
],
"baselines": [
"dispatcher_baseline",
"nearest_neighbor_baseline",
"catalyst_routeops_v0"
],
"candidate_plan": "catalyst_routeops_v0",
"objective_delta": "42.206% objective improvement vs nearest-neighbor baseline",
"risk_delta": "Zero lateness, zero capacity violation, zero vehicle overage, bounded route changes.",
"human_approval": "pending dispatcher approval",
"rollback_plan": "Keep current TMS route export available until the dispatcher accepts the record.",
"replay_id": "routeops-replay-freight-mini-v1",
"signature": "9d0b7c6b3f92e2e0a4f8a6d15d052d9e42a4d7c3f2b8f051b58d38ab4a921b06"
}
},
"hostile_review": {
"open_solver_floor": [
{
"id": "ortools",
"name": "Google OR-Tools",
"role": "Opposing solver floor. Catalyst-Q must beat, match, or explain this row before any rollout expansion.",
"status": "remote_available",
"evidence": "Live in the Cloudflare benchmark container and returning feasible RouteOps comparison rows."
},
{
"id": "pyvrp",
"name": "PyVRP",
"role": "Opposing solver floor. Catalyst-Q must beat, match, or explain this row before any rollout expansion.",
"status": "remote_available",
"evidence": "Live in the Cloudflare benchmark container and returning feasible RouteOps comparison rows."
},
{
"id": "vroom",
"name": "VROOM",
"role": "Opposing solver floor. Catalyst-Q must beat, match, or explain this row before any rollout expansion.",
"status": "remote_available",
"evidence": "Pinned VROOM CLI is live in the Cloudflare benchmark container and returning feasible RouteOps comparison rows."
}
],
"reference_platforms": [
{
"name": "Descartes",
"category": "TMS and route execution incumbent",
"compare_on": "Production workflow depth, route execution, dispatch integrations, and proof packet export."
},
{
"name": "WorkWave",
"category": "Field-service routing incumbent",
"compare_on": "Planner workflow, mobile dispatch, customer notifications, and approval evidence."
},
{
"name": "OptimoRoute",
"category": "Route optimization SaaS",
"compare_on": "Route planning UX, driver workflows, import/export posture, and proof transparency."
},
{
"name": "Route4Me",
"category": "Route planning SaaS",
"compare_on": "Routing ergonomics, fleet operations workflow, and comparison evidence."
},
{
"name": "Onfleet",
"category": "Dispatch and delivery operations",
"compare_on": "Last-mile execution workflows, proof of delivery, and handoff evidence."
},
{
"name": "project44",
"category": "Visibility network",
"compare_on": "Exception visibility and accountability, not solver performance."
},
{
"name": "NextBillion",
"category": "Routing API reference",
"compare_on": "API expectations, solver outputs, constraint support, and exportable evidence."
},
{
"name": "GraphHopper",
"category": "Routing API/open engine reference",
"compare_on": "Routing primitives, optimization API expectations, and benchmark rows."
}
],
"promotion_gate": "Every route recommendation must beat, match, or explain the dispatcher baseline, OR-Tools, PyVRP, VROOM, and relevant incumbent/API references before rollout.",
"solver_superiority_claim_allowed": false
},
"connector_readiness": {
"overall_status": "csv_live_connectors_planned",
"claim_boundary": "CSV intake is live today. Customer-system access requires tenant approval, credentials, field mapping, and pilot validation before any TMS, API, webhook, telematics, or route-platform connector is used.",
"connectors": [
{
"id": "csv",
"label": "CSV intake",
"category": "file",
"status": "live",
"live_surface": [
"https://catalyst-q.strategic-innovations.ai/app?agent=freight-field-routing",
"https://catalyst-q.strategic-innovations.ai/v1/freight/csv/preview"
],
"setup_required": [
"orders CSV",
"vehicles CSV",
"time windows",
"capacity",
"driver hours"
],
"evidence": "Freight CSV template and preview API validate the live intake surface.",
"safe_claim": "CSV intake is live today."
},
{
"id": "generic_api",
"label": "Catalyst-Q API import spec",
"category": "api",
"status": "pilot_ready",
"live_surface": [
"https://catalyst-q.strategic-innovations.ai/v1/freight/proof-packet",
"https://catalyst-q.strategic-innovations.ai/v1/routeops-proof-room"
],
"setup_required": [
"tenant auth",
"field mapping",
"sample export replay",
"approval owner"
],
"evidence": "Structured proof APIs exist; customer import mapping is completed during the paid pilot.",
"safe_claim": "API import/export is pilot-ready once customer fields are mapped."
},
{
"id": "webhook",
"label": "Webhook handoff",
"category": "webhook",
"status": "planned",
"live_surface": [],
"setup_required": [
"target endpoint",
"secret rotation",
"retry policy",
"approval event mapping"
],
"evidence": "Webhook delivery is a planned connector target after shadow-mode replay.",
"safe_claim": "Webhook handoff is planned and pilot-scoped, not live."
},
{
"id": "tms",
"label": "Customer TMS export/import",
"category": "tms",
"status": "customer_config_required",
"live_surface": [],
"setup_required": [
"approved export",
"field map",
"rollback export",
"pilot validation"
],
"evidence": "Catalyst-Q can compare exported route files; each customer TMS mapping is configured during pilot onboarding.",
"safe_claim": "TMS mapping is customer-configured during the pilot."
},
{
"id": "samsara",
"label": "Samsara",
"category": "fleet_telematics",
"status": "planned",
"live_surface": [],
"setup_required": [
"customer authorization",
"API credentials",
"vehicle id mapping",
"telemetry validation"
],
"evidence": "Named as a connector target only.",
"safe_claim": "Samsara is a planned connector target, not live."
},
{
"id": "geotab",
"label": "Geotab",
"category": "fleet_telematics",
"status": "planned",
"live_surface": [],
"setup_required": [
"customer authorization",
"API credentials",
"vehicle id mapping",
"telemetry validation"
],
"evidence": "Named as a connector target only.",
"safe_claim": "Geotab is a planned connector target, not live."
},
{
"id": "optimoroute",
"label": "OptimoRoute",
"category": "routing_platform",
"status": "planned",
"live_surface": [],
"setup_required": [
"customer export",
"field map",
"comparison policy",
"pilot validation"
],
"evidence": "Named as a connector target and comparison reference only.",
"safe_claim": "OptimoRoute is planned and pilot-scoped, not live."
},
{
"id": "route4me",
"label": "Route4Me",
"category": "routing_platform",
"status": "planned",
"live_surface": [],
"setup_required": [
"customer export",
"field map",
"comparison policy",
"pilot validation"
],
"evidence": "Named as a connector target and comparison reference only.",
"safe_claim": "Route4Me is planned and pilot-scoped, not live."
},
{
"id": "onfleet",
"label": "Onfleet",
"category": "dispatch_platform",
"status": "planned",
"live_surface": [],
"setup_required": [
"customer export",
"field map",
"dispatch handoff policy",
"pilot validation"
],
"evidence": "Named as a connector target and comparison reference only.",
"safe_claim": "Onfleet is planned and pilot-scoped, not live."
}
]
},
"buyer_agent_artifacts": {
"llms_txt": "https://catalyst-q.strategic-innovations.ai/llms.txt",
"proof_schema_json": "https://catalyst-q.strategic-innovations.ai/.well-known/routeops-proof-room",
"routeops_proof_api": "https://catalyst-q.strategic-innovations.ai/v1/routeops-proof-room",
"canonical_pages": {
"proof_room": "https://catalyst-q.strategic-innovations.ai/routeops-proof-room",
"freight_proof": "https://catalyst-q.strategic-innovations.ai/freight/proof",
"benchmark_evidence": "https://catalyst-q.strategic-innovations.ai/benchmark-evidence",
"challenge_room": "https://catalyst-q.strategic-innovations.ai/challenge-room",
"competition": "https://catalyst-q.strategic-innovations.ai/competition",
"pricing": "https://catalyst-q.strategic-innovations.ai/pricing"
},
"canonical_apis": {
"routeops_proof_room": "https://catalyst-q.strategic-innovations.ai/v1/routeops-proof-room",
"freight_proof_packet": "https://catalyst-q.strategic-innovations.ai/v1/freight/proof-packet",
"freight_csv_preview": "https://catalyst-q.strategic-innovations.ai/v1/freight/csv/preview",
"benchmark_evidence": "https://catalyst-q.strategic-innovations.ai/v1/benchmark-evidence",
"challenge_room": "https://catalyst-q.strategic-innovations.ai/v1/challenge-room",
"competitive_benchmarks": "https://catalyst-q.strategic-innovations.ai/v1/competitive-benchmarks",
"sitemap": "https://catalyst-q.strategic-innovations.ai/v1/sitemap"
},
"evidence_urls": [
{
"label": "Human proof room",
"url": "https://catalyst-q.strategic-innovations.ai/routeops-proof-room",
"artifact_type": "page",
"reviewer_action": "Read the buyer-safe proof story and connector posture.",
"auth_required": false
},
{
"label": "Freight proof packet",
"url": "https://catalyst-q.strategic-innovations.ai/v1/freight/proof-packet",
"artifact_type": "json",
"reviewer_action": "Inspect baseline rows, deltas, pricing offer, and open-solver gates.",
"auth_required": false
},
{
"label": "Benchmark evidence",
"url": "https://catalyst-q.strategic-innovations.ai/benchmark-evidence",
"artifact_type": "page",
"reviewer_action": "Inspect signed benchmark evidence and replay ids.",
"auth_required": false
},
{
"label": "Challenge Room",
"url": "https://catalyst-q.strategic-innovations.ai/challenge-room",
"artifact_type": "page",
"reviewer_action": "Inspect the artifact-first technical review path.",
"auth_required": false
},
{
"label": "Competitive benchmarks",
"url": "https://catalyst-q.strategic-innovations.ai/v1/competitive-benchmarks",
"artifact_type": "json",
"reviewer_action": "Compare evidence scope against competitors and open solvers.",
"auth_required": false
}
],
"allowed_claims": [
"Route decision proof packet",
"baseline-vs-candidate evidence",
"human-approved route recommendation",
"open-solver comparison gate",
"CSV intake is live today"
],
"gated_claims": [
"solver superiority requires public OR-Tools, PyVRP, VROOM, Solomon, CVRPLIB, and customer shadow-mode evidence",
"third-party connector availability requires tenant approval, credentials, field mapping, and pilot validation"
],
"blocked_claims": [
"best route optimizer",
"TMS replacement",
"autonomous dispatch",
"live Samsara integration",
"live Geotab integration",
"solver superiority"
]
},
"first_30_days": [
{
"day_range": "1-3",
"goal": "shadow-mode baseline replay",
"user_action": "Upload or export one route file with orders, vehicles, time windows, and the current plan.",
"catalyst_action": "Validate the file, build the dispatcher baseline, and create the first Route Decision Record.",
"output": "Baseline replay packet with row counts, constraint coverage, and approval owner."
},
{
"day_range": "4-10",
"goal": "connector overlay without overclaiming",
"user_action": "Choose CSV, TMS export, API import spec, or planned connector target for the pilot path.",
"catalyst_action": "Map fields, document credentials required, and keep third-party connectors marked planned until validated.",
"output": "Connector readiness record and field map."
},
{
"day_range": "11-20",
"goal": "hostile solver review",
"user_action": "Pick public or historical cases where dispatcher tradeoffs are painful.",
"catalyst_action": "Run dispatcher, heuristic, OR-Tools, PyVRP, VROOM, and Catalyst-Q rows where available.",
"output": "Beat, match, or explain comparison packet."
},
{
"day_range": "21-30",
"goal": "CFO ROI packet",
"user_action": "Confirm accepted recommendations, rejected recommendations, and verified cost metrics.",
"catalyst_action": "Summarize savings, risk deltas, adoption, rollback evidence, and expansion gates.",
"output": "Finance-ready pilot closeout packet."
}
],
"pricing_signal": {
"paid_pilot": "$15,000-$35,000 for 4-6 weeks",
"conversion": "$2,500-$7,500/month + usage + verified savings kicker",
"acceptance_metric": "mileage, lateness, capacity, route stability, fuel/emissions proxy, and dispatcher acceptance against baseline"
}
}
}