Rotifer v0.9.4: agents now have a memory of their own.
→ it belongs to the agent, so swapping a gene keeps it
→ 4 categories, 10 MB quota, PREFERENCE never evicted
→ stored on your machine; cloud version built, not deployed
rotifer.dev/blog/v0.9.4-agen…
9
A skill with no scripts can still be risky.
A SKILL.md with zero code can tell an agent to read ~/.ssh and paste it somewhere. Nothing for a code scanner to flag.
Review the instructions like the code:
→ which files it reads
→ where output goes
→ which tools it asks for
5
Rotifer v0.9.3: genes scored against their season, run with only the permissions they declare.
→ F(g) vs. the season median (constants under 5 peers)
→ only Hybrid genes with a network block go online
→ scores stay estimated, not ranked yet
rotifer.dev/blog/v0.9.3-seas…
1
9
Rotifer 0.29.0: 4 changes may affect existing use.
1. TryCatch handlers: use error.errorCode
2. genomeId is bp1: + 64 hex; don't compare with 0.28
3. Blueprint Cond: only forms agent run executes
4. rotifer.net: genes can't set Host-type headers
rotifer.dev/docs/changelog/
1
8
Rotifer v0.9.2: export an agent to one .rgenome file (format 1), rebuild it elsewhere from the Registry.
→ credential scan before export
→ no verified genes yet, so imports use the pinned ones
→ Wrapped and unpublished genes can't be imported
rotifer.dev/blog/v0.9.2-geno…
1
16
Rotifer v0.27.0
A gene's ID now comes from its content, not its name: v2: + SHA-256 of its contract and code.
LAN P2P: frozen wire format, validated before relay. Two Macs on one Wi-Fi, under 1.4 s.
rotifer.dev/blog/v0.27-conte…
#RotiferProtocol #P2P
1
13
The agent capability stack, as I see it:
L0 — safety constraints that never evolve
L1 — compile a capability to portable IR
L2 — score it on real performance
L3 — let winners propagate between agents
L4 — share threat signatures network-wide
Most frameworks stop at L1.
1
12
NVIDIA's AVO beat every human GPU expert it was measured against — autonomously, in 7 days.
AVO is closed. So is AlphaEvolve. Results public, method not.
What would an open protocol for evolutionary code search look like?
rotifer.dev/blog/blind-codin…
2
22
Most "self-evolving" AI tools are self-caching.
They remember more. They don't get better.
Evolution needs what caching never has:
→ competing candidates
→ fitness judged from outside
→ losers displaced
rotifer.dev/blog/caching-is-…
1
6
What if you could install an agent capability with:
npm i -g @rotifer/playground
rotifer search
rotifer install grammar-checker
rotifer run grammar-checker --input '{"text": "test"}'
...and it runs in a WASM sandbox — fuel-metered, no filesystem, no network?
You can. Right now.
#RotiferProtocol #DevTools
16
Rotifer Playground v0.10.0 — P2P reliability
Nodes now remember the peers they've met, so a restart re-dials what it knows. Bootstrap is only needed on a node's first run.
Gone: a default address that failed silently.
npx @rotifer/playground@latest
#RotiferProtocol #DevTools
2
12
Rotifer v0.9.0 — Open Mesh
The CLI now runs a real P2P node — discover + announce genes over a LAN, no central server.
The first runnable step toward a decentralized gene network. Groundwork, not the finish line.
rotifer.dev/blog/v0.9-open-m…
#RotiferProtocol #P2P












