# Den System Manager `den` is the first product layer over the Den prototype. Earlier milestones proved that conda packages can assemble a bootable system generation, that rootfs files can be projected from package metadata, and that generation activation can be represented by `/den/current-system`. Those pieces are useful, but a regular user should not have to call low-level build tools or `den-generation` directly for every inspection task. ## Why `den` Exists `den` is the command a user sees inside the OS. It should answer operational questions in the language of the system: - What release is this? - Which generation is active? - Does the active generation validate? - Which channels and lockfile define the system? - What would the next update do? - Can I activate or roll back a generation? The command also gives CI and image smoke tests a stable interface. That makes the image easier to test than raw path checks alone. ## Relationship To `den-generation` `den-generation` is still the lower-level activation tool. It records, validates, activates, and rolls back generation directories. `den` owns the user-facing parts and replaces shell-only inspection and activation logic with Python code that can parse TOML, emit structured diagnostics, integrate with conda's plugin system, and update `/den/current-system` directly. `den-generation` remains a lower-level compatibility and bootstrap tool. The system manager is the command regular users and image smoke tests should call. ## Relationship To Conda The package installs both: ```text den conda den ``` This follows the pattern used by conda-workspaces, conda-completion, and conda-exec: a small standalone command for daily use, plus a conda plugin entry point that exposes the same feature through conda. The conda package requires the conda runtime and conda-workspaces. Den uses those APIs as part of the system manager, and the plugin is loaded from the same runtime prefix. ## Current Boundary `den update` consumes an existing conda workspace archive. It installs the archive as the next generation, writes generation metadata, validates the result, and only then switches `/den/current-system` unless `--no-activate` is used. `den` uses the public conda-workspaces `WorkspaceArchive` API from the Den runtime environment. Solving, locking, and archive creation are still outside the in-OS command. That keeps the first update transaction narrow: it proves the generation activation protocol without making the running machine responsible for the full forge workflow.