Core developers
Linux isolation
On a qualified Linux x86-64 Host with KVM and the pinned release artifacts, Core can admit a reviewed offline workload inside a Firecracker microVM. The execution graph describes the boundaries measured for that run.
The thread belongs inside this boundary only while its run generation and guest identity match. No network traffic crosses the offline guest boundary.
Read the containment diagram
The cgroup accounts for the owned workload and exposes the measurements the kernel supplies. Namespaces isolate the reviewed host-side runtime. Firecracker provides the guest machine. To put a guest agent inside that graph, Core must bind the observed thread, VM and run generation.
Verified workload
An installed Core started pinned Codex in a guest with a read-only provider image, opened a temporary thread and recovered its original receipt. The verified bootstrap had no external network, shared host workspace, provider credentials or model inference. After the process exited and the run settled, Core retired its live graph.
Inspect the local boundary
cleetus-host inspect execution-graph
Use this on a Core with graph consent. Match the Host instance, run and expiry. The separate cleetus-host inspect isolation command runs a disposable Linux namespace fixture. That result applies only to the fixture. A required property that Core cannot establish denies admission. Execution observability · macOS isolation