CUBESANDBOX v0.7.3 · SDK 0.7.3 · 2026-10-18

A killed process returns with its memory

Two Kubernetes environments · Three rounds each · CPU Python worker

6 / 6 PASS

Environment / round	Snapshot	Before kill	Rollback	New VM	Continue
Lab / 1	17	32	17	17	27
Lab / 2	17	32	17	17	28
Lab / 3	17	32	17	17	28
Production / 1	12	27	12	12	19
Production / 2	11	25	11	11	17
Production / 3	14	27	14	14	22

Each round: capture → kill guest process → rollback → delete source VM → restore.
All restored identities, PIDs and full state digests match. New resources remaining: 0.

Acceptance report rendered from lab-results.json and production-results.json. Not a product UI.

PRODUCTION / ROUND 1 · ACTUAL STATE COMPARISON

Same memory, even after deleting the source VM

Progress and random identity exist only in RAM; no application checkpoint is loaded.

Snapshot 12 → advance 27 → SIGKILL → rollback 12 → continue 20

Captured in the source VM

counter      12
PID          33
identity     7ba5957579f0
digest       5d543454fafb…
hold         true

Restored in a new VM ✓

counter      12
PID          33
identity     7ba5957579f0
digest       5d543454fafb…
hold         true

Source VM deleted before new VM creation. Releasing the hold advances the new VM to 19.
Fresh loopback connections verify the restored process; no old TCP connection is reused.

Light acceptance report · Full SHA256 digests retained in production-results.json.