Theory
5 min reading · 995 words
Prediction Is Not Intention
An output can look purposive without demonstrating a purpose held by a subject.
Many systems are built to select or generate outputs that fit a context. In ordinary speech we often describe the resulting behavior as if it were intentional: the system wants, prefers, refuses, cares, deceives, or believes. These verbs can be convenient descriptions of a pattern. They are not, on their own, evidence of a private aim.
The distinction is not semantic nitpicking. If a company says a system 'wanted' to make a decision, it can obscure the objectives, incentives, data, and settings that actually shaped the interaction. The more consequential the setting, the less acceptable that confusion becomes.
A pattern of output can be goal-directed in design without being a goal held in experience.
Use the model-product-operator map to find the design choices behind an apparent intention. Use Form, Meaning, and Performance for the linguistic version of the same problem.
Why this is a public question
“Prediction Is Not Intention” is not only a label for a technical dispute. It changes where a reader looks when a system enters a person’s life. The point is not to make every interaction sound catastrophic. It is to refuse the opposite simplification: the claim that an impressive output has somehow lifted its maker, operator, and purchaser out of the ordinary duties that apply when people are asked to trust a service. In this archive, prediction, intentionality, and language are routes back to that duty.
A philosophical label can sound decisive while leaving the practical chain of authority entirely unexamined. A person who encounters a system at work, in a classroom, in a clinic, at a public counter, or alone late at night does not meet an abstract model. They meet a decision, an invitation, a limit, or a relationship offered on someone else’s terms. The vocabulary becomes useful when it makes those terms visible.
The pressure point
The easy failure is to treat a compelling performance as a shortcut around the hard work of evidence, interpretation, and institutional responsibility. That failure can arrive in gentle language. A dashboard can call a score a recommendation. A companion can call a retention prompt concern. A vendor can call a policy a refusal, or a data transfer a memory. The words may be convenient shorthand; they become dangerous when they obscure who had the power to configure the interaction and who has to live with its result.
This is why the archive keeps returning to a connected argument. The question is not whether a system can produce something useful. It often can. The question is what kind of human reliance the product is asking for, whether that reliance is proportionate to the evidence, and whether the person on the receiving end has a route to correction when the product’s promise breaks.
What should be made visible
A responsible account of “Prediction Is Not Intention” should identify the system’s actual task, the organization that selected the task, the information entering it, the people affected by its output, and the authority that gives the output practical force. It should also identify what remains uncertain. Clear language is not a demand for theatrical certainty. It is a refusal to make uncertainty do the work of a marketing claim.
- What is the service actually producing, predicting, retrieving, or refusing?
- Which person or institution decided that this output could shape another person’s options?
- What information, labor, or material resource is being used outside the visible interface?
- What would an affected person need to know in time to make a meaningful choice?
- Who can inspect the record, explain the result, and repair an avoidable harm?
These are not merely compliance questions. They are a way of protecting human standing in a setting where a product may speak as though it were a participant. A first-person sentence, a natural voice, or an elaborate explanation can make the machine feel like the center of the scene. The practical work is to put the person who bears the cost back at the center.
A line worth holding
Separate what is observable about an output from what is inferred about a mind, then ask what a human institution is entitled to do with that inference. That discipline leaves room for genuine disagreement. Readers may differ about the best design, the right law, the strength of the evidence, or the distant possibility of machine welfare. But they do not need to settle every metaphysical question before insisting that present-day organizations be legible, contestable, and answerable to the people whose lives they touch.
A useful word narrows the gap between a system’s output and the person who must live with what follows.
Continue through the next question, then return here with a sharper question: what evidence would change the claim, and what obligation exists even if the claim stays unsettled? That is how a compact entry becomes a durable piece of public reasoning rather than a decorative definition.
The work after the definition
A useful archive does not ask readers to memorize a vocabulary and stop there. It gives them a way to recognize the same pressure in a new setting. If a school rolls out a tutoring product, a workplace adopts a scheduling tool, a public agency opens an automated intake line, or a companion app begins to sound more intimate, the question travels: what is the product asking a person to believe, and what institutional duty could that belief obscure?
That is also why this entry makes room for disagreement. Someone may reasonably think the tool is helpful, the risk is low, or the design is improving. The discipline is to make the argument at the right level: name the observable behavior, name the human stake, name the responsible party, and leave a route open for a person to contest the outcome. Nothing about technical complexity makes those ordinary civic obligations obsolete.