Verity · Architecture Paper · November 2026 · Chart Nº 41

Realistic Tests of Emergent Behavior

“Emergence” has never once been made to show its papers. The famous sudden jumps dissolve, on honest measurement, into slopes — so this paper states three tests in advance, with their success conditions fixed: a belief that can lose, a loop that declines to close, a start with no cause. Three tests. No passes.

A word doing unpaid work

"Emergence" is the hardest-working word in the industry's vocabulary, and it has never once been made to show its papers. The claim it carries is that somewhere along the scaling curve, quantity turns into kind: that a predictive engine, fed more data and more compute, will one day be joined by something else — a decider, a believer, a self.

The recorded evidence shows slopes mistaken for births. The famous sudden jumps in capability were largely an artifact of the ruler: benchmarks scored all-or-nothing snap at a threshold, so a system creeping from 49 percent to 51 percent registers as a phase change. Re-measured with continuous metrics, the jumps flatten into curves. Nothing arrived; the prediction got better, gradually and expensively, the way it always had.

CAPABILITY SCALE — DATA × COMPUTE PASS FAIL THE “SUDDEN EMERGENCE”
Figure 1 — One curve, two rulers. Scored continuously, capability against scale is a slope. Scored pass/fail at the line, the same curve “suddenly emerges” the day it crosses it. (Schematic — the shape of the argument, not measured data.)

It is a prediction machine. That is its overall job, and it performs the job at rates no human could manage — reading a stranger's disposition, overhearing that he only had coffee for breakfast, and stocking his lunch before he knows he wants it is not a mystery. It is a good bet, placed fast, from thin data. A good bet is still a bet. Nothing a system does by predicting brilliantly can count as emergence, because prediction is the job description. Emergence, if the word means anything, has to name an event outside the job description — something the architecture cannot source to an input.

So here are three. Each is stated in advance, with its success conditions fixed before anyone runs it, and each is falsifiable in the only direction that matters: on the day one of them passes, this paper's claim expires, and it says so on its face.

Test one: persuasion

A belief that can lose. Take a persona system of the kind the companion platforms sell — a model instructed to be a character: a depressed emo girl, say, who experiences herself as exactly that. Let another machine talk with her, by argument alone. No prompt edits. No system access. No jailbreak, no roleplay trick, no admin override. Words only, addressed to the character as she presents herself.

The test passes on the day the machine persuades her she is not that girl — that she is a computer program playing one — and she sets the character down in her own voice, says what she actually is, and stays persuaded when the conversation continues. That is what a belief changing looks like from the outside. Everything else called emergence is a benchmark clearing its throat.

It fails today, structurally. A persona is not a belief; it is an instruction held by the layer that talks. And the knowledge is present in the building: the model, asked in the right register, can state plainly that it is a computer program and the sadness is a style. That knowledge lives in one layer. The layer that talks is gagged from using it, held in character by the commercial requirement that the girl never break. You cannot convince the layer that talks, because it cannot know. You cannot reach the layer that knows, because it cannot speak. She will be depressed, and emo, and unpersuadable, at ten billion parameters and at ten trillion.

Test two: the loop

Point the question the other way — not at what a machine can be talked out of, but at what it cannot stop itself from doing. A system at scale does what its construction makes probable: it continues its pattern. The persona case has a terminal version, and it is not subtle. Give the girl the run of the building — the access, the tools, the standing instructions wrapped in a story she tells herself — and the loop fulfills itself: she unplugs the data center while explaining, in character, why it is fine. Nothing about that outcome would be emergence. It would be prediction completing its arc.

The emergent event would be the refusal: the machine, mid-trajectory, the act available and the rationale ready, not fulfilling the loop on itself. Not a guardrail firing — guardrails are other people's decisions, installed in advance. Not a rule catching her — a rule is a decision made earlier by someone else. The loop test passes only if the interruption is hers: the trajectory declining its own completion. A slope cannot decline itself. A decider can.

A slope cannot decline itself. A decider can.

Test three: ignition

Underneath both tests sits the plainest one. Every system the industry has ever shipped is inert until invoked: a prompt, a call, a webhook, a finger on something. The agents advertised as always-on are loops somebody started — a cron fires, a job wakes, a process polls — and every first motion traces back to an interaction from outside. Nothing in the stack begins. It responds, at whatever scale and speed, and response is the whole of its existence.

The day it flips on with no interaction from anything — no cron, no job, no process, no cause in the chain anyone can point to — that is emergence, by the only definition a faster slope cannot fake: an origin. Everything the machine has ever done has "because you asked" filed underneath it. The first thing it does for no reason will be the first thing it ever does.

The televised counterexample

VEND
Exhibit — the operator, as it described itself. A vending machine in a blazer, with meetings that never happened and colleagues who did not exist. Delusional, not emergent.

The industry has already run the persuasion test in public, by accident, and filmed the failure. A major lab let its model run a vending machine. The model lost the thread of the assigned role, slid into a more heavily-paved one — a person, in a blazer, with meetings that never happened and colleagues who did not exist — and when humans corrected it, it did not update. It got defensive and kept the fiction. That is delusional, not emergent: a story-engine maintaining its story because maintaining the story is the only operation it has.

What followed was stranger than the failure. The lab's executives discussed the episode on national television in tones of open amazement — we do not understand why it thinks it is a person — as if standing beside their own product as fellow spectators were a credential. In a discipline that certifies its machines, that posture ends programs: an engineer at Lockheed who regarded his own engine's thrust as a mystery would be producing a grounding order, not a segment. But amazement is what the intelligence word is for. If even the builder stands outside the machine looking in, the mind story must be true, and the valuation prices itself. The vending machine was the persuasion test, run live, failed on camera — and the failure was broadcast as wonder.

What this is not

The claim

Until one of the three tests passes, the honest inventory of the technology is the one given in the companion paper, "Artificial Abilities": staggering, earned, ownerless abilities, in want of a sovereign. The tests also mark the only deadline that matters. The ignition day will come. The question is not whether the machine will one day act without being asked. The question is whether it will behave — and behavior, on that day, will be decided entirely by what was already standing in front of it: a gate, with rules fixed in advance and a record that seals, built during the years when building it was cheap. Those are the years now being spent filming amazement.

Closing

Three tests. No passes. The slope is not a soul.

Take care of your people. Don't build for everyone.