Admission is the step between a node being declared and being ready. It answers: may this node start now?
Architecture contract
An admission controller checks, before any executor is spawned:- Policy. The node’s capability request and grants are allowed. A hard deny ends it here.
- Capacity. Spawn caps are not exceeded, and an executor that can run the node is available. Executor probes are auth-aware: an executor that is not signed in is not available.
- Budget. The run’s budget has room. Budgets fail closed.
Current implementation
- The spawn gate runs on every spawn of a work-item-bound turn. Work-bound executor paths are being converged on the Allternit policy gate; direct interactive runtime behavior may differ from Agency/work-runtime execution.
- Execution environment. Each spawned node gets a resolved environment: a working directory, an allowlist of environment keys (never the whole process environment), filesystem scope and a network policy. The default network policy allows only public destinations, enforced by a shared egress guard that refuses private, loopback, link-local and similar ranges and resolves a name once so DNS rebinding cannot swap the address. The resolved document is recorded in the ledger.
- Spawn caps and capacity admission live in the drive runner, which is an opt-in operator command. Caps are shared by every drive process on the machine.