Not a wrapper
Wrappers generate text. ClaimRoute produces operational truth: policies, evidence, and replayable actions.
How we're different
- Orchestrator for long-running follow-ups.
- Policy engine + approval gates.
- Evidence binder exports and audit replay.
Trust rule: AI drafts, humans decide for sensitive outcomes.
Wrappers die by three cuts
No governance
No explicit approvals, no policy versioning, no override logging.
No long-running reliability
No idempotency, retries, SLAs, or escalation ladders.
No integration depth
They can’t keep a file complete across channels and time.
ClaimRoute is infrastructure
Orchestrator
Retries, SLAs, follow-ups, and Catastrophe Mode.
Policy engine
Approval gates, adequacy thresholds, safe mode.
Evidence model
Timeline events + binder exports with hashes.
Simulation
Routing changes measured before rollout.
Proof you can test
- Seed a sample claim and run triage.
- Flip Catastrophe Mode and re-run routing.
- Draft a status update and see adequacy scoring.
- Export a binder (PDF + JSON + CSV).