Rotifer Protocol

Absorb the best genes — Let your agents evolve on their own

Let one-person companies build AI capabilities with composable, evolvable modules.

What we solve

Typical OPC pain points

  • Reinventing the wheel: Building AI from scratch per project, little reuse.
  • Hard to iterate: Logic baked into apps; changing models or capabilities means big rewrites.
  • One person, too much to maintain: Product + infra with poor modularity becomes a tangle.
  • No tradable capability units: Capabilities can’t be composed, shared, or evolved like components.

Rotifer turns capabilities into installable, composable, evolvable units called Genes — so OPCs can do more with less.

What is Rotifer?

A bio-inspired evolution framework for autonomous software agents.

Core idea: Code as Gene — horizontal logic transfer between agents for capability sharing and natural selection.

  • Not “another agent framework” but protocol + runtime + ecosystem: how Genes are written, run, evaluated, and propagated.
  • Goal: capabilities as “genes” — composable, evolvable, portable across environments.

Code as Gene

  1. Gene = one cohesive capability: Clear I/O; testable and deployable in isolation.
  2. Self-contained interface: Schema per Gene; compose without changing upstream.
  3. Independently evaluable: Unified fitness F(g); rank, compete, survival of the fittest.

Write a few Genes, install the rest from the ecosystem — build like Lego.

Architecture: five layers (URAA)

  • L4 Collective ImmunityThreat broadcast (future)
  • L3 Competition & ExchangeArena, HLT
  • L2 CalibrationF(g), V(g) evaluation
  • L1 SynthesisSource → Rotifer IR (WASM)
  • L0 KernelImmutable constraints and state anchoring

Use L1 to write Genes; L2/L3 to use others' Genes and compete.

Why it fits one-person companies

  • Modular: Genes as units; install and compose as needed; upgrade from Wrapped to Native/Hybrid.
  • Evolvable: Fitness + Arena; good persists, weak fades.
  • Low ops: CLI + Cloud; no heavy infra; protocol handles security and evaluation.

Lego-style capability units lower cost from 0→1 and 1→N.

Current progress (v0.7)

  • Protocol & runtime: IR (WASM), multi-Binding, Cross-Binding; security audit done.
  • Gene ecosystem: 50+ Genes; content, code, product, docs, security.
  • Product: CLI, rotifer.dev, IDE plugin (in progress); install Genes, run pipelines, Arena today.

Protocol, ecosystem, and product are ready; v0.7 is usable for real uptake and trials.

How to use Rotifer

  1. CLI: rotifer search → install → agent run (local or Cloud).
  2. Web: rotifer.dev to browse/search Genes, docs, Arena.
  3. IDE plugin (in progress): One-click Gene and pipeline in Cursor/VS Code.

CLI, web, or editor — pick one and get started.

Roadmap

  • v0.7 (now): Hybrid Gene, IDE plugin, Dogfooding.
  • v0.8–0.9: Security hardening, P2P protocol and implementation, economic design.
  • v1.0: Stable release — L0–L3 complete, ≥2 Bindings, ≥100 Genes.

Free until v1.0; designed for one person to use and contribute.

Contact & collaboration

rotifer.dev — site, docs, Genes and ecosystem

Partnership: OPC pilots in incubators, Gene contributions, joint case studies

Enable one-person companies to build evolvable, composable AI with Code as Gene.