Incus Manager

The Outpost breaks the Proxmox baseline on purpose. It runs Incus, a container and VM manager suited to workloads that are created and destroyed constantly — the practice forks of the Climb, spun up per learner and thrown away after, and the disposable targets of the live-fire range. Proxmox could do this; Incus does it lighter and faster for ephemeral system containers, which is why the one exception to an otherwise-uniform hypervisor standard lives here.

The Outpost is dual-purpose by design, hosting both the range and the Climb’s forge, tracker, and grader on a single node — a tight fit with little headroom, tracked openly among the open questions in the Hardware Manifest.

Has anything touched?

If reading this made you want to argue with it, extend it, or notice what's missing, that's the signal to show up.

You're invited to:

commit register to step into opplet partner advance or support the development sync chat or stay without committing deploy clone or fork opplet as your enclave
:/back-to-top