Cleetus Core developers

Core developers

macOS isolation

On Apple silicon, the reviewed offline workload path uses Virtualization.framework to create one Linux VM per operation. Core owns admission and the operation receipt. The native helper owns that VM's lifecycle.

The Apple silicon execution boundary
Selected CoreChecks current scope and capacity
Signed native helperVerifies and starts the approved VM
Virtualization.framework VMOne CPU · 512 MiB · no network interface
Linux guestUnprivileged process · read-only input
Reviewed workload

The guest returns a bounded result on a dedicated port. The supervisor also needs confirmed VM stop to settle the workload.

Read the containment diagram

The reviewed image binds the helper, Linux kernel, guest init, workload and optional immutable input. The VM receives one CPU, 512 MiB of memory and no network interface or shared host directory. The guest runs the selected executable unprivileged. Its optional read-only workspace snapshot is bounded to 8 MiB.

Verified workload

Apple silicon hardware tests exercised the actual guest workload, immutable input and stop of a VM containing a descendant. A workload exit code requires both the guest's result and observed VM stop. If the helper disappears before stop confirmation, settlement stays unknown and Core keeps the capacity hold.

Inspect the release and the run

cleetus-host verify apple-vm
cleetus-host inspect execution-graph

The first command verifies the installed, pinned Apple VM bundle. A live graph observation requires its own graph grant and a matching active run. Current proof covers the reviewed offline Linux workload. Provider login and authenticated guest development require additional implementation and acceptance. Linux isolation · Execution observability