Originally published on Thomas’s Substack. Reproduced from the owner-supplied publication PDF. Statements and patent-status references reflect the original publication date.
Editorial introduction · added October 20, 2026
Before you read
Local clocks worked until railroads crossed their boundaries faster than people could reconcile them. The essay uses that history to explain why valid credentials, logs, and permissions can still leave an AI undertaking ungoverned. It distinguishes the narrow issued communications claims from the broader proposition pursued in pending filings while explaining why the SSOAR authority constraint matters beyond its first embodiment.
SSOAR means Session-Scoped Orthogonal Authority and Routing.
Why read it?
- Architects and standards teams
- Look for the shared reference that persists as an agent moves between tools, systems, and organizations.
- Investors and patent diligence readers
- Follow the essay’s distinction between the examined patent embodiment and the broader architectural thesis.
This introduction is separate from the original essay.
Go to the original essay ↓
On Sunday, November 18, 1883, noon happened twice.
In towns across North America, clocks struck twelve by the sun and then, minutes later or earlier, struck twelve again by the railroad. That morning, every railroad clock on the continent was reset to one of five
standard zones. Some had already passed noon when the new time arrived. They got a second one.
Nobody in 1883 thought the railroads had invented time. Time was older than anyone’s great-grandparents. Every town kept its own, set by the sun overhead, and it worked. It worked for centuries, because nothing moved fast enough to notice that noon in one town was not noon in the next.
The railroad noticed.
A train leaving one town and arriving in another crossed dozens of local noons along the way. Schedules could not be written against a clock that changed every few miles. Two trains on one track, each running correctly by its own local time, could meet head-on. Each clock was right. The railroad was wrong.
So the railroads did something the governments had not yet done. They made time a shared reference instead of a local observation. Congress did not write it into law until 1918. By then, the country had been living on railroad time for thirty-five years.
Remember the structure, because it repeats.
Time existed. Local time was correct. A new capability moved things fast enough and far enough that local correctness stopped adding up to anything. The missing piece was not more accurate clocks. It was a reference that held across the distance.
The pattern
Look for it, and you find it everywhere.
People did business long before the corporation. A merchant, a partner, a family, a ship. The business was the people, and when the people died or quarreled, the business ended. That worked while enterprises were
small and short. Then they became too large and too long-lived to be identical with the humans running them. Law created a persistent entity that survives the people inside it. Owners sell, officers retire, employees leave. The undertaking continues, and everything done in its name acquires meaning from it.
Ships, trains and trucks all carried cargo before 1956. They did not share a boundary. Every transfer from ship to dock to rail to truck meant breaking the load apart and rebuilding it, and at every break things were lost, stolen, damaged or misrouted. On April 26, 1956, the Ideal X left Newark for Houston carrying fifty-eight steel boxes. The container did not make any carrier special. It made the load itself survive the transfers between them.
Same structure each time.
A capability changes the speed, scale, distance, or consequence of what people do. The old arrangement keeps working for a while because something informal quietly carries the load. Then the informal carrier fails often enough that it has to become explicit. A hidden assumption becomes infrastructure.
And here is the part that matters most for what comes next.
The primitive is often not built for everyone who eventually depends on it. Standard time was built for trains. Aviation, broadcasting, financial markets, and every calendar invitation you have ever received inherited it. The container was one entrepreneur’s answer to a slow, expensive waterfront. Global manufacturing inherited it. The corporation was built for chartered trading ventures. Every modern enterprise inherited it.
The primitive arrives for a specific need. The beneficiaries arrive later, and most of them never learn where it came from.
The funnel
The pattern shows one more thing, and it is the part people forget once the answer looks obvious. The primitive does not arrive in one piece. It is distilled.
The packet is the clearest case. In the early 1960s, Paul Baran at RAND worked out how to break messages into blocks that could find their own way across a damaged network. In 1965, Donald Davies at Britain’s National Physical Laboratory arrived at the same idea independently and gave it the name that stuck. Then the field widened, the way it always does. ARPANET ran its own host protocol. Davies’s laboratory built its own network, the French built CYCLADES, and the public data networks standardized X.25, which carried packets over virtual circuits, keeping the old idea of a circuit. For years afterward, whole standards bodies fought over which model the world would use.
Every one of those efforts worked. Each solved part of the problem. None of them was the answer, because the answer was not a network. It was a rule for how any network could join any other.
In 1974, Vint Cerf and Bob Kahn published that rule. It took nearly a decade more to prove it, and on January 1, 1983, ARPANET switched its hosts over to TCP/IP in a single day. Ninety-nine years after the day of two noons.
That is the funnel. A wide top: many independent people seeing the same pressure and building local answers, each correct on its own terms. A long middle: competing implementations, arguments over vocabulary, standards drafts, alliances. And a narrow end, where the thing everyone of them was circling is finally stated simply enough to hold everywhere.
Looking back, the narrow end seems obvious. Looking in from the wide top, it never does.
The person who carried it
For about forty years, digital work had a hidden layer, and it was a person.
An employee moved from the CRM to the email client to the billing system to the phone. None of those systems knew what the employee was doing overall. None of them needed to. The employee carried it: what this is for, who asked, what was approved, what has changed since. Each system checked its own login and its own permissions, and each check was correct. The undertaking lived in someone’s head, and that head went everywhere the work went.
That is local time. Every system kept its own noon, and it worked because a human moved slowly enough between them to reconcile the differences.
I made this argument in The Authoritative Internet, and the line bears repeating: AI did not create that question. It removed the person who used to answer it.
An agent does not carry the undertaking in its head. It moves between tools, models, services and organizations at machine speed, and every step can be individually correct. The credential is valid. The permission is real. The tool call is logged. The model’s output is well formed. Each clock is right.
Nothing says the whole thing is still the thing someone authorized.
AI needs a primitive
This is where the argument has to land plainly, because it is usually softened.
AI does not need better credentials. It does not need more logs, finer permissions or a more accurate model. Those are better local clocks. Each is useful, but none adds up to a shared reference.
AI needs an authority primitive: a governing authority that holds while the actor, the model, the tool, the data, and the state change underneath it. Something every step can be checked against before it becomes real. Something that does not quietly start over each time the work moves to a new component.
Authority always existed. Every agent ever deployed was deployed by someone, for something, within limits. AI did not invent authority any more than the railroads invented time. It made locally reconstructed authority inadequate, the way the train made local noon inadequate.
The authority problem is in the middle of the funnel right now, and it looks exactly like the packet did in the 1970s. Identity vendors, cloud platforms, payment networks, standards authors and researchers are each building a correct local answer. On September 22, twelve companies, including AWS, Google Cloud and Okta, formed an alliance around the problem of agents that “execute beyond their intended scope” as “credentials cross trust boundaries.” Standards drafts now require that authority at each step of a chain be no greater than the step that delegated it. Payment networks are binding an agent’s actions to what a cardholder approved. Each effort is real, and each solves part of the problem.
The need is no longer in dispute. What remains is the narrow end: the rule that holds no matter which vendor, model, tool or network the work passes through.
First embodied somewhere else
The primitive I have been describing was not first embodied in AI.
Its first examined embodiment was a video call.
The problem was ordinary. A call is placed and not answered. The system routes it, plays a recorded message, captures a reply. Or a participant waits in a lobby before the meeting starts, and something is
delivered to them there. Or a participant needs captions or a sign- language interpreter partway through. In every case, the interaction changes while it is still live, and the question is whether what happens next is still governed by the authority that started it, or whether some new, unrelated authority quietly takes over.
The answer became a constraint. Across a live interaction, the governing authority survives the change, and no second independent authority root is created. Downstream authority can be delegated, narrowed, or passed along. It cannot be minted fresh in the middle.
That constraint was examined and allowed. U.S. Patent 12,659,408 issued on June 16, 2026, and the examiner’s reasons for allowance rest on exactly that: all routing, streaming and reply capture executed under a single session authority boundary, with no new session authority created along the way.
That is the unusual part of this story. In the usual funnel, the narrow end is written last, after the field has argued its way down to it. Here the rule was stated, examined, and allowed while most of the field was still at the wide top. I made that case in Before the Market Names the Primitive. The funnel is why it matters.
Here is what is easy to miss. AI was already inside the architecture.
The issued claims include an artificial intelligence processor generating a transcript or description of the response, and a machine learning algorithm modifying the decision tree based on how people behave and respond. The second examined family, allowed in May with every claim as filed, adds a machine-learning classifier to a method in which third- party content enters a session only under a platform-issued credential, without opening a parallel session. A filing from October 2025, now public, describes a policy gatekeeper that evaluates entitlement and consent before an AI sign-language model is activated, and an audit log that records each activation against the same session.
The first embodiment was communications.
The invention is not the communication. It is the authority that survives it.
Every handoff between two things is a communication. That is why the problem appeared there first, and why it does not stay there.
The constraint does not ask what kind of actor is operating inside the boundary: a person, a routing engine, a media server, a model. It asks whether the authority governing the interaction survives what that actor does. The record shows the constraint holding when the actor is a model, whose output can vary from run to run. Variable output does not become authoritative on its own. The governing authority decides whether it can.
To be exact about the line: the issued patent does not claim AI agents in general, and I do not say it does. The pending continuations pursue the broader proposition. What the examined record shows is narrower and, I think, more interesting. The authority primitive was already carrying AI inside it before the market named the problem.
The beneficiary
So which is it? Does AI need its own primitive, or does it get one someone else built?
Both, in the same way the railroads were both.
AI needs an authority primitive as surely as the railroads needed standard time. Without it, every step is locally correct, and the whole is ungoverned. That need is real, and it is AI’s.
But AI does not have to originate the primitive it now requires, any more than air travel had to invent time zones. The primitive was built for a specific need: a live interaction that changes while it is happening. AI is
the first beneficiary powerful enough to make the need impossible to ignore. It will not be the last.
The railroads did not invent time. They made local time impossible.
AI did not invent authority. It is making local authority impossible.
The noon it needs has already been set.