The computational change
From rules to judgment.
Traditional software can be enormously complex, but its institutional authority is comparatively easy to locate. The organization decides what the system is allowed to do; engineers encode those rules; the runtime executes them. If a payment is released when an approved invoice satisfies a set of deterministic conditions, the software does not have to decide for itself what an invoice means or whether the approval seems persuasive. Those questions have already been reduced to application state.
Inference lets the application work before the world has been completely reduced to predicates. A model can judge that two differently worded clauses probably conflict, that a damaged-delivery photograph appears consistent with the customer's description, or that a research record still lacks the evidence needed to answer the question. The programmer specifies the surrounding problem but no longer authors every intermediate conclusion.
The distinction is architectural, not a claim that earlier software was deterministic in the mathematical sense. Statistical systems, machine learning, randomized algorithms, and distributed systems long predate foundation models. In conventional enterprise applications, however, consequential state transitions were ordinarily specified in code, rules, or process; open-ended interpretation remained largely with people. General-purpose learned inference moves that interpretive faculty inside ordinary application execution.
x → f(x)The programmer specifies the operative rule.
(x, C) → ŷThe application supplies context; inference contributes a judgment.
The transformer era matters to enterprise software for that reason. Machine learning and probabilistic computation long predate 2017. What transformer-based foundation models made commercially consequential was a general-purpose inferential faculty over much of the symbolic material in which organizations actually conduct work: prose, correspondence, documents, images, code, policy, research, and records.1
Nothing in this argument depends on whether a model is conscious, sentient, or person-like. Those are different questions. The engineering fact is narrower and sufficient: software can now contribute useful judgments under uncertainty without the application developer having specified the operative reasoning for each case.
But the moment software can contribute a judgment that its programmer did not explicitly encode, an old assumption breaks. The application still has to determine what that judgment is entitled to establish or cause.