01
ESRA
The runtime-neutral architecture: contracts, schemas, benchmarks, safety boundaries, and the protocol for one auditable improvement cycle.
Read the specificationEvolutionary Self-Recursive Architecture
Improve the improvement.
ESRA turns agent self-improvement from an assumption into a bounded, observable process. ESRA Agents makes that process portable across AI hosts—without giving autonomy a blank cheque.
OPEN SPECIFICATION · APACHE-2.0
Two layers, one contract
A specification and the implementation that proves it.
The boundary is deliberate: ESRA defines what reliable evolution means. ESRA Agents implements the portable skills, runtime behavior, evidence records, and thin host adapters.
02
ESRA Agents
The canonical cross-host implementation: five selective skills, a dependency-free runtime, guarded promotion, export, and adapters that stay thin by design.
Explore the implementationThe bounded loop
One cycle. Eight disciplined moves.
Select a stage to see how ESRA moves from observation to learning while preserving intent, evidence, and rollback.
cycle://esra/1.2
STAGE 01 / 08
Observe
Capture a concrete signal: a failure, anomaly, recurring friction, or opportunity. Record what happened without inventing an explanation.
OUTPUT evidence recordCONTROL no mutation
Design discipline
Autonomy that earns its next step.
Routine work bypasses ESRA. Significant improvement moves through explicit gates, and protected surfaces remain under human control.
Selective, not constant
Use ESRA when the stakes or learning value justify a cycle—not as ceremony around ordinary work.
Evidence before promotion
Proposals are tested against a declared hypothesis, evaluation method, and success threshold.
Exact revision control
Only the revision that was evaluated can be authorized for guarded local promotion.
Privacy by construction
Persist allowlisted metadata and hashes—not prompts, transcripts, tool payloads, secrets, or raw run IDs.
Thin host adapters
Portable contracts stay neutral while lifecycle events, permissions, and paths remain host-specific.
Rollback is part of learning
Canary rollout and recovery evidence are first-class parts of the improvement record.
Current evidence
Built to separate “works” from “proven.”
ESRA’s status language stays intentionally precise. Package checks, conformance, and isolated host tests are useful evidence; none of them silently become a universal production claim.
Native host maturity remains evidence-gated. Stable autonomous capability requires the shared host gate and a seven-day soak.
ESRA specificationverified
Portable core and evidence exportverified
Guarded skill promotionverified locally
OpenClaw native adapterprerelease
Hermes and Antigravity packagesgated
ChatGPT / Codex portable skillsavailable
Start with the contract
Make improvement inspectable.
Read the architecture, choose a host, and verify every claim at the boundary where it is supposed to hold.