Alpha Agent 1.38.0 — connected capability development
Local integration candidate; not published or operationally qualified.
Begin with the operator start guide and the Discovery Lab operating and reproduction guide. The proposed operator archive retains these guides at mapped paths, its exact self-contained capability page, original featured papers and the complete 41-source browser closure with original and packaged byte identities. Its adapted archive entry preserves the original inline programs, styles and CSP, retains the raw source page and all directly linked original papers, and identifies the other journeys that require the separate full site distribution.
This proposed additive minor version reconciles the paper/OUT-EXECUTE predecessor with the six-stage Discovery Lab continuation. It preserves both original Git histories through a normal merge and preserves every original manuscript and public PDF path. The source version is separate from deployed smart-contract source identities and the historical website/release pointers.
A single free browser workspace retains proposal development, Out-Evolve, OUT-EXECUTE, six-stage construction, frozen capabilities and subsequent tasks. The future protocol compares all committed tasks under seven treatment/control arms and retains failures, ties, cheaper competent alternatives, inconclusive budgets and interrupted reservations. It demonstrates bounded supplied synthetic semantics, not general autonomous capability or universal economic advantage.
The thirteen-section Evidence Docket binds the original mission history, artifacts, source identities, typed native requests/receipts and cost/lineage reconciliation. Imported evidence grants no execution, promotion, payment or settlement authority. USDC and AGIALPHA are alternative commission routes, with distinct denomination and identity requirements. Current installed cross-repository compatibility and independent organizational reproduction remain separate acceptance requirements.
The Fleet local-review return preserves the original typed work reference and raw native receipt in that same history. Its observations have a separate cost bucket; they do not create a commission or increase a currency balance. The actual public Fleet receiver and Alpha inspector pass the captured-source CLI checks on Node 22 and 24. This remains local finite review: hosted browser import/rejection/reload acceptance and released installed-runtime qualification are still pending.
The recorded 39-contract deployment inventory keeps historical instances and unknown ABI/helper/governance prerequisites explicit. The read-only inspector bounds and aborts cooperative transport work, charges terminal cleanup and retains partial observations. Current chain observation remains NOT_RUN. Unsigned operator proposals remain blocked; no signing, transaction, token approval, funding, minting, activation or unpausing is performed.
The public-software adapter binds a numerical-module proposal, captured artifact, later task bank and independently checked outputs to the same history. It does not execute imported source or claim a completed operational model/tool pilot.
Qualification still required
Both predecessor candidates require their current applicable checks and reviews. This integrated tree additionally requires independent conflict/source review, deterministic canonical/mirror/catalog/cache generation, all preserved Node, Python, browser, recovery, accessibility, security and release-policy gates, then exact-main and installed-package acceptance. Publishing requires authenticated release artifacts, downloaded-byte verification and actual public-site/legacy-link checks. Local preparation and predecessor success do not substitute for those gates.
The normal full software profile applies. Paper-only classification cannot qualify these runtime, workflow and version changes. Existing publication guards, permissions, acceptance dependencies, evidence and historical releases are preserved.