Documentation
How Alpymist works, and why
Alpymist writes its reasoning down. Each foundational choice is an architecture decision record: what forced the decision, what was chosen, and what it costs. They are the best introduction to the project there is.
Start here
- Install Add the signed repository to Alpine, or build an ISO.
- Building from source The Rust workspace, the builder container, and booting an image in QEMU.
Decisions
- One desktop, three renderers Two requirements pull in opposite directions:
- Everything is a signed package The most substantive technical criticism aimed at Omarchy-style projects is about delivery, not taste:
- Foundational choices Four decisions taken at project start. Recorded together because each was a genuine fork, and because the reasoning matters more than the outcome when we revisit them.
- Confining unsafe, and why our binaries are not static Two decisions forced by building the EGL probe. Both are consequences of the same thing: asking the graphics stack a question means talking to C.
- Alpine 3.24 as the base, and why stable is now enough Two constraints had to meet. DeniseUI 0.24 — the toolkit the splash and installer are built on — requires rustc 1.95. And ADR 0003 chose to base Alpymist on Alpine stable rather than edge.