Skip to content

Project notice

1.37.0 — Bounded reusable capability construction

This source release prepares the additive capability workspace from PR #4844 and Out-Evolve constructor from PR #4845 for publication under a fresh version. The source baseline is d8857ba56420c6a34c29cc74831f274d6e767560. A prepared version is not a published release: the matching release manifest, successful exact-source acceptance run, uploaded checksums and public-site readback identify delivery. Existing release gates and publication permissions are unchanged.

Included mechanisms

  • An editable capability brief, frozen versions, exact synthetic construction and retained development/reuse evidence. Proposal-only records remain unevaluated. Unsupported broader proposals are not implemented by a synthetic pass.
  • A bounded Out-Evolve constructor searches installations and primitive compositions in a finite typed language. The generated program operates on declared synthetic apparatus models; it does not execute generated JavaScript. An independent implementation checks transitions, scope, model obligations and certificates.
  • Frozen executable packages support threshold screening, inverse design and constrained selection using prewritten downstream algorithms. Reuse does not invent those algorithms or establish protected external holdout custody.
  • Successors retain the old-plan diagnosis and qualify prior and added obligations. Unsupported parent operations remain structured incompatibilities; only scope-compatible installations with surviving dependencies are inherited. Skipped replay/measurement is explicitly not run, while frozen ancestor construction costs remain charged.
  • Pending searches, insufficient acceptance budgets, failed saves, divergent or older history imports and archived histories retain their evidence. Reuse and successor actions reserve bounded report capacity before evaluation. Compact replayable reports preserve task, exposure, obligation and cost evidence. An unexpected append failure retains the full unrecorded evaluation for session export rather than silently discarding it.
  • Source-bound generated pages, local storage recovery, keyboard/layout checks and scoped accessibility review remain available alongside the earlier flagship. The new capability workspace is English-only; existing bilingual pages and the original proposal/witness journey remain available.

The constructor is bounded by its program language, model support, state, memory, instruction, modeled-cost and wall-time limits. A budget exhaustion is not a proof of impossibility. Classical planning ties and sensing wins remain valid outcomes; incomplete optional comparisons are not successful baselines or evidence of savings. Costs are abstract model-work units, not measured currency, speedup, customer benefit or revenue.

Dependency correction

The operator, verified CPU demo and MuZero release locks use certifi==2026.10.19 with the official PyPI distribution hashes. This corrects GHSA-6q48-6c7w-9gw2 (PYSEC-2026-4320), which affects the previous 2026.7.22 pin's bundled certificate authorities. The correction does not suppress advisories or change release gates; a fresh exact-source dependency audit and the remaining acceptance checks must pass before publication.

Published v1.36.0 and earlier artifacts are unchanged and are not patched by this source update. Install the matching new lock with the new release, and rebuild any container images that vendor the affected certifi bundle. Preserved historical and development dependency environments are outside this three-lock correction.

Source evidence and remaining release gates

The final feature source 9302abb9e313e217c9a362b0e63ff12b6eb393cd passed all 18 reported source checks, including capability acceptance. On the merged baseline, capability acceptance, Smoke Test and Integration CI completed successfully. Those results retain their exact source and scope; they are not acceptance of this later version-preparation commit.

The baseline Agent release run stopped at the reused-version guard because v1.36.0 already identifies an earlier source. Version 1.37.0 follows the normal fresh-version path without moving an old tag, replacing assets or weakening that guard. Fresh configured CI, the separate capability-workspace checks, complete Agent release acceptance, package verification, public HTTPS readback and uploaded-byte verification remain necessary. Source merges alone do not establish live availability.

Published v1.36.0 identifies a6d20a93c7c5b7430bf42d2367701b350513e90d. Its matching artifacts and acceptance evidence retain their original validity and limitations. They do not include or qualify the later capability workspace and Out-Evolve additions. All historical release records and original papers, including Out-Strategise, remain unchanged.

Compatibility and operational boundaries

The current compatible Jobs/Fleet release set remains incomplete. This Alpha release does not repair the separate Jobs operator recovery blocker or establish passing Fleet Manager regression/functional review. Exact source, release, adapter and commissioning evidence for those projects must be checked separately before interoperating. Do not infer compatibility from a shared token, repository relationship or successful Alpha-only checks.

Manager USDC6 and Jobs AGIALPHA18 remain separate routes with their existing schemas, contracts and authorization requirements. No conversion, deployed contract, ENS binding, wallet authority, mainnet transaction, unpause, funding or spending is changed by this release. Native execution and paid or external actions still need their own supported adapter and explicit authorization. Local imports and successful synthetic checks grant none of that authority.

No physical deployment, unrestricted invention, general scientific or business qualification, novelty, superiority over competent classical planning, voluntary demand or realized revenue is established. Automated accessibility checks and scoped inspection are not full WCAG certification or human assistive-technology qualification.

Upgrade and recovery

Retain the previous runtime, matching release assets, complete private native backup and browser JSON exports. Keep identity material private; do not include it in public evidence. Test a new native installation with a separate home and never run two versions against one Journal. The capability histories use their own storage and do not rewrite existing native missions or confer authority on imported evidence.

Export full histories and any unrecorded evaluation before leaving the page or clearing storage. Browser storage is a local convenience, not a backup or trusted external journal. Oversized or conflicting histories fail closed; retain independent copies rather than deleting older evidence to force admission.

See the first-use guide, capability workspace guide, Out-Evolve source guide, Jobs/Fleet boundaries and release readiness.