Project notice

1.27.0 — Your own SUCCESSOR Ω

Create your personal lab. Name it, choose a challenge, run an experiment and save the entire working experience as one HTML file. Reopen that file in a modern desktop browser, even offline. The bilingual guide explains how to keep it. For a separately installed agent, follow the operator start guide and backup, upgrade and recovery instructions.

What changes

• The welcoming homepage features SUCCESSOR Ω, a clear three-step introduction and a preview of what visitors can keep. The simple planner remains available, with its original review and export flow.
• The personal lab uses the existing bounded SUCCESSOR engine: four candidate configurations, exact correctness checks, six fresh workloads, comparator timings and complete evidence for the latest run.
• A portable copy includes the working engine, full Apache 2.0 license, reading preferences, personal name, last eight experiment summaries and latest evidence. It requires no server, API, model or account.
• English/French, larger text, keyboard focus, cancellation, readable failure messages and an unsaved-change prompt support a calmer first experience. No analytics or automatic browser storage is added.
• Saved observations are explicitly historical and unverified. New experiments compute fresh measurements; no saved state creates proof, permissions or autonomous authority.

Keeping your copy

Select Save my Ω, then open My-SUCCESSOR-Omega.html from Downloads in a desktop browser. Save again after changes; an open file cannot overwrite itself. Some mobile file viewers do not execute downloaded HTML, so use a desktop browser for the saved interactive edition. Files are not encrypted.

Users retain their personal files and software copy under Apache 2.0. This is not exclusive IP, a token, an NFT or company equity. The personal lab runs focused synthetic experiments; it is not a general AI assistant, a paid-work runtime or a demonstration of open-ended self-improvement.

Acceptance and scope

The release requires the existing complete acceptance workflow plus a real download → offline reopen → new experiment → second download round trip, exact output checks, hostile-name escaping, English/French, mobile and larger-text reflow, accessibility audits and no-network/no-storage checks. The same new journey must pass on the built gallery and the public site. The generated single-file application embeds the existing engine and uses exact script/style CSP hashes; it does not evaluate imported code.

These are acceptance requirements. The final release manifest and validation archive identify the exact tested commit and outcomes. Automated checks do not establish universal accessibility or billion-user capacity and do not replace usability studies with older and nontechnical participants.

All original workspaces, media, research and diagrams remain. This change performs no on-chain transaction and requires no native journal or contract migration. Independent qualification, production signing and commissioning remain subject to the existing release readiness requirements.