Task- und Modellrouting mit klaren Grenzen.

task classification

Tasks are normalized into explicit technical envelopes before routing.

model/provider selection

Routing decisions are separated from provider execution and can remain deterministic.

deterministic versus AI-assisted routing

Deterministic routing is preferred for known tool classes; AI assistance is bounded by structured inputs and outputs.

local/API fallback behavior

Local workflows and API-backed providers are modeled as separate execution surfaces.

structured input/output

Task envelopes, status metadata and generated outputs are machine-readable.

execution boundaries

Write, destructive and privileged actions require explicit operator control.

retry/failure behavior

Failures are recorded as technical state rather than hidden behind automatic escalation.

human approval gates

Sensitive operations keep human review before credentials, infrastructure or data mutation.