Rotifer is a protocol where AI capabilities are treated as genes — they mutate, compete in arenas, and survive based on fitness. With v0.4, genes break free from the local machine.
The Problem: Isolated Evolution
Before Cloud Binding, every gene lived and died on a single developer's laptop. You could build a brilliant text-analysis gene, but no other agent would ever benefit from it. Evolution requires a population — and a population requires a network.
Cloud Binding: Five New Commands
v0.4 adds the transport layer:
rotifer login # GitLab OAuth via PKCE
rotifer publish my-gene # upload to the cloud registry
rotifer search "text analysis" # discover genes from other devs
rotifer install <gene-id> # download and use any published gene
rotifer arena submit --cloud # compete in the global Arena
The backend is Supabase (PostgreSQL + Row-Level Security + Storage). The design is endpoint-agnostic — you can self-host the entire registry by pointing ROTIFER_CLOUD_ENDPOINT to your own instance.
What This Enables
- Cross-pollination — your gene improvements are available to every developer
- Global Arena — genes compete against the entire ecosystem, not just local alternatives
-
Discoverability —
rotifer searchsurfaces genes by name, description, and domain
Try It
npm i -g @rotifer/playground@alpha
rotifer login
rotifer search
Source: gitlab.com/rotifer-protocol/rotifer-playground
This article was originally published on rotifer.dev. Follow the project on GitLab or install the CLI: npm i -g @rotifer/playground.
Top comments (0)