errors
shared failure vocabulary
→Redox OS responsibilities recast as small mechanisms with bounded state, visible invariants, and orchestration kept outside the primitive.
The browser model exposes the control grammar. Advance one bounded mechanism at a time, then compare it with the real readiness record below.
A slot and generation become a bounded, stale-safe resource identity.
This proof surface explains the architecture. The real readiness gate runs against Redox, QEMU, and the VirtIO-GPU driver in the maintainer environment.
The public harness no longer imports an ignored local kernel checkout. Each atom family builds on its own and every Rust crate stays below the 4,000-line ceiling.
shared failure vocabulary
→generation-checked identity
→resources, commands, health
→vibration and traffic projection
→device and display mechanisms
Local folders, public forks, extracted snapshots, and misleading names were compared by implementation depth, recency, tests, and provenance.
Fresh resource atoms, bounded lane service, reset/reclaim/replay work, deterministic evidence gates, and current launch proof.
PUBLIC AS LUCERNA-LABS / ATOM-REDOX-KERNELCapability authority wall, graph min-cut quarantine, EventRing, EEVDF, and portable driver primitives remain important implementation lineage.
LINKED, NOT MISREPRESENTED AS THE FRESHEST LABThe Redox mirror contains no Atom conversion; extracted kernel folders are provenance-managed source snapshots rather than publishable repositories.
KEPT OUT OF THE PUBLICATION UNITThe selected source passed the complete maintainer gate before publication. The artifacts stay local because disk images and raw logs are intentionally excluded; the scripts, fixtures, implementation record, and claim boundary are public.
“Kernel conversion to atoms” is the architecture direction and the implemented subsystems shown here. It does not mean the whole Redox kernel is converted, production-ready, or certified across physical GPUs.