1.34.0 — Useful Alpha and current deployment evidence
Version 1.34.0 combines a useful SUCCESSOR Ω flagship with the current Mainnet deployment record. Start with a working catalog reconciliation, inspect its evidence and retain the tool and project history. The deployment directory separately records five fresh contracts and their finalized one-time bindings. Source preparation alone is not publication: the matching release manifest, exact-commit acceptance and verified public site identify the delivered version.
Included
- English/French catalog reconciliation with exact matching, duplicate preservation, joined output, unmatched rows and discrepancies. Keep CSV/JSON artifacts, a readable report, a standalone Node tool and the complete working browser workspace offline.
- Four maintained join strategies with correctness checks, operation counts and observed local timings. Optional strategy development constructs bounded composite plans against seven declared textbook baselines under an explicit resource objective, freezes a plan, and checks it on a new public synthetic case. A loss remains HOLD and retains the incumbent.
- Executable per-key discrepancy-action plans retain every source occurrence for review. This changes the review contract; fewer action items do not establish automatic correction or measured time savings.
- Project history and a checked learning archive retain inputs, methods, local observations and reusable tools. Exact catalog handoffs use the existing native workbench and Jobs compiler. The browser SDK rehearsal and installed Node runner are distinct paths; checked returns grant no execution authority and the compiled AGIALPHA route stays unfunded.
- Complete imported resource limits, bounded standalone file reads through short reads, nonregular-file rejection and guarded restoration preserve the local input/export boundaries.
- Contain decorative hero artwork and require overflow-free English/French first use at nine viewport widths from 320 to 1440 pixels, including intermediate desktop and tablet layouts.
- Read-only public contract directory, explorer links, machine-readable deployment record and source/report provenance. Historical October 11 evidence remains unchanged.
- Exact deployed source compiler profile and creator/authority tooling from
c0fc5217e364a39a4cd123d17a8317c06b80f820, including the narrow SOL-2026-7 workaround, strict profile admission and regression controls. - Early publication preflight catches a version already tagged to another commit before expensive acceptance jobs. Immutable tags, exact-current-main, full acceptance, uploaded byte verification and served Pages checks remain required.
- Keep the original local validation archive unchanged and retain public acceptance in separate hash-verified public-validation packs. All evidence remains available within the unchanged 450 MB per-asset limit, with both captures listed in the release manifest and checksums.
Scope and limits
The Gym develops capabilities; it does not certify Specialist ASI. A frozen candidate must separately beat Current and the best credible alternative on agreed protected work and constraints. Accountable authorization remains required for succession or operational authority. The local public synthetic checks establish neither independent evaluation nor a novel algorithm, model improvement, general intelligence or realized economic advantage. Optional value estimates use the user's supplied assumptions and do not establish full costs or actual savings.
The deployment and scoped graph verification are recorded separately from activation, external dependency qualification, security assurance and off-chain commissioning. No public funding or activation is approved by this release. There is no global pause. Existing wallet profiles and historical contract addresses are not automatically migrated. The five October 18 records are separate from the older 29-address ecosystem snapshots; historical archives and pinned wallet profiles retain their original identities. External authority closeout completed at 2026-10-18 15:24:15.848 UTC, releasing both original actor leases without signing or broadcasting transactions. The original deployment session remains historically incomplete at sequence 20 with its journal unchanged. Actual manual binding calls were verified post hoc; that evidence does not recreate missing pre-sign intent. See the record for deviations.
The release source includes publication changes and therefore has a different commit from the immutable deployed source. Use the deployment record's exact commit/tree when reproducing deployed contracts. The compiler workaround is narrow, not a guarantee against every compiler defect or a claim of production readiness.
Continue from 1.33.0
Existing routes, laboratories, compiler/admission gates, research and diagrams remain available. Obtain matching published assets in a new destination and retain earlier project exports and checkpoints. Imports are checked local history, not active proof, permissions or publisher identity. Recompute observations for new inputs and review source changes before reusing retained tools. Do not alter an existing wallet profile to adopt the new deployment without a separate reviewed configuration and authorization decision.