Project
Architecture, methodology, and academic context of MimOS.
Build pipeline
Archiso releng → Auditable MimOS overlay → ISO + manifest + SHA-256 → Diskless QEMU checks → Packaged assets → Download and reassembly verification.Technical base
MimOS does not maintain a complete Archiso fork. During the build, it copies the official releng profile and applies a minimal delta: extra package list, branding, and services.
Live system
- ✓Architecture: x86_64
- ✓Desktop: KDE Plasma on Wayland (SDDM)
- ✓Networking: NetworkManager
- ✓Audio: PipeWire + WirePlumber
- ✓Ephemeral Live user: mimos
Installer
Alpha 3's public launcher still opens a disk-disconnected visual prototype. Post-Alpha 3 development completes an internal Calamares path on QCOW2 fixtures, but it remains unavailable to users until the full safety matrix passes.
Centro de MimOS
Centro de MimOS debuted in Alpha 3 with Inicio, Privacidad, and Acerca de, no telemetry, and no network access. The exact image passes autostart, relaunch, local persistence, AT-SPI, and scaling checks. Post-Alpha 3 work also validates its installed context without an installer action.
The first capture is from published Alpha 3; the second is internal post-Alpha 3 evidence and does not make the public release installable.
Future work
Calamares 3.4.2 is packaged and the internal path completes installation, boot, login, and cleanup on QCOW2. Cancellation, inventory, preservation, encryption, and other gates remain before the public launcher can be connected.