Skip to content

Project notice

1.24.0 — SUCCESSOR Ω mission institutions

Release retries bind the historical-CI report to the successful job's unique artifact name and digest. Packaging rejects stale or unsuccessful reports, and the wait budget accommodates the historical test jobs' full time limit. See retry recovery.

Publication requires the exact-commit acceptance workflow. The published release manifest records the accepted revision, workflow and evidence; this guide describes the version's behavior and requirements. This feature extends the maintained runtime with persistent mission institutions, separately versioned candidate/proof/authority records, bounded aggregation search and explicit succession. It is an additive progression from Ascension. A software release, a local comparative result, external qualification and production authority remain distinct statuses.

Start with the SUCCESSOR guide, the beginner entry point, architecture and release packs.

What changes

  • Strict versioned protocol objects and domain-separated canonical commitments bind missions, exact releases, comparators, examination conditions, work terms and accountable decisions.
  • The offline public technical mission measures streaming metrics aggregation with constructed bounded challengers, a competent incumbent, alternatives, WORLD predictions and explicit correctness gates. Negative results, retaining a better alternative and missing external evidence remain useful outcomes.
  • The native lifecycle adds durable institution state, atomic shared resource reservations, attributable decisions, scoped action-time grants, revocation, impairment, permitted memory and successors whose proof and authority begin empty. The existing native signed journal format is preserved.
  • The Ascension adapter distinguishes indexed plan leaves from the market's zero-index Spec hash and binds richer sealed terms to the observed assignment. Useful negative evaluation can be accepted and settled without admitting its candidate. Existing $AGIALPHA economics and Solidity meanings remain.
  • The English/French browser rehearsal uses fixed bounded engines and carries a validated request to the installed CLI. Returned evidence is bound to the original request and separately retained trusted key.
  • Imported Ed25519 evidence rejects weak and noncanonical keys or signature components before library verification. Historical signed bytes and the documented wheel-signature format remain unchanged.
  • Distribution uses a small native core and bounded browser/site packs. Every published file is checked against the 450,000,000-byte limit, with original content retained and safely reconstructed.
  • Installation, offline restoration and the source setup wizard provide command examples, actionable failures and interruption recovery. The operator guides cover wheel-only examples, Windows execution, checkpoint-aware upgrades and separate private recovery versus portable institution transfer.
  • The Hardhat deployment guide adds a read-only plan and a verified disposable local deployment with compiler/source identities, complete mined receipts and contract bindings. The unavailable legacy Truffle deployment now stops before loading credentials or submitting transactions. External-chain migration remains unsupported.

Compatibility and preceding repair work

This version includes PR #4758 at d1fb99e629ec1627e7d3876a330797bde79d5ee6, based on main aab4995ee87f7fb575180931c79b8bf86e26d50d, merged with SUCCESSOR in PR #4759. That work retains repair-path safety and rollback, public-tag identity checks, Insight dependency/layout corrections and MuZero controls. Its formerly stale generated Insight documentation assets are rebuilt from the locked toolchain. Repair copies and comparisons also exclude CI's generated .tmp browser caches, while continuing to reject links and special files in project inputs. Excluded caches cannot become proposed deletions.

The preserved web client updates Vue and source-map-js for their production advisories. Insight's locked build dependencies use patched sharp 0.35.5 and compression 1.8.2. Its ONNX installer uses global-agent 4.1.3 to remove the unpatched sprintf-js dependency chain while retaining the existing Transformer browser runtime. The existing dependency-audit thresholds remain required.

The five maintained native mission kinds, CLI entry points, Ascension contracts, original demos, research, media, diagrams and historical URLs remain available. The complete pre-SUCCESSOR inventory covers 2,731 paths, including 167 exact media assets and 94 Mermaid blocks, in addition to earlier README/manuscript/factory checks. No historical signature bytes or plugin wheel-signature conventions are redefined. The new institution protocol does not convert old approvals into new proof or grants.

Installation, upgrade and rollback

Use the matching release wheel, requirements-agent.lock, SHA256SUMS and install_agent.py to create a new environment. The guide's first offline rehearsal requires no wallet, account, API key or model weights. Arbitrary generated-code execution retains explicit Docker opt-in and has no host fallback. For browser/site packages follow the pack restoration instructions.

Pause the old agent, verify and privately back up its state, and retain its independent checkpoint. Keep the old environment and state directory. Run the new version with a new home and restore only through the documented explicit workflow. Portable institutional knowledge exports exclude operational grants and private signing credentials; they are different from private disaster-recovery backups. Do not run two serving versions against one home. To roll back, stop the new process and restore a verified backup into a separate home using the retained previous environment only if the backup satisfies the latest independently retained checkpoint. Do not erase later revocations or work by choosing an older checkpoint. If current history cannot be restored compatibly, keep the operator stopped. Follow the private recovery procedure before reassessing permission.

Validation and limits

The release workflow retains existing Python 3.11/3.12/3.13, regression/coverage, types, hooks, browser, Solidity/local-EVM, real Docker, model, advisory-audit, installed-wheel, site and publication gates. It adds the SUCCESSOR lifecycle, adversarial protocol/authority/lineage tests, browser/native handoff, cache upgrade, exact baseline preservation and bounded distribution round trips. Public acceptance must identify the exact same commit and version as the packaged bytes before publication.

Read the final validation evidence and requirement matrix for actual passes, failures and untested platforms. Gate definitions do not mean a run passed. A deterministic supplier adapter verifies its local interface and recovery behavior; it does not establish actual neural execution or frontier supplier replacement. Distinct local roles/keys are local provenance, not external verifier independence. Missing external frontier/customer evidence remains explicit, and no mainnet spending, token migration, ENS mutation, production grant, independent Alpha or Specialist ASI designation is asserted here.