Repository guide · 0 diagrams

View source on GitHub ↗
Original documentation, preserved from the repository. Historical projections and scenario ambitions are not evidence of live performance. See the current readiness record for deployment requirements.

Build your SUCCESSOR Ω with Alpha Agent + AGI Jobs

Open the bilingual workshop · Canonical source and complete guide

Name your Ω, compare four small programs on synthetic service records, compile 21 bounded job drafts, and save the working lab as one offline HTML file. English/French, larger text and keyboard controls are included. No account, installation, wallet or token payment is needed.

The example runs Alpha's existing fixed candidate engine and an unchanged pinned copy of this repository's SUCCESSOR compiler, templates, schema validation and integrity modules. The compiler's actual work orders include inputs, dependencies, limits, acceptance, expiry and rollback. All remain DRAFT with unsigned commitments. Public browser comparisons do not establish independent proof. Admission remains HOLD.

Check the exported package with this checkout

After downloading successor-build-pack.json, use the repository's supported Node.js version:

node scripts/pages/verify-successor-build.mjs /path/to/successor-build-pack.json

The verifier checks the package digest and canonical token, verifies every unsigned draft commitment, recompiles the complete job graph using this checkout's compiler, and requires equality with the exported compilation. It rejects altered terms, admitted jobs, forged authority and claimed settlement. It also rejects unknown evidence fields and checks Alpha's request, candidate and release commitments using an unchanged, source-pinned copy of the Apache-2.0 Alpha engine. It reruns the bounded synthetic discovery and evaluation to check deterministic correctness and row counts, and derives recorded totals and verdicts from the cases. New execution timings cannot authenticate the old reported timings. The consumer accepts this workshop's fixed local-only mission template. Only its name, whole-token planning allowance and creation/expiry timestamps vary. Recompiling broader permissions does not make them a valid workshop package; a different mission needs its own explicit schema and review. The complete plan is regenerated from the pinned Alpha workshop model. Its only adaptations are declared import paths to this checkout's Jobs compiler; tests reconstruct the original source and check its hash. Fixed evidence metadata is compared with replayed metadata, while historical timings remain unverified.

MATCH means historical consistency plus replay of this fixed synthetic workload. It does not authenticate a producer or their timings, prove correctness on a real-world mission, establish fresh rights or grant current authority. It never broadcasts transactions or changes job state.

Both deployed systems use the same token

$AGIALPHA · Ethereum mainnet · chain ID 1 · 18 decimals

0xA61a3B3a130a9c20768EEBF97E21515A6046a1fA

The workshop features all 5 Alpha Ascension and 24 Jobs instances with full addresses, roles, explorer links and pinned records. Inspect the complete directory. These are public records dated 11–12 October 2026, not a live readiness monitor.

Alpha MARK is fixed to its own market. Sharing AGIALPHA creates no automatic market bridge or permission. An operator must commission the chosen integration, identities, independent review, evidence and settlement. The recorded Alpha contracts precede later safeguards; the Jobs record does not open live intake. Read current readiness before considering live work.

Maintenance

website/successor-build/index.html is a byte-for-byte mirror of Alpha's generated workshop. Its provenance file identifies the canonical source path, engine identity, vendored Jobs revision and whole-page SHA-256. The site build publishes it at successor/build/ and includes that route in the site manifest/sitemap. The page is self-contained; no remote application code is fetched at runtime.

Update the canonical Alpha templates, regenerate and validate there, then update the HTML and provenance together. The site tests check the page digest, inline CSP hashes and agreement with the local deployment directory. The source guide maps the four supplied SUCCESSOR publications to the implementation and explains ownership, code licenses, full costs, independent evaluation, separate admission and renewal.

← Back to the collection