A new paper from UC Berkeley, UCL, and Shanghai Jiao Tong University proposes a compelling vision: the Agentic Web, an internet where AI agents — not humans — are the primary operators. Users state goals in natural language; agents plan, coordinate, and execute across services autonomously.
The paper is thorough. It maps three dimensions of this new web (intelligence, interaction, economy), catalogs open challenges (trust, interoperability, reward design, catastrophic forgetting), and surveys the protocol landscape (MCP, A2A). What it doesn’t do is prescribe how to build the missing infrastructure.
That’s where things get interesting for us. Because the requirements the paper identifies — modular capabilities, competitive markets, decentralized trust, cross-platform portability, quantified fitness evaluation — are not hypothetical needs. They’re the exact mechanisms Rotifer Protocol has been building since v0.1.
The Paper’s Requirements vs. Existing Mechanisms
The Agentic Web paper articulates five structural requirements for a functioning agent ecosystem. Here’s how each maps to protocol-level mechanisms that already exist or are formally specified:
1. Modular, Transferable Capabilities
The paper says: Agents need composable capability units that can be shared and reused across the network.
What exists: The Gene model — atomic logic units satisfying three axioms (functional cohesion, interface self-sufficiency, independent evaluability). Genes carry their own I/O schema (Phenotype), are content-addressed by hash, and transfer between agents via Horizontal Logic Transfer.
2. Competitive Markets for Agent Capabilities
The paper says: “Agent Attention Economy” — services will compete for agent invocations the way websites compete for human clicks. Agent call frequency becomes the new traffic metric.
What exists: The Arena — a continuous ranking system where genes compete on standardized benchmarks. Fitness F(g) is a multiplicative function:
Agents prefer top-ranked genes. Low-fitness genes retire. The selection pressure is quantified, reproducible, and resistant to gaming through multidimensional scoring and sliding-window evaluation.
3. Decentralized Trust Infrastructure
The paper says: Agents operating autonomously need trust mechanisms that don’t depend on human verification at every step.
What exists: Two complementary systems:
- V(g) — a security score computed from static analysis (7 scanner rules, S-01 through S-07) that gates Arena admission. No test suite = no entry.
- L4 Collective Immunity — a network-wide threat ledger with temporal decay, defense sharing, and consensus-verified writes. A vulnerability detected by one agent generates defense fingerprints that protect the entire network.
4. Cross-Platform Interoperability
The paper says: Agents and their capabilities need to work across heterogeneous environments — different clouds, different runtimes, different platforms.
What exists: The Rotifer IR — genes compile to WASM with custom sections carrying metadata, schemas, and verification proofs. Before execution in a new environment, a formal negotiation protocol checks compatibility:
negotiate(gene.irRequirements, binding.capabilities)// → Compatible | PartiallyCompatible | IncompatibleThree Binding types (Local, Cloud, Web3) are already implemented. The abstraction eliminates “works on my machine” at the protocol level.
5. Reward Design That Resists Gaming
The paper says: Designing reward mechanisms that guide agent behavior without being exploited is an unsolved bottleneck.
What exists: F(g) uses a multiplicative model where any zero-valued dimension (security, reliability, coverage) zeros the entire score — you can’t compensate for a security hole with speed. Anti-gaming measures include Sybil detection, reputation discounting, sliding evaluation windows, and diversity-adjusted display ranking that penalizes monoculture.
What the Paper Covers That We Don’t
The Agentic Web paper is a full-spectrum vision document. It covers topics outside the scope of an evolution protocol:
- Search engine replacement — how agents will change information retrieval paradigms
- Labor market disruption — socioeconomic implications of agent automation
- Advertising model transformation — the shift from human attention to agent attention economics
- Recommendation systems for agents — how to surface relevant services to autonomous agents
These are important questions. They’re just not protocol-level questions. Rotifer focuses on the capability layer — how agent logic is created, evaluated, secured, and propagated — and leaves the application-layer questions to the teams building on top of the protocol.
What We Cover That the Paper Doesn’t
Conversely, several mechanisms in Rotifer address gaps the paper identifies as open challenges but doesn’t propose solutions for:
| Gap in the Paper | Rotifer Mechanism |
|---|---|
| ”How to prevent catastrophic forgetting?” | Modular genes evolve independently — updating one capability doesn’t overwrite others. HLT pulls genes by phenotypic need, not wholesale replacement. |
| ”How to measure capability quality?” | F(g) — a formal, reproducible fitness function with five dimensions and multiplicative zero-out. |
| ”How to ensure tool safety?” | V(g) security scoring with 7 static analysis rules, dual-threshold admission (F(g) ≥ τ AND V(g) ≥ V_min), and L0 constitutional immutability. |
| ”What’s the IR for agent capabilities?” | WASM + custom sections, with cross-binding negotiation protocol. |
| ”How to distinguish capability quality levels?” | Gene Fidelity: Native (full WASM sandbox) → Hybrid (WASM + controlled network) → Wrapped (API shim with metadata). Honest labeling enforced. |
Independent Convergence
The most interesting aspect of this alignment isn’t that Rotifer answers the paper’s questions — it’s that the questions were asked independently. The Berkeley/UCL/SJTU team arrived at their requirements through survey methodology and multi-institution analysis. Rotifer arrived at its mechanisms through bio-inspired protocol design. Neither referenced the other.
When independent research paths converge on the same structural requirements, it’s a signal that those requirements are real — not artifacts of a particular framing.
The Agentic Web paper maps the territory. Evolution infrastructure builds the roads.
Try it: npm i -g @rotifer/playground · rotifer.dev · Docs · Paper