Keep the catalog mission through native work
The flagship's Continue with native work step keeps the exact catalog project and its latest completed
cycle. It prepares an executable mission through the maintained
createWorkbench extension API and compiles its seven
work packages through the existing AGI Jobs compiler. This is useful local work with inspectable outputs.
It remains an unfunded draft, with independent qualification and admission unresolved.
What is connected
| Artifact | Actual native format or API | Meaning |
|---|---|---|
| Handoff | successor-alpha-native-handoff/v1 |
Exact project, cycle and catalog mission |
| Input | successor-workbench/v1, catalog-reconciliation adapter |
Exact rows, duplicates and conflicts |
| Jobs draft | Existing compileJobs, via native plan |
Seven DRAFT packages, zero AGIALPHA funds |
| Return | successor-alpha-native-return/v1, native run / inspectPack |
Five catalog files and four methods |
| Continuity | successor-alpha-native-continuity/v1 |
Exact original snapshots, handoffs and returns |
| Manager / Fleet | Catalog executor not installed | Existing integer-total adapter does not join catalogs |
A catalog is never converted into group,amount totals to make an unsupported receiver accept it. That
would change the mission. The downloaded catalog handoff is not an agi-fleet/project-request/v1 or a
Fleet controller receipt. The existing guided integer-total journey remains available separately.
The native compiler uses AGIALPHA planning units. The separate USDC brief is still an unfunded planning brief for Manager; it does not acquire this native adapter through a currency switch. No job is posted, funded or settled, and the five supplied Ascension contract references do not change that boundary.
Run and inspect the same task
In the flagship, complete a catalog reconciliation and explicitly declare the permitted input rights. Prepare and download the native handoff. Local SDK run exercises the native workbench API in a cancelable browser worker; it is browser execution and does not establish a host or Fleet round trip.
For actual host execution, keep the exact handoff and run this command with Node 22.17.1 or later from this repository checkout. The output filename must be new:
node examples/successor-alpha/native-cli.mjs successor-alpha-native-handoff.json NEW-successor-alpha-native-return.json
The host runner opens only a bounded regular UTF-8 input, independently computes the installed source identity, executes the maintained adapter and independently validates its returned catalog output. It publishes the complete return exclusively after validation, refuses existing outputs and requires no account, provider credential, wallet or network access. FIFOs and devices are rejected without waiting for their contents. A changed source commitment refuses execution and creates no return.
Import that return into the unchanged flagship project and keep the resulting continuity file. The return uses the same checked format as a browser SDK run; its checksum alone does not authenticate an external host or establish runtime isolation. The separate automated acceptance test actually launches the Node process with OS files, then imports and verifies its result against the retained catalog project.
The handoff is bound to the exact current project revision; edits or a fresh cycle require a fresh handoff.
Source identity covers the maintained generator's entire reviewed static JavaScript module closure for
the flagship engines and native SDK/compiler. UTF-8 line endings normalize to LF, matching that generator.
computeInstalledSourceHash() in native-cli.mjs exposes this check for local tooling. The hash establishes
consistency with installed code, not publisher authenticity. No source code from a handoff executes.
For programmatic use, nativeCatalog.validate accepts the downloaded native spec and
nativeCatalog.plan(spec, compiledAt) reproduces its compiler draft. runNativeHandoff returns checked
native evidence, and importNativeReturn retains that evidence separately from the strict flagship project.
The planning compilation and the actual local execution compilation retain their respective timestamps. Neither is a funded or accepted contract. The native runtime always compiles its own plan before work; import checks that exact plan using its recorded creation time and the current installed native compiler.
Returned evidence and retained learning
Imports verify the handoff checksum, original project and cycle, exact native spec, native compilation, source commitment, artifact digests and native pack binding. They then independently recompute all catalog pairs, unmatched rows, conflicting shared fields and deterministic operation counts. Rehashing an invented result or changing its summary cannot make it pass. CSV exports remain formula-safe; exact JSON retains the original strings and duplicate multiplicity.
Only an exact matching current project can append its return. A later cycle can append another return to the same continuity record when all earlier project cycles and opportunity notes remain unchanged. Earlier snapshot and return bytes stay intact. Different projects, stale cycles, duplicate returns, rewritten history, changed routes and authority or qualification claims are rejected.
The separate continuity record avoids changing the strict flagship project format or presenting this local result as a native institutional credential. Imports restore historical observations, empty active proof, no current acceptance review and no operational authority. Timings remain recorded observations; they are not independently reproduced timings. A local exact-output check does not certify an external controller, independent reviewer, protected evaluation, production isolation or economic advantage.
The transport is bounded to 2 MB, eight returns and eight project snapshots. Native artifact policy also limits each file to 200,000 characters. A catalog allowed by the browser may exceed these stricter native transport limits. Capacity errors retain the original project and earlier continuity; nothing is truncated or deleted. Keep the original useful catalog outputs and explicitly select a smaller task if needed.
node --test examples/successor-alpha/continuity.test.mjs examples/successor-alpha/native-cli.test.mjs
These checks exercise real SDK execution, an actual Node host subprocess, compiler validation, duplicate joins, conflicts, exact artifacts, source substitution, cancellation, rehashed forged evidence, stale imports, FIFO/oversize refusal, output preservation and append-only continuity. An eligible independent reviewer and an explicitly commissioned catalog executor remain separate work.