Source-Sensitive Model Route

A source-sensitive model route is used when the answer depends on exact external facts rather than general reasoning. Examples include API parameters, pricing, product availability, legal or medical wording, compliance rules, dates, versions, and current documentation.

The route starts by asking whether the fact could have changed or whether exact wording matters. If yes, the workflow should locate primary sources, compare the draft against them, and distinguish verified fact from inference. A stronger model without source access is not enough.

This route is useful even in a one-default workflow. The default model can draft the structure, but source-sensitive claims need a separate check. That check may use browser search, official docs, repository code, changelogs, or local files depending on the domain.

The route should leave a citation trail or at least a source note. Reviewers need to know why the answer should be trusted. If a source is unavailable, the output should say what remains unverified.

The boundary is efficiency. Do not over-source stable, low-risk questions. Activate the route when change, exactness, or consequences justify it.

Source-Sensitive Model Route

// COMMENTS

ON THIS PAGE