Concepts
Three ideas explain what an Executor binary is and why it starts fast: the file is five integrity-protected segments, its supervisor comes in the smallest variant your manifest needs, and interpreted runtimes run from a verified, content-addressed cache.
In this section
Single-binary layout
The five segments of an
OEE!executable, the 128-byte footer, and how the whole file is verified.Supervisor variants
The
coreandextendedvariants ofoee-stub, what each contains, and howoee buildchooses.Runtime cache
Where Python, JVM and Node.js workloads are extracted, how the cache is keyed and locked, and how to move it.
The parts of the Executor
| Part | What it is |
|---|---|
oee | The developer CLI: init, validate, keygen, build, run, inspect, status, stop and runtime. |
oee-stub | The native Rust supervisor at the head of every wrapped binary: signature verifier, sandbox builder, exit-event evaluator, CPU and memory governor, auto-scaler, load balancer and process reaper. |
oee.yaml | The policy manifest: workload, sandbox, resources, auto-scaling, stop policy and exit events, signed with Ed25519 and sealed into the binary. |