Concepts · 4 of 4

Specific guarantees, not a magic sandbox.

Celln makes different promises for declared tools and agent-authored code. It refuses to claim a hardware property on a host that cannot provide it.

What is enforced in a KVM cell

Agent-authored code

celln agent creates a real sealed KVM cell. The generated program is always author=agent and runs in the agent lane: only its executable and writable workspace are loaned. Landlock rejects other filesystem access; seccomp rejects network and privileged syscalls. Compiling model-written source does not promote it to tool-lane authority.

Network is brokered

A cell has no in-kernel network stack. For a named HTTPS destination, use --allow-host example.com, or in a spec [cell] allow_hosts with a tool declaring builtin = "fetch". Pilot passes the request over vsock and the host performs the fetch; private addresses and redirects that leave the declared authority are refused.

What Celln does not claim

Verify on your own host

celln doctor
celln verify
make acceptance-kvm
make bench-kvm

The acceptance check drives setup, generated code, its in-cell boundary, and celln ps -a using a deterministic local model stub. On a suitable host, the hardware checks include guest code that attempts forbidden operations; they are not host-side assertions alone.