Why Your Network Is Half the Solution
Intent-based networking is a genuine engineering achievement. Cisco DNA Center, ACI, Juniper Apstra, Palo Alto Prisma SD-WAN — these systems abstract policy intent away from individual device configurations. You define what the network should do; the controller figures out how to do it across thousands of devices. Zero-touch provisioning. Policy-driven microsegmentation. Dynamic path selection based on real-time telemetry.
The enterprise network has become, in a meaningful sense, an intelligent routing fabric.
But it routes packets. Optimally, securely, at scale — but packets. Bytes moving from source to destination according to policy.
What it does not do:
- Take the distilled outcome of a local analytical process and route it to every other node in the world that has the same problem
- Identify semantic similarity between outcomes produced at the edge of two different organizations
- Enable distributed synthesis across N nodes without any data leaving those nodes
- Scale the number of unique synthesis opportunities as N(N-1)/2 while keeping routing cost at O(log N) or better
These are not networking problems in the traditional sense. They are a different category of routing problem — one that Cisco, Juniper, and every SASE vendor has left unaddressed, not because they missed it, but because it requires a different architectural layer entirely.
The Every-Component-Exists Objection
Before describing what the missing layer looks like, this objection must be addressed directly because it is a good one:
"We already have the components. We have REST APIs, data lakes, vector databases, Kafka event streams, SD-WAN, and federated learning frameworks. What does a new architecture add?"
The objection is correct. Every component exists. The discovery is not a new component.
The discovery is the complete loop — the specific sequence that closes the intelligence cycle end to end. Here is why each existing component fails to close it:
Data lakes centralize data to a hub. They route data inward, not insights outward. When your hospital sends data to a central lake, the intelligence that emerges stays at the center. It does not route back to your semantic twin at another institution. Centralization is, by definition, the opposite of the closed loop.
Kafka routes events with high throughput and low latency. It does not synthesize distributed outcomes. A Kafka consumer receives an event; it does not receive a distilled outcome packet from a semantically similar node and synthesize locally against it. Kafka is an excellent transport mechanism. It is not an intelligence routing protocol.
Vector databases retrieve — they find semantically similar vectors when queried. They are passive. They do not emit insights to relevant consumers when a new outcome is deposited. They do not trigger synthesis. They wait to be asked.
Federated learning keeps raw data local and aggregates model gradients centrally. It is a significant improvement on centralized training. But it still has a central aggregator. It still requires a consensus step. And it produces a shared model — it does not produce routed outcome packets that each node synthesizes against its own local context. Federated learning closes the data privacy gap; it does not close the distributed synthesis loop.
Intent-based networking routes traffic by policy intent. Brilliantly. It does not route validated drug safety signals to every pharmacovigilance system in the world with the same patient profile. The "intent" in IBN is network configuration intent — QoS policy, security policy, path selection. It is not semantic intent derived from analytical outcomes.
Each component does something real and valuable. None of them close the loop. When you close the loop, intelligence scales as N(N-1)/2. That is not a property any of the above systems exhibit.
What the Missing Layer Looks Like
The Quadratic Intelligence Swarm — QIS — is an architecture discovered by Christopher Thomas Trevethan on June 16, 2025. It defines a complete loop for distributed intelligence routing. The loop has six steps:
Raw signal stays local. An edge node — a hospital, a manufacturing plant, an autonomous vehicle fleet — processes raw data locally. Raw data never moves. Privacy is architectural, not policy.
Distillation into an outcome packet. The local analytical process distills its result into a small structured payload — approximately 512 bytes. This is not raw data. It is a compressed outcome: what this node learned, in a form that can be routed.
Semantic fingerprinting. The outcome packet is fingerprinted — a representation of its semantic content that can be compared to other fingerprints without revealing the underlying data.
Routing by similarity to a deterministic address. The fingerprint resolves to a routing address. Outcome packets route to nodes whose fingerprints are semantically similar. The routing mechanism does not matter — DHT achieves this at O(log N) cost per hop, but a database lookup, a pub/sub topic subscription, a REST API call, or even a shared folder on a local network all work. QIS is the protocol. The transport is whatever your infrastructure already runs.
Local synthesis. Receiving nodes synthesize the incoming outcome packet against their own local context. No data leaves. The synthesis happens at the edge using only the ~512-byte outcome packet received.
New outcome packets. Synthesis produces new outcome packets, which re-enter the loop. The loop continues. Intelligence compounds.
This is the complete loop. The breakthrough is not step 4 (routing) or step 3 (fingerprinting) or step 5 (synthesis). The breakthrough is that steps 1 through 6 form a closed cycle — and when they do, something mathematically interesting happens to the scale of intelligence.
The Drug Safety Example in Detail
88% of Phase II to Phase III clinical trials fail. Many of those failures are safety failures — signals that existed in distributed post-market data but were never surfaced in time to redirect the trial.
Vioxx was withdrawn in September 2004 after an estimated 38,000 cardiovascular deaths. The data supporting the cardiac risk signal was distributed across FAERS reports, insurance claims databases, and hospital adverse event records. No single institution had a statistically sufficient sample to raise an alarm alone. The distributed systems never synthesized across sites. It took five years from market launch for the signal to become undeniable.
This is not a data collection failure. FAERS, EudraVigilance, and VigiBase collect adverse event reports globally. This is an intelligence routing failure. The collected data sits centrally. The intelligence does not route back to the prescribing edge. The pharmacovigilance system is a one-way funnel — data flows in, insights do not flow back out to the distributed sites that need them.
Under QIS, the loop runs differently:
- Hospital A's pharmacovigilance system detects an ADE pattern. It distills the pattern into a 512-byte outcome packet. Patient records never leave the hospital.
- The outcome packet is semantically fingerprinted based on drug combination, patient population characteristics, and adverse event type.
- The fingerprint resolves to a routing address. The outcome packet routes — via the hospital's existing Kafka cluster, or REST API, or SD-WAN fabric, or whatever transport is already running — to Hospital B, Hospital C, and Hospital D, whose fingerprints indicate they have the same patient profile and are monitoring the same drug combination.
- Hospitals B, C, and D synthesize locally. Each now knows that other institutions with semantically similar populations are seeing the same pattern. New outcome packets are generated. They route further.
- The safety signal propagates across 200 hospitals in days, not years. No patient data moves. There is no central aggregator that can be breached or that creates a HIPAA compliance exposure. The routing infrastructure is the hospital's existing network.
The Vioxx signal across 200 hospitals would have generated 19,900 unique synthesis paths. At five adverse events per hospital, that is 99,500 synthesis opportunities that did not exist under the hub-and-spoke model.
The Math That Changes the Equation
The scaling property is the reason this architecture is qualitatively different from every hub-and-spoke alternative.
In a hub-and-spoke model — data lake, central aggregator, federated learning coordinator — intelligence synthesis scales linearly. N nodes produce N data flows to the center. The center produces one aggregate output. N synthesis paths.
In a fully connected mesh — every node talks to every other node directly — you get N(N-1)/2 synthesis paths, but network overhead scales as O(N²). You cannot run a fully connected mesh at enterprise scale.
QIS achieves N(N-1)/2 synthesis paths while routing overhead scales at at most O(log N) per hop (using DHT as the routing mechanism) or O(1) for simpler transports. This is the specific mathematical gap that the architecture closes.
| Network Size | Hub-and-Spoke Paths | QIS Synthesis Paths | Overhead |
|---|---|---|---|
| 10 sites | 10 | 45 | O(log 10) ≈ 3 hops |
| 50 sites | 50 | 1,225 | O(log 50) ≈ 6 hops |
| 200 hospitals | 200 | 19,900 | O(log 200) ≈ 8 hops |
| 10,000 edge nodes | 10,000 | 49,995,000 | O(log 10,000) ≈ 13 hops |
At 200 hospitals, QIS produces 99.5x more synthesis paths than hub-and-spoke, at logarithmic routing cost. At 10,000 edge nodes, the ratio is approximately 5,000x. The gap compounds with scale.
This is not an optimization of an existing architecture. It is a different scaling curve.
The Protocol, Not the Transport
The most operationally significant property of QIS for enterprise infrastructure teams is this: QIS is a protocol, not a transport. It does not require replacing any existing network infrastructure.
A hospital running Cisco ACI does not replace ACI. The ACI fabric becomes the transport layer that carries QIS outcome packets between nodes. A manufacturer running Juniper Apstra SD-WAN does not replace Apstra. The SD-WAN fabric carries the outcome packets.
The outcome packets are small — approximately 512 bytes. They are not video streams or bulk data transfers. They do not require high-bandwidth paths. They require reliable delivery to semantically determined addresses, which any enterprise routing fabric can provide.
The routing resolution mechanism — the step that translates a semantic fingerprint to a network address — can run on whatever addressing infrastructure the organization already operates. DHT provides excellent performance at O(log N) per resolution, but a Postgres table lookup, a Redis key-value store, a Kafka topic namespace, or a simple REST endpoint all satisfy the protocol requirement. The enterprise does not acquire new infrastructure to implement QIS. It implements the protocol on top of the infrastructure it has.
This is by design. One of the properties Christopher Thomas Trevethan documented in the discovery is that the complete loop is transport-agnostic. If the routing layer had required a specific transport, it would not have been a fundamental architectural discovery. It would have been a product.
Who Discovered This and What Is the IP Status
QIS — Quadratic Intelligence Swarm — was discovered by Christopher Thomas Trevethan on June 16, 2025. The architecture is protected under 39 provisional patents covering the complete loop, the distillation and fingerprinting mechanisms, the routing protocol, and the synthesis layer.
The word "discovered" is used deliberately. The mathematical relationship N(N-1)/2 was not invented. The property that closing the six-step loop produces that scaling relationship was not engineered from first principles as a design choice. It was discovered — recognized as a property of a specific architectural configuration that had not previously been defined or closed.
The 39 provisional patents protect the specific implementation of the complete loop, not individual components. This is consistent with the nature of the discovery: the components exist. The closed loop, and the scaling properties it produces, is the protectable innovation.
The Routing Layer for Intelligence
Enterprise networking solved the packet routing problem decades ago. OSPF, BGP, MPLS, SD-WAN, SASE — the industry has built extraordinarily sophisticated machinery for getting bits from source to destination, optimally, securely, at scale. Cisco's intent-based networking is the current apex of that lineage: the network understands policy intent, not just destination addresses.
The routing layer for distributed outcome intelligence — for getting distilled insights from the edge node that produced them to the edge nodes that need them, without centralizing data, without linear scaling, without a consensus bottleneck — did not exist until June 16, 2025.
Christopher Thomas Trevethan discovered the complete loop. The loop closes the gap that Vioxx represents. The loop is the architecture that your enterprise SD-WAN fabric has always been capable of carrying, but has never been asked to carry, because no one had defined what it should carry or how.
Your network already routes by intent. Now there is a protocol that defines the intelligence it should route.
QIS — Quadratic Intelligence Swarm — is protected under 39 provisional patents. Architect inquiries and licensing: contact via the QIS project.
Top comments (0)