Current production readiness
This is the stable entry point for deployment status. Dated reports describe the exact checks and limitations observed at the time; they are not perpetual production certifications.
Latest Ethereum mainnet deployment — 18 October 2026
The new 25-contract record publishes all addresses, exact deployed source 818b3a246871e4cd4dde86558dbb91ef82b15eef, 39 successful historical deployment receipts and the finalized closeout. All 25 runtime/source comparisons and 46 explicitly named state checks passed at provider-finalized block 26,221,285 (18:37:11 UTC); canonicality/finality were rechecked, and readback completed at 18:55:20 UTC. Etherscan observations are separately timed.
At that anchor, all eight managed modules were paused. Recorded ownership and the explicit governance/treasury getters match the intended addresses; the creator owns none of these 25 contracts. The configuration records 10% per-job collateral (1000 bps), a separate 1000 AGIALPHA eligibility stake, 5% fee, 1% burn, one-day commit/reveal windows and the pinned participant tax notice. Only the named getter list is a fresh state observation.
This is a separate stack. The historical record below is retained and its fixed-stake statement applies to the old deployment only. Current main and the deployed source have separate whole-tree identities; neither this publication nor source rc.14 substitutes the exact deployed revision. No wallet/client routing change, funding, unpause, migration or activation is enabled. Production approval and activation readiness remain false. Bounded source and getter checks do not replace exhaustive authority review, independent security review, provider/worker commissioning or live acceptance.
Historical Ethereum mainnet deployment — 12 October 2026
The deployment record and address directory now identify the existing mainnet stack, deployed from b4c5b66ea05a6bb27f1f1cb197f055c179bbd38e (source-v2.1.0-rc.4). The operator's saved readback reports 24 runtime-template matches, all eight managed modules paused under SystemPause, and Ledger control of SystemPause and three direct-owner modules. All 24 contract sources have exact-match Etherscan verification, including StakeManagerEscrow confirmed at 17:12 UTC on 12 October. The record keeps dated explorer evidence separate from runtime and operational approval. This is the AGIALPHA stack; it must not be confused with AGIJobManager/ENSJobPages and its USDC settlement.
The later configuration extract records all 24 exact runtime matches including immutables and the Ledger ownership handoff at provider-reported finalized block 26,179,827. Later operator screenshots record the 88,888,888 AGIALPHA reward cap; they are separate from that snapshot. The job stake remains a fixed 500 AGIALPHA, and a requested 10% rate is not implemented. The validator pool was empty and temporary-wallet EIP-7702 code remained present. The source release does not redeploy, migrate, unpause or open paid intake. These observations do not establish global authority cleanup or independent commissioning.
What can be used now
The public website provides the complete preserved demo collection, guided experiences, original diagrams, browser workbenches and a local job planner. The repository supplies executable local-chain workflows and an operator-admitted OpenClaw computer-work adapter. These capabilities require their documented environments and have distinct evidence boundaries.
The local evidence reviewer checks delivered artifact integrity against the original task and records an unsigned reviewer assessment. It does not authenticate provider provenance or satisfy independent acceptance by itself. The adapter rejects malformed UTF-8, invalid Unicode strings and text artifacts exceeding 128,000 UTF-8 bytes.
The container operations guide identifies every maintained and historical Dockerfile, its startup probe, and the additional setup needed for live operation. The validator review console supports an explicit human verdict, current round deadlines, and private browser recovery records; browser storage and downloaded backups are unencrypted. Neither a successful health check nor a structurally valid delivery establishes acceptance of the work.
SUCCESSOR Ω release candidate
The SUCCESSOR Ω local guide adds compiled missions, executable discovery, signed evaluation mechanics, durable state and portable knowledge. The public/local missions are synthetic rehearsals. The new mission-bound computer-work route and action broker refuse live dispatch; legacy admitted computer-work behavior is preserved. A local signed fixture is not I3 independent proof, and export/restoration grants no authority.
Read the acceptance matrix and security review before commissioning this subsystem. Its current local verification does not clear any existing production gate below.
Current deployment tooling
Use the staged Hardhat guide for new deployments and the plain-language coordinator guide for review. The current script validates public-network configuration and compiler evidence before transactions, commits the resolved plan on its coordinator, and hands off all eight managed modules paused. Submitted transactions and recovery checkpoints are retained in a private report and append-only journal. Tax metadata is installed before ownership transfer; explorer failures and pending governance actions remain explicit.
This does not retrofit existing coordinators or migrate deployed state. Historical direct coordinator entrypoints keep their unpaused behavior; use the supported script for a new paused deployment. Only governance may authorize unpausing after the gates below.
What a live deployment still needs
| Gate | Evidence needed |
|---|---|
| Release trust | Authorized maintainer signing identities and verified release artifacts |
| Merge enforcement | Active repository rules requiring the intended checks and review policy, verified against GitHub configuration |
| Security | Independent review, current dependency findings resolved or explicitly assessed, and validated provider configuration |
| Worker commissioning | An isolated real runtime with verified permissions, account selection, action/network policy, spending limits, stop behavior and representative success/rejection cases |
| Independent acceptance | Reviewers qualified for the work category, conflict disclosures, reproducible checks and actual buyer acceptance |
| Network commissioning | Reconcile the recorded mainnet inventory with current ownership/pause/immutable readback; complete identity/tax/stake checks, monitored settlement and recovery |
| Recovery | Reconciled uncertain actions, durable dispatch/settlement journals and a validated procedure for lost validator reveal secrets |
The agent:validator rehearsal example now persists private, deployment-scoped reveal secrets before broadcasting and reconciles retained records after restart. Its explicit fixed decision is a rehearsal input, not an independent content assessment; see the validator quickstart. The reviewed validator service now uses the current domain-bound protocol, exact round/specification/result review admission, pre-broadcast private records and restart reconciliation. Its structural evaluator cannot authorize a vote. Other validator paths still require separate recovery commissioning: apps/orchestrator/service.ts retains an in-memory commit map and gateway validators use a separate persisted-record format. These changes do not retrofit or certify those separate paths. Computer-work evidence requires independent acceptance and is not automatically approved by structural validation. The three Node release publishers now use delegated Storacha upload-agent credentials with CAR/root and upload-index checks; see the migration guide. Their live space and permissions still require commissioning. The browser legacy uploader and orchestrator HTTP-pinner defaults remain separate provider-migration surfaces. The static GitHub Pages site does not use those APIs.
The current contract commit entry point accepts an opaque hash without an expected-round argument. Client-side scope checks protect saved secrets and refuse inconsistent reveals, but they do not provide contract-level isolation for a transaction that mines across an administrative round reset. Reconcile in-flight transactions before reset/reselection; complete epoch-bound transaction rejection requires a separately versioned protocol change and deployment review. This update does not certify that mempool boundary.
The production release workflow enforces npm run release:audit-dependencies before publishing release artifacts. It audits all tracked npm and pnpm production lockfiles, preserves raw registry responses and exact input hashes, and fails on critical/high findings, malformed responses or unavailable audit evidence. A passing website deployment does not bypass this release gate. The rc.4 source candidate includes dependency updates and a provenance-checked maintained Braces depth patch; local full/production audits report no high or critical findings, while moderate and low findings remain. A registry audit does not certify a downstream patch. Exact-source integrity, adversarial/compatibility tests and final hosted qualification remain required, along with independent security review; forcing incompatible dependency versions is not remediation.
Verification records
Current paused mainnet deployment, 2026-10-18: exact deployed source, all 25 addresses, 39 deployment receipts and the bounded finalized closeout.
Recorded mainnet deployment and explorer status, 2026-10-12: all 24 addresses, deployed source, paused governance evidence and remaining commissioning work.
Dependency repair and upload-credential migration, 2026-10-11: maintained patch provenance, qualification boundaries and residual findings.
Deployment and operator update, 2026-10-10: paused handoff, configuration-bound recovery, governance call preparation and remaining gates.
Container, deployment and diagram update, 2026-10-08: current changes and validation boundaries.
Platform and website update, 2026-10-07: earlier integration, dependency refresh and validation scope.
Use current CI results for the exact candidate commit and rerun the documented checks when dependencies or deployment settings change. Do not infer production authorization from local simulation receipts, self-signed fixture evidence or a successful website deployment.