Connected Discovery Lab — source candidate

This additive candidate extends the existing capability workspace with one finite synthetic materials-testing mission. Visitors can change measurement accuracy, intended uses, observations, operations, memory, worker placement, fault hypotheses, checkpoints and resource budgets. Those constraints drive construction and independent checking across all six stages. Failed and incomplete attempts remain in the same portable history as accepted predecessors. Visitors can select an earlier accepted campaign and export its still-qualified review draft after a later failure, without spending another construction attempt.

The generated platform is frozen before threshold screening, inverse design and constrained selection. A four-control successor preserves the predecessor's original obligations and undergoes fresh finite qualification. Complete same-primitive reference planning, tied and cheaper alternatives, ablations, invalid evidence and exhausted budgets are retained in the reproducible case bank.

Try the candidate

Use the reproduction commands, paper-to-code map and public integration checklist. The generated entry is successor/capabilities/index.html#discovery-lab in a qualified site package. Its presence in source is not a claim that the public website has been updated.

Manager #1613, Jobs #4010 and Fleet #64 add explicit local semantic receiver admission. Their evidence identifies the exact Alpha source and native runtime inspected. One frozen logical commission can select separate USDC6 and AGIALPHA18 branches; both remain zero-cap DRAFT_NOT_SUBMITTED records. A local inspection does not submit, execute remotely or settle a job. Unprovisioned external execution remains explicit.

Existing work and recovery

Original capability workspace v1 histories remain readable. The v2 extension adds reserved campaign starts, completions and interruptions to the existing store and hash chain. Storage is reserved before construction; failed persistence retains recovery exports. Imports restore historical evidence and charge their actual checking work without granting current authority. Keep a downloaded history and account receipt before clearing browser storage or upgrading.

Existing demos, papers, URLs, releases and supported workflows retain their own evidence and meaning. This candidate follows the separate PDF repair and pending OUT-EXECUTE/research integration. It does not replace those owners' work or waive current-main, security, package, publication or public-byte gates.

Qualification scope

The model has three or four binary controls and bounded, supplied construction grammars. Acquisitions, logical operations, encoded bytes, virtual workers and observed local elapsed time are separate units. The report distinguishes constructor work, independent checking, recurring uses, successors and the whole retained history. Public seeds are reproducible regression cases, not protected holdouts.

Exact-source tests, configured public review and CI, reconciled baselines, native source/runtime qualification, release packaging and actual public acceptance must all identify the delivered version. Until those gates pass, this remains a source candidate. No physical material result, general invention, industrial deployment, revenue, token value, external execution or spending is established.