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.

Validation and qualification record · 2026-10-06

Scope

This revision completes the local Synthesis Foundry website, connects it to GitHub Pages, retains both original engines and their flowcharts, and adds an explicit admitted-worker path. It does not certify an unattended production fleet or report a live provider run, buyer acceptance or payment.

Correctness changes

Reproducible checks

Check Coverage
Python demo tests Existing functionality plus winner/telemetry identity, numeric/path rejection, CLI failure codes, stake/reward/vote and timelock regressions, HTML escaping
npm run demo:program-synthesis:test All three candidates and counterexamples, fixed task/source binding, exact accounting, reviewer and rights admission, receipt mutation, complete TypeScript dossier and manifest integrity
Existing TypeScript demo suites Original mission coverage, deterministic candidates, owner-command audit and report export
npm run demo:program-synthesis:qa Actual Chromium interactions and downloads, Python checks of downloaded files, wrong-candidate rejection, held plans, responsive layouts, WCAG A/AA checks, local assets and original diagrams
npm run site:build / site:test Integration into the complete observatory and catalog
PR workflows Authoritative remote build, test, lint, security and Pages checks; inspect the PR for the exact commit's results

Browser evidence is written under reports/pages/program-synthesis/ and uploaded by CI. Reproduction commands are in the README. Dynamic timestamps remain in original reports; seeded inputs and decision/score behavior are reproducible, not every report byte.

Remaining deployment work

Real-worker integration requires actual account/version/tool commissioning, an isolated host, independently enforced spend/action bounds, tested cancellation and reconciliation, separate reviewer/operator identities, actual buyer use and deployment-specific settlement authorization. The fixed synthetic acceptance suite is published and finite. It is neither a proof of universal correctness nor a substitute for independent evaluation of new work categories. Model/provider access was not required for this local qualification.

← Back to Program Synthesis