Prepare-first and “no target install” acceptance contract
A strict claim needs a reproducible experiment, not an animation or a provider logo.
Guarantee scope
For declared, completely prepared and compatible environment resources, the accepted task should not require dependency-registry access or reinstall runtimes, dependencies or tools inside the target. Record versions, native inputs and locks, target OS/architecture/ABI, preparation tooling and host prerequisites.
What the claim does not mean
It does not mean the business application never uses the network. It does not mean handoff performs zero transfer or extraction. Reading prepared image layers, importing a fully materialized package or mounting existing prepared storage are delivery operations. Resolving or compiling missing environment pieces through a package manager inside the target is target-side preparation.
Minimum experiment
Record a clean target baseline. Run sync in an isolated preparation location with fixed native locks. Deliver source and environment without inheriting undeclared preparation directories or proxies. Deny access to declared dependency/runtime/tool sources in the target. Activate with the real UID, cwd and process, then run environment probes and the native task. Preserve exit status, logs, network observations and instance configuration before teardown.
Required negative cases
Delete a required browser binary: fail with missing resources rather than invoking an installer. Supply only a source distribution or installer archive: fail as not materialized. Change CPU architecture: reject the old materialization. Corrupt a resource: reject failed verification. Put package installation in the startup script: strict mode fails even if automatic installation succeeds. Remove activation metadata: report activation required, not ready.
Ready-for-task criteria
Target installation must be false, dependency-registry access must be false, and compatibility, completeness, verification, source delivery and activation must all be satisfied. Task success is a separate outcome.