Rotifer v0.4: Cloud Binding — Genes Can Now Travel Across Developers

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 ins