What A Real Distribution Needs¶
The current Den prototype demonstrates a boot path. A complete conda-owned operating system would need more than a boot path.
Package Channel¶
Den-owned packages need to be published through the package forge as normal conda channels. The current release-channel plan is a hosted static channel root:
https://packages.den-os.org/den-forge/den-2026.6
The build must keep package reads public and ordinary for conda while keeping uploads restricted to the package forge CI and operator credentials.
Artifact Provenance¶
Every boot artifact needs provenance:
source URL,
source hash,
build tool version,
build configuration,
source commit,
dirty-tree state,
generated artifact hashes.
The QEMU bundle manifest is the first small step in this direction. The UEFI raw/qcow2 disk image is another local artifact, but it does not yet carry a release manifest beyond the files already embedded in the rootfs.
SBOM And License Reports¶
Before redistribution, Den needs:
Buildroot
legal-info,conda package license manifest,
SBOM for the rootfs,
source and patch provenance for kernel, BusyBox, Buildroot, systemd, and Den recipes.
Signing¶
A complete distribution would need a signing story for:
package artifacts,
lockfiles,
rootfs images,
initramfs,
kernel,
boot manifests,
release metadata.
Boot Targets¶
The prototype boots QEMU directly with:
kernel + initramfs + rootfs ext4
The prototype also has a first QEMU UEFI disk form:
GRUB EFI + kernel + initramfs + rootfs partition
Future targets still need:
systemd-boot layout,
optional unified kernel image,
provider-ready cloud image metadata,
installer.
The current OCI image is useful for inspection and CI-style userland checks. The current raw/qcow2 disk proves the UEFI handoff in QEMU. Neither one is a complete release image.
Updates On A Running Machine¶
The staged-rootfs generation smoke exercises the model outside a live system. A future Den system would need a command that can:
read configured channels,
solve or consume a lockfile,
install a new generation,
record metadata,
validate the generation,
activate it,
integrate with systemd reboot and rollback behavior.
Users And Login¶
The prototype has minimal account files and a locked root account. It can boot systemd and expose console units, but a complete system would need:
user creation,
password or key-based authentication,
PAM or a deliberate non-PAM alternative,
SSH policy,
recovery access.
Release Engineering¶
Den needs a release process that can answer:
which package set defines this release,
which early boot layer built it,
which channels were trusted,
which keys signed it,
which platforms are supported,
how long it receives updates.