1.12.0 — Alpha-Factory operating guide and native Ascension handoff

The package landing page lagged behind the maintained runtime and executable Ascension protocol. It contained broken launch paths, proposed commands presented as installed APIs and unsupported maturity labels. This release provides a current factory guide while retaining every original package path, flowchart and media asset.

Native work connects to committed jobs

examples ships all five editable missions with source and wheel installations.
ascension-compile and ascension-check use exact Ethereum Keccak/ABI/Merkle rules and integer token units.
ascension-deliver binds an explicitly reviewed native result to its exact plan and matching goal.
ascension-verify-delivery requires an independently trusted key and plan root, verifies exact signed bytes and rechecks native arithmetic. Code replay requires explicit permission and Docker.

The handoff does not submit transactions, impersonate ENS ownership or cast validator votes. Validators still assess the success metric and intended chain/job independently. The same plan root may occur in several seeds; chain binding must be observed separately. See the Ascension guide.

Reliable setup and documentation

Bash and Python source launchers share one implementation. Source paths resolve correctly, Python 3.11–3.13 is supported consistently, and the maintained agent has a preflight that needs no Node or Docker for non-code work. Check-only mode never installs. New environments install hashed dependencies; partial installations, changed lock digests and failed preflight checks stop visibly. Existing user state is never replaced.

The full research architecture, industry-agent suite, 26-entry catalog, manuscript and original flowcharts remain. Current execution modes and links distinguish tested runtime behavior from optional integrations and research targets. This is a maintained private-operator release, not a claim that all historical research modules are commissioned production services.

Acceptance and upgrade

Release gates exercise native missions, adversarial handoff checks, Python/JavaScript/Solidity interoperability, source launchers, the wheel outside its checkout, all historical regression tests, browser flows, strict types and documentation. Preservation checks compare the package paths, Mermaid blocks and media against the pre-update commit. The release validation archive contains exact results.

No journal schema or contract changes are introduced. Pause and back up the old agent, install in a new environment, restore into a new home, verify the identity/head, and resume after inspection. The operator guide includes rollback and offline installation commands.