Routing Simulator

Start with a scenario, adjust task shape and watch the route change: model tier, governance band, risk flags and gate outcome. Routing here means the path for the work, not a vendor pick list.

Demo only

Outputs are produced by routeTask in src/lib/routingRules.ts. They are not legal advice and not tuned to your firm.

What this shows

A low-risk internal summary and a client-facing advice note should not follow the same path, even when the prompt looks similar.
Routing decisions should be explicit enough to inspect: model tier, governance and flags, not a black box.
Budget pressure and sensitivity can trade off only when policy allows it.

Scenario briefing

Pick a situation, then tune the route. The objective is to see how the same tooling makes different decisions when context, destination and risk posture change.

Current narrative

A team needs quick directional research for an internal workshop, speed matters and cost discipline is expected.

Control inputs

Task type

Sensitivity

Complexity

Budget pressure

Output use

Decision storyline

Model tier

Lightweight

Governance band

Standard

Review load

Moderate

Estimated cost

Low

Expected latency

Faster

Risk flags

1
Task requested
2
Context assembled
3
Route selected
4
Execution planned
5
Gate decision
Can proceed with controls
6
Outcome recorded

Related playbook