WEBVTT

00:00.502 --> 00:12.214
Now a configured worker will stop across a real virtual machine power cut. The debugger runs independently of the managed renderer,
so it remains available to explain the stalled job.

00:15.198 --> 00:28.169
I disable the installed worker, then cut power and boot its original volume. Disable is durable configuration. The new kernel boot
has a different incarnation, and the worker process does not start.

00:36.255 --> 00:50.442
A new job remains pending. The coordinator can prove its local pending state and enrollment. The worker reports disabled. That is a
plausible bottleneck, not proof that a packet was lost or work never executed.

00:51.417 --> 01:05.668
Configuration observations connect across boots through matching content and the disable request. Dashed grey correspondence is
context, not a newly invented causal edge. The receipt IDs keep the two boots distinct.

01:06.087 --> 01:19.079
I power off the worker again and query the job. Its cached records are still inspectable, but the source is now historical. The
debugger stops presenting the old disabled report as live service state.

01:19.485 --> 01:32.093
Next I power cut and reboot the coordinator on its original volume while the worker remains offline. The persisted remote cache
survives. Missing live evidence remains visibly missing after reboot.

01:35.722 --> 01:47.520
I boot and enable the worker. Real work resumes, and the completed pixels match the independent reference. The earlier completed job
also retains its exact accepted bytes.

01:57.970 --> 02:12.861
Both machines here are native x86 sixty-four QEMU guests. This demonstration does not claim physical hardware support, authenticated
HTTP peers, deterministic replay, or exactly once execution.