Expand description
Which isolation tier a tool runs in, what it enforced, and the record of what actually confined a step.
Named here, in the crate with no execution in it, because four layers need
the same vocabulary and none of them should have to depend on the others to
get it: a tool manifest declares a tier, the compiler checks it against
the profile a flow claims, the sandbox is one and reports what it
Confinement amounts to on this host, and the ledger records the
Isolation a step actually ran under (US-0508).
The last of those is what turns “this ran confined” from a claim into a
fact: bg plan says which tier a tool needs and a tier says what it
can do here, and neither says what happened.
ARCHITECTURE.md D1 schedules all four — in-process now, subprocess as the
Layer 3 target through M2 to M6, Wasmtime at M7 for Profile C, Firecracker
later — so the enum is complete from the start even though two of them are
not built yet. A tier arriving later should be a new implementation, not a
new word.
Structs§
- Confinement
- What a tier actually enforces, per domain, on this host.
- Isolation
- What actually confined one step (US-0508).
- Worker
- Which reused worker served a step, and how much it had already done (US-0909).
Enums§
- Enforcement
- How strongly a tier confines one resource domain.
- Tier
- How strongly a tool is isolated from the machine it runs on.