Build the mental model

Model choice is a constrained engineering decision, not a leaderboard shopping trip. The best model is the smallest, cheapest, fastest option that meets the task’s quality and risk requirements in the environment where it will run. The boundary matters: A benchmark estimates capability under a test setup; a deployment decision includes your prompts, data, traffic, risk, and operations. Parameter count is not quality, context limit is not effective recall, and a low token price is not a low cost per completed task.

Draw the system in prose as four boxes: need → evidence → decision → consequence. The need belongs to a person or workflow, not the model. Evidence is what the system can legitimately inspect. The decision is the transformation choosing a model performs. The consequence is what changes for a user, operator, or downstream system. If you cannot fill every box, the design is still a label rather than a working mental model.

For an invoice-extraction service, ask what happens when the model is absent. That baseline reveals the actual value. Then ask what remains deterministic: identity, permissions, arithmetic, record updates, and irreversible actions should not become fuzzy merely because a model participates. The model can propose or interpret; an application still owns policy and state.

A benchmark estimates capability under a test setup; a deployment decision includes your prompts, data, traffic, risk, and operations. Parameter count is not quality, context limit is not effective recall, and a low token price is not a low cost per completed task. This distinction is practical. It tells you where to inspect a failure and which component can repair it. Avoid explaining the concept as “the AI understands everything.” Name the artifact moving between stages—a token sequence, retrieved passage, ranked candidate, stored memory, trace, image latent, or agent message.

A good explanation also includes uncertainty. Inputs may be incomplete, learned behavior is probabilistic, and proxies can disagree with real outcomes. That does not make the system unusable; it means the workflow needs a fallback and a way to expose uncertainty rather than hiding it in fluent prose.

Use this compact record:

| Question | Concrete answer to supply | |---|---| | User job | One action the person is trying to complete | | Input boundary | Data allowed into the system | | Model contribution | The uncertain judgment or generation | | Deterministic guard | Rule, permission, schema, or calculation | | Success signal | Observable outcome, split by important group | | Escape hatch | Retry, fallback, escalation, or stop |

For this topic, a plausible first signal is not “the output looks intelligent.” It is a task outcome tied to the concept and checked on representative cases. Save this sketch; later pages add controls and measurements without changing the user job.

Teach the concept using the analogy above, then deliberately state where the analogy breaks. The kitchen, notebook, workbench, team, or librarian metaphor omits numerical limits and operational ownership. A learner has mastery when they can leave the metaphor and describe the actual information flow.