Ethereum mainnet deployment: 18 October 2026

25 deployed contracts, all exact-source verified. All eight managed modules remain paused. This is a dated deployment and bounded readback record, not operational activation or an independent security audit. Production approval and activation readiness remain false.

Exact source and observation times

• Deployed source: 818b3a246871e4cd4dde86558dbb91ef82b15eef, tree b1c3bb0f4b8d64e0d23376d6b6ef3722c4c67b0d. It is the source on draft PR #3986, not the current main branch or a release tag.
• Compiler: Solidity 0.8.37+commit.f401782d, Cancun, via-IR, 200 optimizer runs, IPFS metadata. Original Standard JSON SHA-256: a962576832d4540c4cd682f9251b6eed2a333c87a1ce5fa61ed5716e7091b891.
• State anchor: provider-reported finalized block 26,221,285, hash 0x4bd7698479db125e9a7e4f031571fd2844224f822a630ba22b40aea48fb592e6, at 2026-10-18 18:37:11 UTC. Canonicality and provider-finalized status were rechecked; readback completed 18:55:20.035 UTC.
• Explorer observations were separately timed between 18:54:46 and 18:55:16 UTC. Etherscan source metadata is not block-pinned chain state.

The public snapshot retains each exact address, runtime hash, fully qualified source, compiler-input hash, constructor encoding, observed owner and explorer comparison. The 39 successful deployment receipts retain creator nonces 308–346 and canonical receipt anchors from the completed deployment report. These are historical records, not instructions to sign or replay transactions.

What was checked

• 25/25 exact runtime comparisons, including constructor-dependent immutable values.
• 25/25 Etherscan source-content, compiler, settings, contract-name and constructor-argument comparisons; zero Similar Match, unverified or incomplete results.
• 46/46 explicitly named finalized-state getter checks passed.
• 8/8 managed modules were paused and owned by SystemPause. The creator owned none of these 25 contracts.
• IdentityRegistry and TaxPolicy pending owners were zero.

Five StakeManager-family verifications used minimal 37-source import closures. Closure proofs retained exact source contents, settings, executable creation/runtime bytes, metadata, ABI and link references. Immutable declaration and patched-value equivalence were checked; compiler-internal AST IDs may differ after pruning. Verification does not change deployed code.

Governance and configured policy

The owner-operated Ledger governance address is 0xd76AD27a1Bcf8652e7e46BE603FA742FD1c10A99. Chain readback proves the recorded address values, not physical key custody or an exhaustive absence of indirect permissions.

• SystemPause: 0x887782AE59A56D1E9923947A6784A4453193e303, governed by the address above.
• StakeManager treasury and FeePool governance: 0xa9eD0539c2fbc5C6BC15a2E168bd9BCd07c01201.
• FeePool treasury: 0xd76AD27a1Bcf8652e7e46BE603FA742FD1c10A99.
• Creator: 0x6c8B8897Fb6b08B4070387233B89b3E9A94eD00E; it is absent from the two explicitly checked treasury allowlists and owns none of the recorded contracts.

The completed configuration records 10% per-job collateral (1000 basis points), distinct from the 1000 AGIALPHA general minimum stake; fee 5%, burn 1%, employer/treasury slash split 10%/90%, validator slash reward 0%, and 86,400-second commit and reveal windows. Amounts use the existing 18-decimal AGIALPHA token. These economic settings come from the completed configuration record; the final readback freshly queried only the listed 46 getters. They are not all fresh economic observations.

TaxPolicy points to the immutable participant tax responsibilities policy. That policy does not promise a tax exemption or replace independent advice. Full ENS roots and configuration fields remain in the public snapshot.

Address directory

Source release and operational boundaries

This new stack is separate from the 12 October deployment. The old addresses, source, receipts, fixed-stake policy and obligations remain historical and unchanged. Publication does not migrate funds, extinguish obligations, alter old approvals or repoint a wallet/client profile.

The publication branch starts from main af71b175fb4930cfe6b4f5bfc29987fa863bda05. Comparison against deployed source 818b3a246871e4cd4dde86558dbb91ef82b15eef found identical contracts/, config/solidity-compiler.json and config/implementation-modules.json; deployment and qualification tooling differs. This limited source comparison is not whole-tree equality or a claim that compiling the release recreates the deployment artifact. The exact deployed source remains the authority for reproduction.

The public directory is informational. No live transaction route, deployment profile, funding, unpause, migration or production signing is enabled by this publication. Contracts are paused, not permanently locked; any later governance action requires its own authorization and applicable readiness evidence. Named getter checks do not establish exhaustive historical/indirect authority, ENS/operator readiness, full obligation reconciliation, or a security certification. Provider/worker commissioning, monitoring/recovery and independent acceptance remain separate gates. External audit and Sepolia rehearsal were not performed (owner-accepted omissions); automated and AI-assisted checks are not an external audit. See current readiness.

Evidence integrity

Original completed deployment report SHA-256: bad23bc71cde7a888f824b310d3ef7762ebc4ce6f1ac82eb8859521ff9986e7c.

Finalized source/governance readback SHA-256: ae80dd19133da0a3fbaacb4612f8a07df0c11fbd137615487311fb8ab5f8dec2.

Five-closure proof manifest SHA-256: d6430dee1c4059e1aec65448fc9112a7753178052acb0c7eff162c9fb7cda2ce.

These identify retained original evidence. Public JSON files are deliberately scoped projections and have their own checksums in the release inventory; their hashes must not be substituted for the original reports. Local paths, process/lease details and private operational data are excluded.