Model Choice Is an Information Policy

Model selection is presented as a capability decision: accuracy, latency and price.

For private work, it is also an information policy. Hosted, regional, local and specialist models create different observers, retention and tool boundaries.

Route by task and data

A public research question, restricted legal analysis and personal health summary should not automatically use the same model and connector set.

Value object — The Model Routing Policy

- Task class.

- Data classification.

- Approved models.

- Permitted connectors.

- Retention and region.

- Escalation or no-AI route.

Keep choice replaceable

Evaluate factual quality, privacy controls, failure behaviour and portability. Avoid embedding provider names directly into every workflow.

The best model is the model permitted for this information and consequence—not the one winning a generic leaderboard.

Where this breaks

A routing policy can exist on paper while users select models directly from a menu. Sensitive work then follows convenience, speed or brand familiarity.

The operating move

Enforce routing in the interface and connectors. Show users why a task was routed and provide a secure exception process when the classification is wrong.

Default by data class.

Hide prohibited model choices.

Log routing exceptions.

Re-evaluate after provider change.

The test

Submit the same sensitive task through every available interface. None should bypass the approved model, retention and connector policy.