Compare demonstrated behavior with outstanding signing, integration, security review and commissioning requirements. A simulation cannot replace authentic evidence for those gates.
# AGI Jobs v0 (v2) — Demo → Omni Concord Ascension Atlas
> AGI Jobs v0 (v2) is our sovereign intelligence engine; this module extends that superintelligent machine with specialised capabilities for `demo/OMNI-CONCORD-ASCENSION-ATLAS`.
## Execution status
This directory contains design documentation and preserved architecture diagrams; it has no standalone executable. For a related runnable workflow, use [atlas-conductor](../atlas-conductor/README.md). See the [complete demo guide](../README.md) for setup and evidence boundaries.
## Overview
- **Path:** `demo/OMNI-CONCORD-ASCENSION-ATLAS/README.md`
- **Module Focus:** Anchors Demo → Omni Concord Ascension Atlas inside the AGI Jobs v0 (v2) lattice so teams can orchestrate economic, governance, and operational missions with deterministic guardrails.
- **Integration Role:** Interfaces with the unified owner control plane, telemetry mesh, and contract registry to deliver end-to-end resilience.
## Capabilities
- Provides opinionated configuration and assets tailored to `demo/OMNI-CONCORD-ASCENSION-ATLAS` while remaining interoperable with the global AGI Jobs v0 (v2) runtime.
- Ships with safety-first defaults so non-technical operators can activate the experience without compromising security or compliance.
- Publishes ready-to-automate hooks for CI, observability, and ledger reconciliation.
## Systems Map
```mermaid
flowchart LR
Operators((Mission Owners)) --> demo_OMNI_CONCORD_ASCENSION_ATLAS[[Demo → Omni Concord Ascension Atlas]]
demo_OMNI_CONCORD_ASCENSION_ATLAS --> Core[[AGI Jobs v0 (v2) Core Intelligence]]
Core --> Observability[[Unified CI / CD & Observability]]
Core --> Governance[[Owner Control Plane]]
```
## Working With This Module
1. From the repository root run `npm install` once to hydrate all workspaces.
2. Inspect the scripts under `scripts/` or this module's `package.json` entry (where applicable) to discover targeted automation for `demo/OMNI-CONCORD-ASCENSION-ATLAS`.
3. Execute `npm test` and `npm run lint --if-present` before pushing to guarantee a fully green AGI Jobs v0 (v2) CI signal.
4. Capture mission telemetry with `make operator:green` or the module-specific runbooks documented in [`OperatorRunbook.md`](../../OperatorRunbook.md).
## Directory Guide
### Key Files
- `MISSION-PLAYBOOK.md`
## Quality & Governance
- Every change must land through a pull request with all required checks green (unit, integration, linting, security scan).
- Reference [`RUNBOOK.md`](../../RUNBOOK.md) and [`OperatorRunbook.md`](../../OperatorRunbook.md) for escalation patterns and owner approvals.
- Keep secrets outside the tree; use the secure parameter stores wired to the AGI Jobs v0 (v2) guardian mesh.
## Next Steps
- Review this module's issue board for open automation, data, or research threads.
- Link new deliverables back to the central manifest via `npm run release:manifest`.
- Publish artefacts (dashboards, mermaid charts, datasets) into `reports/` for downstream intelligence alignment.
{"revision":"5b4cebb309a83a7a6749d8911d8bf96a1921e042","sources":[{"file":"demo/OMNI-CONCORD-ASCENSION-ATLAS/README.md","content":"# AGI Jobs v0 (v2) — Demo → Omni Concord Ascension Atlas\n\n> AGI Jobs v0 (v2) is our sovereign intelligence engine; this module extends that superintelligent machine with specialised capabilities for `demo/OMNI-CONCORD-ASCENSION-ATLAS`.\n\n## Execution status\n\nThis directory contains design documentation and preserved architecture diagrams; it has no standalone executable. For a related runnable workflow, use [atlas-conductor](../atlas-conductor/README.md). See the [complete demo guide](../README.md) for setup and evidence boundaries.\n\n## Overview\n- **Path:** `demo/OMNI-CONCORD-ASCENSION-ATLAS/README.md`\n- **Module Focus:** Anchors Demo → Omni Concord Ascension Atlas inside the AGI Jobs v0 (v2) lattice so teams can orchestrate economic, governance, and operational missions with deterministic guardrails.\n- **Integration Role:** Interfaces with the unified owner control plane, telemetry mesh, and contract registry to deliver end-to-end resilience.\n\n## Capabilities\n- Provides opinionated configuration and assets tailored to `demo/OMNI-CONCORD-ASCENSION-ATLAS` while remaining interoperable with the global AGI Jobs v0 (v2) runtime.\n- Ships with safety-first defaults so non-technical operators can activate the experience without compromising security or compliance.\n- Publishes ready-to-automate hooks for CI, observability, and ledger reconciliation.\n\n## Systems Map\n```mermaid\nflowchart LR\n Operators((Mission Owners)) --> demo_OMNI_CONCORD_ASCENSION_ATLAS[[Demo → Omni Concord Ascension Atlas]]\n demo_OMNI_CONCORD_ASCENSION_ATLAS --> Core[[AGI Jobs v0 (v2) Core Intelligence]]\n Core --> Observability[[Unified CI / CD & Observability]]\n Core --> Governance[[Owner Control Plane]]\n```\n\n## Working With This Module\n1. From the repository root run `npm install` once to hydrate all workspaces.\n2. Inspect the scripts under `scripts/` or this module's `package.json` entry (where applicable) to discover targeted automation for `demo/OMNI-CONCORD-ASCENSION-ATLAS`.\n3. Execute `npm test` and `npm run lint --if-present` before pushing to guarantee a fully green AGI Jobs v0 (v2) CI signal.\n4. Capture mission telemetry with `make operator:green` or the module-specific runbooks documented in [`OperatorRunbook.md`](../../OperatorRunbook.md).\n\n## Directory Guide\n### Key Files\n- `MISSION-PLAYBOOK.md`\n\n## Quality & Governance\n- Every change must land through a pull request with all required checks green (unit, integration, linting, security scan).\n- Reference [`RUNBOOK.md`](../../RUNBOOK.md) and [`OperatorRunbook.md`](../../OperatorRunbook.md) for escalation patterns and owner approvals.\n- Keep secrets outside the tree; use the secure parameter stores wired to the AGI Jobs v0 (v2) guardian mesh.\n\n## Next Steps\n- Review this module's issue board for open automation, data, or research threads.\n- Link new deliverables back to the central manifest via `npm run release:manifest`.\n- Publish artefacts (dashboards, mermaid charts, datasets) into `reports/` for downstream intelligence alignment.\n","format":"text","sha256":"d8f8d441e52839da6877937442057f4a79bc33f50e34b89ccac369c2003f1af8","bytes":3028,"download":"/AGIJobsv0/examples/d8f8d441e52839da-README.md","source":"https://github.com/MontrealAI/AGIJobsv0/blob/5b4cebb309a83a7a6749d8911d8bf96a1921e042/demo/OMNI-CONCORD-ASCENSION-ATLAS/README.md"},{"file":"demo/atlas-conductor/README.md","content":"# AGI Jobs v0 (v2) — Demo → Atlas Conductor\n\n> AGI Jobs v0 (v2) is our sovereign intelligence engine; this module extends that superintelligent machine with specialised capabilities for `demo/atlas-conductor`.\n\n## Run the local mission\n\nComplete the [pinned root setup](../../docs/START_HERE.md#reproduce-the-local-baseline), then run from the repository root:\n\n```bash\nnpm run demo:atlas-conductor:local\n```\n\nThis launches a disposable loopback chain, deploys the actual modular contracts, and settles four scenario jobs. The mission retains its configured validator committees (5 for every job validators), commits and reveals votes, checks each finalized job, and verifies worker/validator payouts. Open `reports/localhost/atlas-conductor/atlas-conductor-report.md`; transaction evidence is under `receipts/jobs/`.\n\nThe work, identities, and token are local fixtures. Real contract settlement does not demonstrate delivery of the physical projects described by the mission. No live wallet or provider credentials are needed. Anvil is optional; the installed Hardhat node is the fallback. The node stops when the command finishes. Later live owner commands require a separately managed test deployment.\n\nIf port 8545 is occupied, run `DEMO_PORT=18545 npm run demo:atlas-conductor:local`. Existing nodes are preserved. A unique `AURORA_REPORT_SCOPE` preserves separate runs; defaults reuse the mission's namespace. Allow several minutes for initial compilation. Missing configurations, duplicate receipt names, incomplete settlements, and placeholder transaction hashes fail visibly.\n\n[All demos and troubleshooting](../README.md)\n\n## Overview\n- **Path:** `demo/atlas-conductor/README.md`\n- **Module Focus:** Anchors Demo → Atlas Conductor inside the AGI Jobs v0 (v2) lattice so teams can orchestrate economic, governance, and operational missions with deterministic guardrails.\n- **Integration Role:** Interfaces with the unified owner control plane, telemetry mesh, and contract registry to deliver end-to-end resilience.\n\n## Capabilities\n- Provides opinionated configuration and assets tailored to `demo/atlas-conductor` while remaining interoperable with the global AGI Jobs v0 (v2) runtime.\n- Ships with safety-first defaults so non-technical operators can activate the experience without compromising security or compliance.\n- Publishes ready-to-automate hooks for CI, observability, and ledger reconciliation.\n\n## Systems Map\n```mermaid\nflowchart LR\n Operators((Mission Owners)) --> demo_atlas_conductor[[Demo → Atlas Conductor]]\n demo_atlas_conductor --> Core[[AGI Jobs v0 (v2) Core Intelligence]]\n Core --> Observability[[Unified CI / CD & Observability]]\n Core --> Governance[[Owner Control Plane]]\n```\n\n## Working With This Module\n1. Follow the [root setup](../../docs/START_HERE.md#reproduce-the-local-baseline) to install the pinned toolchain and locked dependencies.\n2. Inspect the scripts under `scripts/` or this module's `package.json` entry (where applicable) to discover targeted automation for `demo/atlas-conductor`.\n3. Execute `npm test` and `npm run lint --if-present` before pushing, then inspect CI for the exact commit.\n4. Capture mission telemetry with `make operator:green` or the module-specific runbooks documented in [`OperatorRunbook.md`](../../OperatorRunbook.md).\n\n## Directory Guide\n### Key Directories\n- `bin`\n- `config`\n### Key Files\n- `env.example`\n- `project-plan.json`\n- `RUNBOOK.md`\n\n## Quality & Governance\n- Every change must land through a pull request with all required checks green (unit, integration, linting, security scan).\n- Reference [`RUNBOOK.md`](../../RUNBOOK.md) and [`OperatorRunbook.md`](../../OperatorRunbook.md) for escalation patterns and owner approvals.\n- Keep secrets outside the tree; use the secure parameter stores wired to the AGI Jobs v0 (v2) guardian mesh.\n\n## Next Steps\n- Review this module's issue board for open automation, data, or research threads.\n- Link new deliverables back to the central manifest via `npm run release:manifest`.\n- Publish artefacts (dashboards, mermaid charts, datasets) into `reports/` for downstream intelligence alignment.\n","format":"text","sha256":"c994fa126b2139acce25e0f626d74e2615eab7de77182b549a29f91f4a8ae54d","bytes":4144,"download":"/AGIJobsv0/examples/c994fa126b2139ac-README.md","source":"https://github.com/MontrealAI/AGIJobsv0/blob/5b4cebb309a83a7a6749d8911d8bf96a1921e042/demo/atlas-conductor/README.md"},{"file":"docs/production/readiness-2026-10-03.md","content":"# Production readiness review — 2026-10-03\n\nReviewed baseline: `7049353e1ee13c19b97365b269f9a9ac1800434c`, with the accompanying readiness-hardening changes. This is an engineering verification record, not an independent security audit or a claim that the full vision has been proven in production.\n\n**Decision: suitable for continued local development and demonstration; not ready for a mainnet release.** The modular candidate passes the contract-size gate; release trust and the remaining integration/configuration gates are not complete. Existing features, examples, and diagrams are preserved.\n\n## Verified locally\n\nThe subsequent [production rehearsal](rehearsal.md) executes signing rejection tests, real HTTP adapter fault injection, adversarial contract checks, and three local settled jobs as one isolated workflow. Its signed report explicitly records simulation evidence, `productionApproved: false`, and `independentReview: false`. It makes the remaining handoff reproducible without converting simulated evidence into production authorization.\n\n| Check | Result |\n| -------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |\n| Supported root toolchain | Node 22.23.3, npm 10.8.2; toolchain and lockfile checks pass |\n| Solidity compilation | 267 source files compile with the repository's default optimizer/viaIR settings |\n| Full `npm test` | Pretest checks and 581 Hardhat tests pass with contract-size limits enforced |\n| Python repository suite | 246 passed, 1 skipped |\n| Focused recursive-model suite | 13 passed |\n| New release guard regressions | 12 passed: signed/unsigned/untrusted/wrong-commit tags, shell metacharacters, malformed keys, and bytecode-size boundaries and empty artifacts |\n| Gateway and orchestrator builds and runtime packaging | Pass; 4 packaging regressions pass |\n| Owner console production build | Pass |\n| CI context synchronization, summary coverage, formatting and targeted lint | Pass |\n| Demo gallery | 41 runnable suites exercised; three initial failures repaired and all affected suites pass on rerun |\n| Root README flowcharts | All 17 Mermaid blocks identical to the reviewed baseline |\n\nThe initial demo runner skipped some suites when their independent toolchains were absent. The follow-up below adds specific Foundry, Prisma, and browser checks; it does not establish that every skipped suite passed. Docker is unavailable locally, so container builds and vulnerability scans require the pull request's workflows.\n\n## Follow-up verification and repairs\n\nThe first CI cycle at `00fa77e4b6282dde4ead8ce1dcfc28c34f365296` passed 38 workflows, including the primary containers, Torch tests, contract CI, fuzzing, static analysis, and root browser workflows. Application-image builds and CULTURE failed; two long-running demo workflows were cancelled, and core CI was still running when checked. These results belong to that commit, not to subsequent fixes.\n\n- Upgrade all four Next.js manifests/locks to the September security release **15.5.27**. Enterprise portal, Onebox, and validator UI production builds pass. Validator UI now uses strict TypeScript checking. Repair the application-image build contexts, portal dependency installation, digest/provenance subjects, and promotion order so `latest` follows the OS scan.\n- Repair CULTURE's independent pnpm dependencies, ESLint 9 compatibility, npm image lockfiles, shared-code bundle, Prisma generation checks, Compose anchors/build contexts, and static-server packaging. Its three service builds and lint checks pass. Existing source-format checks required mechanical formatting changes; no workflow screens or diagrams were removed.\n- Require authenticated write requests when configuring an on-chain arena operator. Validate paired operator/address settings and canonical/legacy address aliases. Obtain round IDs from the confirmed transaction's `RoundStarted` event instead of a preflight call that could race another transaction.\n- Forward rejected Express 4 handlers, await startup recovery, clear completed-operation timers, and write persistent state through serialized atomic replacements. Corrupt or unreadable state now blocks startup. Failed replacement preserves the previous state file and does not poison subsequent saves.\n- Make studio preview mode explicit (`VITE_DEMO_MODE=true`), label simulated results, and make it issue no service requests. Service mode exposes failures rather than inventing successful uploads, mint receipts, jobs, or owner changes. Correct the GraphQL artifact query, escape tooltip content, and improve graph-label contrast. The operator token is kept in tab memory and sent only to the orchestrator.\n\n| Follow-up check | Result |\n| ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ |\n| Root pretest checks and Hardhat suite | Pass; 571 Hardhat tests |\n| CULTURE Foundry v1.4.4 | 26 tests pass |\n| CULTURE Hardhat | 3 tests pass |\n| CULTURE arena | 58 tests pass; 100% lines and 96.51% branches in its configured coverage scope |\n| Compiled arena runtime | Startup, health endpoint, rejected missing/wrong credentials, authenticated validation, and graceful SIGTERM pass |\n| CULTURE indexer | 2 tests pass; coverage gate fails |\n| CULTURE studio API | 20 tests pass; 98.07% lines, 82.14% branches in the configured API-helper scope; branch gate fails |\n| CULTURE browser walkthrough | Draft, preview upload/mint/job, arena, and error-state checks pass; zero uncaught browser errors and zero preview API requests |\n| Workflow syntax | Actionlint passes for both edited workflows |\n\nThe corrected Vitest thresholds use **90**, not **0.9** (which meant 0.9%). Indexer coverage is 24.54% lines, 57.74% branches, and 43.24% functions. Arena coverage excludes several adapters and the service implementation in the existing configuration; its percentage must not be presented as whole-service assurance. Browser walkthroughs exercise the explicit preview and error behavior, not real economic settlement.\n\nThe CULTURE gas snapshot is stale, and the lifecycle (682,540 gas versus 500,000 budget) and misconduct (612,729 versus 520,000) scenarios exceed committed budgets. Those budgets were not raised. Its Compose/Cypress commissioning still requires deployment to real dependency contracts, valid operator roles, and resolution of the existing duplicate-service/environment setup. Studio requests for LLM generation, IPFS upload, artifact minting, job creation, and owner controls need real provider implementations; several backend adapters also remain simulations. These are release blockers in addition to the mainnet items below.\n\n## Release publication follow-up\n\nBefore the modular refactor below, a subsequent release review confirmed that the authorized-signers check and production size gate both failed. At that stage, no tag or release was published and the changes were still in PR #3876. The public repository had no release records or remote tags; no version was invented to conceal the blocked state. The main-branch follow-up below records the subsequent merge.\n\nThe release workflow now requires successful main-branch CI for its exact commit, a matching signed-tag workflow ref, contract verification before container/npm publication, and scans of both image architectures before signing immutable digests. GitHub assets stay in draft until image promotion succeeds. Prereleases cannot move `latest`, and the separate container workflow no longer promotes tag builds. Current Cosign 3.1.3 bundle signing preserves the detached signature/certificate assets, adds the complete verification bundle, and uses the required attestation permission. Downloaded checksums no longer require a `dist/` subdirectory. The signing guide now uses valid SSH registry instructions and the correct GitHub provenance verification command.\n\nAdditional validation:\n\n- CULTURE installs, lints, and builds in a clean temporary tree without the root npm dependencies. The GitHub arena lint failure came from an undeclared body-parser type dependency; the server now uses Express's built-in JSON parser with the same 1 MiB limit.\n- Studio API coverage now **passes**: 25 tests, 100% lines, 95.23% branches, 100% functions. This supersedes the earlier studio branch failure above; indexer coverage and gas failures remain open.\n- All 30 release regressions pass (12 prior signing/size checks plus 18 CI/publication checks). They cover stale/foreign/missing/pending/failed evidence, pagination and API failures, dependency ordering, prerelease promotion, draft publication, and portable checksums.\n- Application-image CI at `dab6bae0b37ae2996bc3f02a52ec7c2c1f243f05` passed both console and portal builds/scans ([run](https://github.com/MontrealAI/AGIJobsv0/actions/runs/37132344290)). Its CULTURE job still failed on the gas snapshot and the arena lint issue repaired here. New-head CI must be checked independently.\n\nPublishing a production release still requires review of the modular refactor, a verified maintainer public key and maintainer-signed tag, real deployment/governance configuration, completed integration/coverage/gas work, and passing CI. The private signing key must remain with the maintainer.\n\n## Repairs included\n\n- The scheduled Torch workflow installed the optional Streamlit dashboard after FastAPI. That second installation replaced Starlette 0.41.3 with an incompatible 1.7.0 and caused nine collection errors. Headless model requirements are now separate, installed with the platform requirements in one resolver invocation, followed by `pip check`. Relevant pull requests trigger this check.\n- Compiled runtime packaging now includes the gateway config helpers and gRPC schema. The gateway and orchestrator launch commands now point to their emitted server entrypoints; compilation alone had not caught these startup failures.\n- Node 20 pins were updated to supported Node 22.23.3 across the root toolchain, workflows, Dockerfiles, and explicit-version instructions. The Node doctor no longer reports an exact matching pin as a mismatch.\n- The container workflow now uses supported primary base images and a current Trivy scanner, gives its matrix jobs stable required-context names, scans PR builds, and scans both published architectures before promoting a candidate to `latest`. Existing application-library scans remain advisory; green OS scans are not a complete dependency-security sign-off.\n- Release verification parses actual OpenSSH public keys, invokes Git without shell interpolation, checks trust and the checkout commit, and applies to manual releases too. Invalid placeholder signing bytes no longer pass validation.\n- Production releases and mainnet preparation enforce EIP-170 runtime and EIP-3860 initcode limits. Invalid or empty Safe-plan JSON is no longer replaced with a successful-looking empty object.\n- The CULTURE CI dependency cache now resolves pnpm inside its own workspace, after Node and Corepack setup. The root npm package-manager declaration had blocked setup before any demo checks ran.\n- Demo tests isolate inherited environment variables and network probes. The reasoner subprocess disables host startup customizations with Python `-I -S`. Its tests use the configured default memory allowance and separately assert failure under memory exhaustion. This subprocess is still a trusted demonstration harness, not a security boundary for arbitrary hostile programs.\n\n## Mainnet size gate\n\nRun `npm run compile`, then `npm run release:check-size`. The modular candidate passes for **66** non-mock deployable v2 artifacts, including ten fixed implementations. The [deployment architecture guide](fixed-implementations.md) explains the constructor changes, shared layouts, direct-call protections, domain separators, and paused/resumable staging.\n\n| Contract | Previous runtime bytes | Candidate runtime bytes | Candidate initcode bytes |\n| --- | ---: | ---: | ---: |\n| JobRegistry | 48,855 | 8,004 | 11,847 |\n| StakeManager | 45,337 | 7,881 | 10,396 |\n| ValidationModule | 28,199 | 6,368 | 8,980 |\n| Deployer | 234,082 | 10,116 | 10,239 |\n\nNormal Hardhat tests now set `allowUnlimitedContractSize: false`, use automatic gas estimation, and enforce a 30 million block gas limit. Constructor arguments also contribute to actual initcode size. Existing job, staking, validator, dispute, settlement, tax, and governance features remain. The original 17 root README Mermaid blocks remain unchanged.\n\n## Modular candidate verification\n\nThe final clean default build and `npm test` pass: **267 Solidity sources** and **581 Hardhat tests**, including the complete pretest sequence. The ten new compatibility/deployment tests preserve all prior controller functions, events, errors, and storage offsets; verify identical implementation layouts and controller-specific voting domains; enforce direct-call and governance checks; and exercise paused, interrupted, resumed, and completed staging with per-transaction gas limits.\n\n- **66** non-mock deployable v2 artifacts pass EIP-170/EIP-3860 size checks.\n- **59** selected Foundry staking/slashing/validator/deadline regressions pass with 256 fuzz runs.\n- **13** tests across all five invariant suites pass, covering escrow, fee pools, staking accounting, and pause/governance controls.\n- **4** validation-finalization tests pass, including both finalization gas scenarios.\n- **30** release/signing/size regression tests pass. Toolchain/lock integrity, Solidity lint, workflow syntax, and required formatting checks pass.\n- Foundry output and cache are isolated from Hardhat artifacts, avoiding incompatible build-info files in subsequent test runs.\n- All **17** root README flowcharts remain byte-for-byte identical to the reviewed baseline.\n\nFresh-checkout CI follow-up:\n\n- Both prebuilt demos now bundle the ten fixed implementations and pass with an empty Hardhat artifacts directory. The supply-chain transcript passes both schema checks; the labour-market transcript retains its timeline, owner controls, scenarios, and portfolios. A compatibility regression requires the bundled ABI and creation bytecode to match the compiled contracts.\n- The owner CLI shebang is restored to the first line; its complete local deployment, governance, pause, and resume rehearsal passes. This repairs the shared cause of seven deterministic-demo workflow failures.\n- All **13** focused modular/deployer tests and **6** Slither-policy regressions pass. The earlier full-suite result remains 581 tests; the new bundle regression adds one test.\n- Slither 0.10.4 analyzes 266 contracts with 92 detectors. The validator now reads rule-level security severity; previously, all 816 results were labeled warnings and high-impact findings escaped enforcement. The 27 high-severity findings match scoped, documented exceptions. See the [static-analysis review](static-analysis-review.md), including the existing randomness risk and required production review.\n\nThe root version and changelog prepare **v2.0.0** because constructor setup and whole-stack deployment change. No release or signed tag has been published. The authorized-signers check still rejects the committed example keys. At the prior PR head `c420ecc7caf2b731eaa40d48fccebcc03dbd82a4`, CULTURE CI still failed; new candidate CI must be evaluated on its own commit.\n\n## Local lifecycle completion and launcher safety\n\nThe follow-up to PR #3878 repairs the separate ASI Take-Off local failure and exercises employer settlement. Staged deployment now authorizes JobRegistry tax acknowledgements and connects StakeManager to ValidationModule. The driver preserves the committed reveal salt, completes identity ownership acceptance and validator selection, uses fresh RPC state with buffered gas estimates, and checks the decoded final job state. Its mock token supports the burn needed by the configured settlement path. A missing creation event or blocked identity setup fails the run instead of producing a successful empty mission.\n\nReport namespaces default to the mission scope, so running ASI Take-Off preserves AURORA receipts. Explicit namespace overrides remain available, with traversal rejected. Local launchers refuse occupied ports, validate a localhost RPC endpoint and chain ID 31337, bind explicitly to localhost, and stop only the node they started. `DEMO_PORT` selects an alternate port. Compilation is incremental and serialized. The workflows also run when contract/deployment dependencies change and retain receipts when a demo fails. [AURORA](../../demo/aurora/README.md#run-the-local-job-lifecycle) and [ASI Take-Off](../../demo/asi-takeoff/README.md#retained-local-contract-walkthrough) now provide direct walkthroughs and report locations.\n\nVerification uses Node 22.23.3 and npm 10.8.2 with the production compiler profile. Contract-size checks pass; Deployer runtime/initcode are **10,116 / 10,239 bytes**. The **54 standalone Node checks** pass, including occupied-port preservation, endpoint/chain validation, and existing release safeguards. Toolchain/lock checks, required formatting, shell syntax, workflow lint, and focused Solidity lint pass. All **17 root README flowcharts**, plus the two edited demo diagrams, are unchanged.\n\n**14 focused contract tests pass**, covering deployment wiring/mode checks, immutable-implementation compatibility, and mock-token burn accounting. The three-job ASI Take-Off run passes on Anvil; the one-job AURORA run passes using the Hardhat fallback. Both generate reports and per-stage receipts after checking successful final settlement. These runs use mock tokens, configured identities, and demonstration work/results, while executing actual local v2 contracts.\n\nThe full root test attempt ended with exit **137** at the validator reservoir tests under local memory pressure; it is not a passing full-suite result. Exact-commit CI remains required. Maintainer signing validation still rejects the committed example key. These fixes do not establish independent security review, real provider execution, production identities, or paid settlement on the intended network.\n\n## Remaining production work\n\n### CULTURE gate repairs after PR #3877\n\nThe review continued from merged main `ff8db39d4e2a47885d1a63a24925a8764aa1181f`. All 14 other triggered workflows passed at that commit, including core CI, contract CI, containers, application-image provenance, Torch, browser E2E, fuzzing, and static analysis. CULTURE services passed, while its stale gas snapshot stopped downstream checks.\n\n- Fix the arena's signed-difficulty magnitude comparison: large unsigned limits no longer become negative, and `int32.min` is handled without negation overflow. **39 Foundry tests** pass, including restored submission/authorization/operation-sequence tests and new configuration, ownership, atomicity, and boundary cases.\n- Use Foundry minimum-IR coverage and isolate production Foundry, coverage, and Hardhat artifacts. Enforce the **unchanged 90% line threshold for each production contract** using the actual Foundry LCOV report; reject missing/invalid evidence. CultureRegistry reaches **94.06%**, SelfPlayArena **97.44%**, and both have 100% function coverage. The separate three-test Hardhat report remains supplemental (62.93% aggregate production-contract lines); it is not presented as 90% coverage.\n- Refresh the obsolete gas snapshot and explicitly revise the lifecycle/misconduct ceilings to **750,000 / 675,000** for the existing integrated scenarios. Measured costs are **682,641 / 612,935**. The prior ceilings predated the JobRegistry/ValidationModule fixture integration. The [gas review](../../demo/CULTURE-v0/gas-snapshots/REVIEW-2026-10-03.md) preserves the old values and rationale. Fuzz tests still run; exact gas comparison covers deterministic tests.\n- Slither 0.10.4 reports zero findings after narrow source annotations explain four reviewed findings: validation selection remains owned by the ValidationModule, zero revokes the designated relayer, and artifact timestamps are metadata rather than authorization/existence conditions. Existing entropy and governance assumptions remain subject to independent review.\n- **27 indexer tests** pass with **92.50% lines/statements, 90.24% branches, and 94.66% functions**, including ordered finality-aware live replay and failure retries. Normalize PageRank when the graph grows and stop on external-validator failure; preserve the previous verified metrics. A compiled runtime against a localhost chain verifies migrations, ingestion of three actual artifact events, graceful shutdown, and restart without duplicates. Deep reorganization/orphan reconciliation is still not established.\n- Repair deployment-script config compatibility, module-relative paths, artifact lookup, ethers v6 chain lookup, dependency-code checks, strict failure reporting, and comment-preserving atomic environment updates. Six helper regressions and script type-checking pass. Add an explicitly local fixture bootstrap and repair the single-stack Compose/Cypress path, pinned dependency images, localhost bindings, writable data volumes, Python runtime, and Prisma migrations.\n\nAt `a87ff65b813f4ba2326eadc6353943fd17555001`, [CULTURE CI](https://github.com/MontrealAI/AGIJobsv0/actions/runs/37150017071) passes all six jobs. The actual Docker stack starts five healthy services, validates NetworkX influence results, indexes three on-chain seed artifacts, and rejects unauthenticated writes. The Chrome 154 UI smoke passes; its provider responses are explicitly intercepted fixtures. [Core CI](https://github.com/MontrealAI/AGIJobsv0/actions/runs/37150017016), contract CI, fuzzing, static analysis, container builds, and the root browser workflows also pass at that commit. The separate ASI Take-Off local workflow exposed a stale RPC nonce during rapid transactions; the shared AURORA driver now disables the provider's short-lived cache and awaits asynchronous impersonated-signer lookup. Subsequent-head CI must be evaluated separately.\n\nThe final local follow-up completes three ASI Take-Off mission jobs on Anvil, each with validator selection, three commitments and matching-salt reveals, employer finalization, token burns, payouts, and transaction receipts. The driver now fails if identity setup or settlement is skipped. This rehearsal uses public local keys and a fixture token; it does not establish production economics. The optional Thermostat is absent from this deployment and is explicitly reported as skipped.\n\nStaged deployment now authorizes registry tax acknowledgements and wires validator stake locking. Separating deployment-mode checks from common wiring reduces Deployer runtime to **10,116 bytes**. All 66 deployable artifacts pass the size gate. Both deployment paths export the ten actual implementation addresses; the staged path also records all 14 component constructor argument lists and source names, including when resuming an already registered stack. Its explorer calls use those creation records. Legacy direct-deployment constructor argument lists have also been reconciled with their creation calls; actual explorer publication still requires network commissioning.\n\nThe six PR review findings are addressed: idle scans persist a separate completed-block checkpoint (without advancing across a failed batch); local Compose removes inherited fixture settings; generated environment/manifest files are ignored; production scripts preserve explicit environment overrides; indexer startup loads dotenv before choosing its database and supports SQLITE_PATH; and deployments export implementation addresses. **30 indexer tests** pass the unchanged coverage thresholds, eight quality-gate/environment tests pass, and the compiled startup entrypoint migrates and serves a database configured solely through `.env`. The deployment compatibility tests cover resumed constructor records against the coordinator's creation-code hashes. Root static analysis has no unapproved high-severity findings (27 reviewed baseline exceptions). All 17 root README diagrams remain unchanged.\n\nLocal grouped contract runs covered 581 of 582 tests before the mock-token regression was added; the reservoir-selection test exceeded local memory. At `ebb89ca7cc6f9230589818e32009d0c1c6eeddd1`, the GitHub Tests job passes all **583 tests**, including the reservoir-selection case. The combined follow-up still requires its own final-head CI. Two existing Omega scenario tests pass after repairing duplicated function declarations left by a historical merge. A repository-wide standalone TypeScript check still stops at its existing missing `hardhat` type-definition configuration; this is not reported as a passing global typecheck.\n\nThese results supersede the earlier gas and coverage failures below. They do not establish real provider integrations, paid settlement, independent validator operation, an authorized release signature, or a mainnet deployment.\n\nThe release inventory now includes all ten fixed implementations, and both explorer configurations verify them with their empty constructor arguments. Record their actual addresses under `implementations` (keyed by contract name) in `docs/deployment-addresses.json`. Manifest validation rejects omitted implementations and malformed addresses; explorer verification rejects empty, partial, duplicate, skipped, or cross-network inventories. Dry-run results are labeled `planned`, never `verified`. Six release-inventory regressions cover these gates. Existing example address books and controller constructor-argument files still require reviewed deployment evidence; the recorded constructor evidence still requires comparison with actual creation transactions on the intended network before commissioning.\n\n### Main-branch follow-up after PR #3876\n\nPR #3876 was merged at `f83334bdb636cbe77f17d5b510da198ccf8d061f`, whose tree exactly matches the reviewed `348a9235` candidate. No release or tag was created. Main-branch checks exposed two further CI-specific defects: the test launcher silently switched to a 50-run optimizer profile after the production build, and SLSA's default artifact filename inherited a forbidden colon from image tags. The follow-up makes the production profile the test default, keeps Node test suites in their dedicated CI runners, and supplies valid provenance filenames without changing the attested image subjects.\n\nThe CULTURE indexer now passes its existing coverage thresholds with **25 tests**, **93.40% lines/statements**, **91.76% branches**, and **95.94% functions**. Its production build and lint pass. Tests exercise the real Fastify/GraphQL API and SQLite migrations/data, pagination and lineage, ordered history replay and retries, checksums/timers, external-process failures, and weekly analytics. Startup and packaging entry scripts are still not exercised by this suite.\n\nThese tests accompany concrete corrections: the current nine-field `RoundFinalized` ABI replaces the stale five-field signature; failed backfills stop before later events and advance their cursor only after successful computation; rejected influence results are not persisted; cyclic lineage and malformed cursors fail explicitly; Python validation has time/output limits and rejects invalid scores; and influence inequality uses all metrics instead of only the displayed top ten.\n\nThe follow-up passes all root pretest checks and **582 Hardhat tests** with the production compiler profile, plus **42 standalone Node regressions**. The targeted bytecode/bundle compatibility checks also pass after a clean 267-source compile. Torch CI now runs on every main-branch push so the release gate can obtain evidence for the exact commit. Live event ordering and orphaned-event reconciliation still need commissioning; the historical replay tests do not establish reorganization safety.\n\nThe CULTURE Solidity contracts and tests are unchanged from the reviewed main baseline. Re-measurement confirms the existing lifecycle and misconduct costs (682,540 and 612,729 gas), and the committed snapshot references several tests no longer present in that baseline. Gas limits have not been raised to conceal these failures. The snapshot/budget review, contract coverage, real provider integrations, and Compose commissioning remain required, alongside authentic release signing and deployment configuration.\n\n1. **Review the modular deployment architecture.** The four oversized contracts are split and the size gate passes. Review the fixed delegation boundaries and staged deployment, and complete any migration and independent security review required for the intended network. The test evidence does not replace that review.\n2. **Configure authentic release trust.** Replace the example registry with authorized SSH public keys, verify fingerprints through the maintainer's process, and sign the reviewed tag. No signing identity has been invented or installed by this change.\n3. **Complete deployment configuration and planning.** `deployment-config/mainnet.json` still has a zero governance address. `release-mainnet.yml` references `scripts/v2/plan-deploy.ts`, which is absent from the reviewed baseline. Implement and review the intended deployment-plan generator before using that workflow; a configuration-update plan is not a substitute for a deployment plan.\n4. **Require current CI and security evidence.** Validate the PR's actual container builds, OS and application dependencies, browser suites, Foundry checks, branch rules, and release workflow. The baseline's August container run failed OS vulnerability scans; the October scheduled Torch run failed collection. Historical green badges are insufficient.\n5. **Commission the intended deployment.** Verify contract addresses, token units, identities, signer/validator independence, pause/recovery behavior, provider failures, monitoring, and paid end-to-end settlement on the intended network. Simulation totals and local tests do not establish live throughput, reliability, or economic returns.\n\n## Evidence and upstream references\n\n- [Baseline scheduled Torch failure](https://github.com/MontrealAI/AGIJobsv0/actions/runs/37092992665)\n- [Baseline container failure](https://github.com/MontrealAI/AGIJobsv0/actions/runs/33083499117)\n- [Node 22.23.3 release](https://nodejs.org/en/blog/release/v22.23.3)\n- [Node support schedule](https://github.com/nodejs/Release#release-schedule)\n- [Next.js September 2026 security release](https://nextjs.org/blog/september-2026-security-release)\n- [Passing primary-container CI at the earlier PR commit](https://github.com/MontrealAI/AGIJobsv0/actions/runs/37128420970)\n- [Application-image failure that prompted the follow-up](https://github.com/MontrealAI/AGIJobsv0/actions/runs/37128421393)\n- [CULTURE failure that prompted the follow-up](https://github.com/MontrealAI/AGIJobsv0/actions/runs/37128420924)\n- [EIP-170: contract code size limit](https://eips.ethereum.org/EIPS/eip-170)\n- [EIP-3860: initcode limit](https://eips.ethereum.org/EIPS/eip-3860)\n\nReturn to [Start here](../START_HERE.md).\n","format":"text","sha256":"757948592439a01370e052ae8c93bfc704141e4336a3425ad9d202a1fa23a76a","bytes":33837,"download":"/AGIJobsv0/examples/757948592439a013-readiness-2026-10-03.md","source":"https://github.com/MontrealAI/AGIJobsv0/blob/5b4cebb309a83a7a6749d8911d8bf96a1921e042/docs/production/readiness-2026-10-03.md"}]}
FROM READING TO A REPRODUCIBLE RUN
Continue to the implementation.
Architecture reading path
No standalone executable exists in this directory. Follow the related implementation below for an executable experience and its own prerequisites.
Open the related experience below for its guided inspection and run instructions. Reading this design does not execute or commission the proposed system.
The source inspector above reads bundled repository material. Local commands run separately on your computer. Recorded examples may contain historical timestamps, placeholders and simulated metrics.
MAKE IT YOUR OWN
One useful experiment.
Choose a component from the diagram and map it to code, a test and an output in the related demo. Record any component that still has only a design description.
THE SYSTEM, MADE VISIBLE
Architecture & relationships
Architecture diagram · source preserved belowView original Mermaid source
flowchart LR
Operators((Mission Owners)) --> demo_OMNI_CONCORD_ASCENSION_ATLAS[[Demo → Omni Concord Ascension Atlas]]
demo_OMNI_CONCORD_ASCENSION_ATLAS --> Core[[AGI Jobs v0 (v2) Core Intelligence]]
Core --> Observability[[Unified CI / CD & Observability]]
Core --> Governance[[Owner Control Plane]]
WHEN SOMETHING DOESN’T MATCH
Troubleshooting
A command or service fails
Start at the first error, confirm the working directory and pinned toolchain, then follow the linked component guide. Optional packages and provider services have separate prerequisites.
A report looks successful but lacks evidence
Check its source revision, configuration, timestamps and underlying events. Historical fixtures and generated plans do not prove a fresh execution.
TRACE THE CHECKS
Verification & next steps
This directory has no standalone test source files. Follow the shared implementation and its behavioral tests before making correctness claims.