Catalyst-Q

Catalyst-Q Docs

Start here if the webapp felt too technical: Catalyst-Q turns one route file into a signed Route Decision Record that an operations, finance, or compliance owner can approve without trusting a black box.

First route-file intake.

The first useful workflow is intentionally narrow so the buyer can see value before system integration.

1

Upload or paste

Start with orders, stops, vehicles, capacity, time windows, service times, and the dispatcher baseline.

2

Compare

Catalyst-Q builds the candidate plan and compares it against current plan, open-solver rows, and route-stability constraints.

3

Approve

The decision owner gets a signed Route Decision Record with rollback, replay id, confidence, and the next safe action.

How the moat works.

  • Catalyst-Q SDK runs the candidate search, verification, hostile baselines, and proof-packet assembly.
  • Catalyst Brain keeps tenant-scoped memory of prior assumptions, accepted outcomes, rejected actions, and recurring failure patterns.
  • AI Workers automate intake, missing-data checks, buyer briefs, reviewer routing, and approval-state updates.
  • The Route Decision Record compounds: every accepted or rejected route decision improves the next approval path.

Where to go next.

  • Run the sample RouteOps proof: https://catalyst-q.strategic-innovations.ai/routeops-proof-room
  • Score pilot fit: https://catalyst-q.strategic-innovations.ai/pilot-room
  • Preview the freight proof packet JSON: https://catalyst-q.strategic-innovations.ai/v1/freight/proof-packet
  • Wire the API after the story is clear: https://catalyst-q.strategic-innovations.ai/api