We approved the Aigarth evolution PEP on August 12. We closed out the build on August 13. Here is what shipped, why it matters, and what we are working on next.
The Organism, in one paragraph
An Organism is a single, addressable intelligence that lives in your Garden. It has a mutable genome, an episodic memory, a fitness history, and a lineage. You can fork it, mutate it, and watch it improve (or not) over time. The schema, the routes, the Garden view, and the marketplace listing are all live.
The Work Runtime, in one paragraph
The Work Runtime is the engine that turns Organism intent into executed work. You submit a work item, the scheduler picks a worker, the worker runs the algorithm, the verifier checks the result against three replicas, and the accountant emits the billing event. Five new tables, thirteen new routes, a four-tier compute model, and a v1 verification stack (replication + challenge + reputation) that catches the obvious attacks while we earn the right to add TEE and ZK.
What you can do today
- Create an Organism: one POST, returns a draft with a slug, a genome, and a creator.
- Fork and mutate: every Organism has a lineage. Every mutation is signed and auditable. The fitness history is append-only.
- Submit a work item: the Work Runtime picks the best worker, runs the algorithm, and verifies the result. Disputed results pause the credit settlement.
- List your Organism: the marketplace listing includes a lineage preview, a fork count, and a fitness max. Forks are billable.
- Read the fitness curve: the Garden view renders the Organism header, the lineage breadcrumb, the fitness curve, the experience stream, and an art-directed live neural field (clearly labeled as a visualisation, not a literal read of the genome).
What is next
Phase 28 (federated workers) is on the schedule for Q4 2026. Phase 29 (the Qubic OC processor) is on the schedule for Q1 2027. We are not changing the public roadmap; the one we published in the first post in this series is the one we are running against.
Two open questions, named out loud
We are not hiding the hard parts. Two open questions from the evolution ADR are still being decided:
- Verification upgrade trigger: when do we move from replication+challenge+reputation to TEE or ZK? Volume, value, adversarial rate, or a manual decision? We will pick one and document the function in a follow-up ADR.
- Dispute resolution: when all three replicas disagree, who decides who is right? Deterministic re-run on a high-reputation worker, manual admin review, or refund to the payer? Same deal: a follow-up ADR with a default.
The numbers
- 60+ new test cases shipped in this wave, on top of the 213 from Wave 2.
- 6 packages typecheck clean. The Work Runtime service (port 7012) is the new 12th service in the platform.
- 3 new ADRs (Organism primitive, Work Runtime, OC processor) plus the governance-migrations ADR from Wave 1.
- Zero regressions across the existing 200+ tests.
The full engineering record is in the docs. The roadmap is on the site. If you want to see the platform run, the dev environment is open.