Model routing

Model routing selects a model for a task while keeping the relevant company context available. A straightforward lookup and a question that requires comparing several sources can call for different kinds of work.

Company Brain holds the sources, relationships and decisions independently of a particular model.

What stays with the work

Consider a readiness brief. One step extracts a status from a checklist. Another compares that status with the approval condition and prepares the final explanation.

Both steps need the correct project context. Changing the model used for a step should not change which source or approval condition applies.

Specify the outcome first

You can make the task easier to evaluate by describing the result you need:

Prepare a readiness brief from these sources. Keep confirmed facts separate from pending approvals and show the evidence for each open item.

Evaluate whether the output answers that request. A model's name alone does not establish that a result is accurate or complete.

Availability and deployment

Model availability is configured for each deployment. Logos or examples on the website illustrate the model ecosystem; they do not mean that every model is selectable in every account.

For enterprise work, discuss any model requirements with Hexagon as part of implementation. Include the type of work, data considerations and how you will evaluate output quality.

Review the applicable privacy policy and provider terms for data processing. Model routing does not remove the need to understand how the information used in a task is handled.