Skip to content

SUCCESSOR Ω implementation and preservation record

Baseline: Alpha b1be06f1e9d85a1517af46bb5757fb93003ef8cf, release 1.28.1. The attached 13 October mandate and the owner's additive/Computer Use requirements govern this work. This is a working gap register; an implementation path is not evidence of a passing release.

Requirement Baseline evidence Initial disposition
Existing missions, research, routes, flowcharts and deployed contracts scripts/check_successor_preservation.py, existing runtime/browser suites Preserve; regression checks required
Strict identities, commitments, independent proof and expiring authority core/runtime/successor/protocol.py, state.py, trust.py Already implemented; retain semantics
Durable reservations, revocation, recovery and portable knowledge Existing successor state, jobs and adversarial tests Already implemented; reuse
Five useful, distinct work families Metrics-only combined builder Needs extension with real processing and artifacts
Consequential customization and extension registry Closed aggregation grammar Needs versioned family manifests and input-bound execution
No-account local journey; save and restore Existing personal and combined labs Preserve; extend with work artifacts
AGI Jobs compilation and work acceptance Pinned compiler; Alpha job dispatcher and Ascension adapter Extend local work binding; deployed market commissioning remains external
Browser/desktop Computer Use No successor execution adapter Missing; add bounded provider/actuator interfaces and recovery
Real provider and operating-system qualification No account credential or Docker executable in this environment External evidence required; no host fallback
Evaluation, incumbent comparison and successor continuity Metrics mission plus independent-custody gates Extend per family; preserve negative outcomes
EN/FR accessibility and artifact ownership Existing browser controls and licenses Extend complete work journey
Installation, packaging, publication and provenance Existing agent release acceptance workflow Add new checks; retain every gate

Preservation rules

Add modules and routes. Existing files may change only to register commands, package their assets, link the new experience, generate caches, document its limits or run its acceptance checks. Record each such integration change in the final PR. No smart-contract, economic-rule, historical journal, legacy export, original demonstration or original diagram change is planned.

Evidence status

Implementation and validation are in progress. Live provider execution, macOS commissioning, independent evaluators, real-customer acceptance and mainnet authorization are separate gates. The $40 trillion/year screen-work opportunity is a founder estimate requiring a cited methodology before use as an independently established market statistic.

Implemented candidate, 13 October 2026

The initial gap register above is retained as history. The candidate now contains the shared five-family engine, portable EN/FR page, native journal/lifecycle binding, signed receipts, installed extension SDK, and optional bounded Computer Use browser. The latest addition has no host desktop, account-login or live-market authority. Review the explicit domain boundaries in SUCCESSOR_WORK.md.

Local qualification used Linux, Python 3.12.14, Node 22.17.1 (final domain/conformance runs) and Node 24.19.0 (initial complete native suite). Browser QA used Chromium through the repository's Playwright 1.54.0. The optional container declares its own locked Playwright 1.63.0 environment; this is a separate gate.

ID Status at stated scope Evidence and remaining boundary
Ω01 PASS Real browser create/run/save/reopen, no credentials or storage
Ω02 PASS Five different adapters; actual Node repair checks, timings, docs execution, CSV and exact rational work
Ω03 PASS Semantic/cosmetic binding tests; live input invalidation in browser
Ω04 PASS for draft handoff Pinned Jobs compiler, exact task-bound seven-package graph; live dispatch/settlement uncommissioned
Ω05 PASS for local scopes Schema, rights, resource and unsupported-code refusals; live reviewers remain an external gate
Ω06 PASS Correct incumbent retained, negative numerical result retained; existing comparator adversarial suite
Ω07 PASS in initial candidate CI The browser-contracts job in run 38416321126 exercised the real local EVM; the final head must pass again
Ω08 PASS for local protocol Existing forgery/replay/signature suite plus hostile artifact and supplier-substitution checks
Ω09 PASS for bounded local protocol Existing atomic ledger tests, work revision/lease bounds, computer task reservation and replay guard
Ω10 PASS for controlled faults Native pause/recovery and uncertain computer-effect receipts; normal real-container typing and screenshots also passed CI
Ω11 PASS for controlled faults Failed cleanup quarantines; missing Docker has no host fallback; normal real-container cleanup passed CI
Ω12 PASS for existing bounded lifecycle Existing specialist/delegation suite preserved; extension SDK adds installed adapters, not arbitrary self-provisioning
Ω13 PASS for local export/rebuild Offline reopen, native reinstall, signed attribution, inert restore with empty authority
Ω14 PASS for substitution binding Provider identity changes require a different permission commitment; no live supplier equivalence claim
Ω15 PASS for existing metrics study Existing matched memory/control study preserved; new families make no unmeasured compounding claim
Ω16 PASS for controlled adversarial scope Unknown tools, host keys, private DNS, unlisted queries, poisoned source and artifact paths rejected
Ω17 PASS for browser scope EN/FR, keyboard, 1440/390/320 widths, larger text, axe WCAG tags and offline reopen; manual screen-reader/native OS qualification NOT RUN
Ω18 PASS for source preservation 2,895 starting files, 167 media files and 95 Mermaid blocks retained from the exact starting SHA
Ω19 PASS for Linux installed wheel Five families and receipt verification run outside checkout from the 1.29.0 wheel; other native OS qualification NOT RUN
Ω20 NOT RUN No release tag or Pages publication yet; exact-head CI and independent review required

Reproducible commands are in the user and Computer Use guides. The initial native suite reported 499 passed and one Docker-dependent skip. Focused follow-ups cover the later reconciliation/cleanup hardening. Nine Node conformance cases pass. These are overlapping scopes, not additive proof counts. The browser report records all five families, EN/FR, three viewports, offline reopening and zero axe violations. The 1.29.0 wheel is approximately 5.1 MB; the standalone page is under 150 KB.

The full local legacy pytest run recorded 2,297 passed, 32 failed, 75 skipped and 4 expected failures. Failures included four candidate release-metadata checks, inherited SOCKS-proxy dependency/HTTP subprocess problems, missing local tools and notebook-kernel startup failures. The four publication checks were corrected; the subsequent focused publication/workbench/computer run passed 141 tests with one Docker-dependent skip. This does not turn the earlier full run green. The broad type scope reported 205 errors across 50 files, including optional-import typing problems; the dedicated strict runtime scope passes. Exact final CI must decide the release gate; retain failed and skipped results.

The initial candidate CI run 38416321126 passed the existing browser/contract, real-model, dependency, native demo and distribution jobs. It caught stale release metadata, a gallery navigation insertion that altered the workbench inline script, and formatter/workflow lint issues. Those failures prompted explicit fixes rather than disabled gates. The corrected local browser acceptance reports all five families, offline reopening and zero axe violations; the full pre-commit report passes.

Required integration changes include release version/cache references in current workspaces and marked demo launch headings. These are generated by the existing gallery, mirror and catalog tools; historical release notes, original diagrams, contract interfaces and economic rules are retained.

External and publication gates

  • Maintainer: independent engineering review and the normal merge decision. No self-approval is claimed.
  • Repository administrator: effective main protection was absent in the inspected branch/rules responses; source workflow files alone do not establish enforced review/check requirements. No protection was weakened.
  • CI operator: qualify the exact final head and merge state, actual Docker/Chromium behavior, EVM and final downloaded distributions using all existing gates plus the new workbench job.
  • Provider operator: supply authorized account access and spending controls, then record real model usage, screenshots, costs and task review. No provider credential or paid model call was used here.
  • Independent evaluator/customer: qualify claims and accept real commissioned work under actual custody.
  • Chain authority: separately commission live operations. This task authorizes no transfer, approval, unpause, ownership change or mainnet deployment. Existing 29-address historical records are preserved.

This is a software candidate awaiting those gates, not a claim of complete production commissioning.

Container and final-distribution follow-up

At candidate 8465b57338b2fe8119be4b0e94f5fe69e25b7dd7, CI run 38418835189 passed the new workbench job: 26 native tests with no skip, including actual disposable Docker/Chromium typing, screenshots and verified cleanup. The scripted advisor in that test is explicitly not a live model. The complete local native suite passed 501 tests with one local Docker skip. The same candidate wheel ran all five families outside the checkout and verified their signed receipts. Final-head CI remains required after changes, including this post-publication workbench gate.

A future 1.29.0 publication now requires the deployed workbench to match the checked-out HTML and domain-source hashes, execute all five families, reopen saved artifacts offline and pass EN/FR, keyboard and accessibility checks. Release finalization rejects stale, incomplete or local-only reports. This adds a publication requirement; no release or site has been published here.

Pre-merge lifecycle review

On 13 October the owner explicitly requested merging PR #4777 and publishing the next release. Review of head 96f9254ea5a135c166226629c1c50df6eebaa866 checked the execution, import/export, Computer Use and publication boundaries and identified a stopped-run recovery defect: the control command could change a stopped run back to paused, allowing an explicit resume. The correction refuses that transition, preserves the original stopped record and still permits retirement. The regression is test_stopped_work_cannot_resume_through_pause in tests/runtime/test_successor_workbench.py.

This is an internal source review, not an independent mission proof or a GitHub approval from another maintainer. The observed main branch remains unprotected, repository rulesets are empty, and the integration cannot read the administrative branch-protection endpoint (HTTP 403). No rule is changed or bypassed. The owner's merge instruction permits the normal PR merge after final-head checks; the existing main-branch workflow must qualify the integrated source before Pages/release publication. Final run links, merge SHA and publication evidence belong in the PR and generated release manifest, so these historical candidate observations must not be interpreted as final publication results.