ao (@aoTheComputer): Evolutionary forks are a new software primitive: PermawebOS Seed

Evolutionary forks are a new software primitive: PermawebOS Seed A few days ago we released a new framework for bootstrappable self-forking permaweb apps, and launched a new way to get involved. If you missed it, here's what it is and why it matters. In the age of increasingly capable agents, deploying a permaweb app now takes a matter of minutes, not hours or weeks. And the permaweb is the perfect substrate for an iterative application layer: Arweave as a permanent data lake, AO as its decentralized supercomputer, and now, the PermawebOS as the intuitive app layer that makes building everlasting applications instant. PermawebOS Seed is the public launch of an idea we have been working toward for a while: apps that are not only permanent, but forkable and iterative by design. The open source framework has been established for as long as software has existed, but what has been missing is a reliable path from discovering an app -> shipping a fork, without a long setup process, insider knowledge, or direct handholding from the original team. If software is supposed to be durable, it should remain reproducible after the original author has moved on, with all prior versions and provenance stored permanently. Apps built with the PermawebOS framework have a self-perpetuating lineage. Passing a deployed app URL to an agent and saying "look in the headers, fork this app and add <feature>" works like magic; inside every seed app there's a bundle of source code, scripts and agent instructions that make it foolproof for tools like Codex and Claude to know what to do next, and upload the final result to Arweave with a tag that points back to the previous seed. This produces apps with onchain versions and provenance built in, where anyone can discover a past iteration and branch off from it to build something new. Anatomy of a seed app A seed app is packaged so an LLM can reconstruct and execute the fork path from artifacts attached to the deployed app itself. At a high level: The app is loaded from an Arweave gateway. The code archive transaction is discoverable in headers/tags. AGENTS.md provides machine-readable instructions for setting up and modifying the project. Included scripts define how to deploy a fork. The fork records lineage by pointing to the seed app's ID. Software goes from ephemeral and siloed to permanent and interlinked. Why LLMs change the equation LLMs are typically just coding assistants inside one repo. The PermawebOS Seed framework uses them differently: for continuity across generations of apps. Given a deployed seed and the right metadata: they can discover the relevant code archive, follow project-specific instructions, implement requested changes, and publish a new permanent fork with lineage preserved. With tools that allow anyone to code an app in 5 minutes, it's easy to envision a less open future where software is forked onto a dev's local machine, expanded, and never shared. Iterations to seed apps automatically deploy to the permaweb with full attribution and genealogy, creating a flywheel of new apps that are discoverable by tracing forward from the seed TX-ID. That creates a stronger loop for the evolution of durable software. The fork becomes less of a one-off clone and more of a permanent public good. The PermawebOS Seed campaign is live now The campaign is already underway. Choose one of the seed apps below, open your local agent, and prompt it to create a fork. "Look in the headers for the code archive for arweave.net/<txid> and create a fork that adds <feature>." From there, the agent inspects the archive, uses AGENTS.md, runs deployment scripts, and publishes a new app on Arweave that references its seed. Seed apps: Public Square — arweave.net/kkTIOszueFOmJ2pBo3ymi5Qkw7xgVBYTGe4irFJnZ4M/ Groupthink — arweave.net/9184NcGqffERl4dlTguw0pUC8kZDIXRfXfdw2J3Yzss/ Fork Visualizer (lite) — arweave.net/MhgEk1YM167GpT5PCcYEWN28IWy86y3Wy1F3bsoZQJ0/ Campaign details: Top 2-4 forks each week: 35 $AR each 3 weeks, submissions due Thursdays 11:59pm ET Submit in the AO Discord: #permawebos-seed Share your build on X with #PermawebOS Submission format is simple: live app URL and a short description of what changed. A shift in how we build permanent apps PermawebOS Seed is the spark, but the bigger goal is a shift in how we build on the permaweb. Permanent apps that carry their own fork instructions, reproducible forks with explicit provenance back to the seed, and a visible lineage graph of how products evolve over time. In a future with thousands of seed apps all drawing from the same permanent data lake, we move from static software artifacts to preserving software evolution paths. That is the practical philosophy behind Seed: not just permanence of bytes, but permanence of the ability to continue building.