Distinctive by design
Floating navigation, custom window controls, consistent iconography, thoughtful motion, and adaptive appearance.
Clover SplashBY WOODS STUDIOA desktop operating system project by Woods Studio. Built around Obsidian—a distinctive interface, an integrated application family, and a security-focused architecture.
Clover Splash brings together a streamlined desktop, consistent applications, and a planned system foundation designed for predictable updates and recovery.
Floating navigation, custom window controls, consistent iconography, thoughtful motion, and adaptive appearance.
A planned read-only system architecture with separate user data and alternate system images.
Explicit installation decisions, visible system status, and recovery workflows designed around user control.
Clover Splash is not a production-ready operating system. Current desktop and installer builds are application-level prototypes; the bootable OS, signed boot chain, encryption, and recovery mechanisms remain development goals.
Obsidian is the planned graphical environment for Clover Splash, with floating controls, a centered application dock, and a unified visual language.
Try changing the appearance to explore the different official wallpapers.
Clover◈ FilesFile Edit ViewA preview of the intended window layout, floating navigation, and glass surfaces.
Illustrative interface · not a functional file manager






Conceptual desktop composition using official Clover Splash assets. Features shown are not necessarily implemented.
Three dedicated controls for the Clover menu, active application, and application commands.
Custom window controls, app switching, and planned workspace behavior across displays.
Auto, Light, and Dark themes with official Obsidian wallpapers.
Explore the planned first-party application family. Official icon assets are included where available; functional implementation varies by app.
Tap the dock to reveal the Clover Splash application family. Every icon is part of the Woods Studio visual identity.
Application icons and launcher previews do not indicate completed functionality.
The target architecture combines a minimal Linux-based system with Qt 6/QML interfaces and a Wayland-based graphics stack. Integration choices remain subject to testing.
Alternate system and recovery images are intended to support staged updates and controlled fallback, with personal data stored separately.
Current prototypes do not implement this partition layout or write to physical disks.
The security model is designed around authenticated components, narrowly scoped privileges, encrypted personal data, and recoverable system updates.
Planned verification of boot-critical components through an appropriate signed boot chain.
Read-only images and integrity validation to protect operating system components.
Validated update artifacts staged into an inactive system slot with a fallback path.
Planned LUKS2 protection and a recovery mechanism controlled by the device owner.
Privileged operations restricted to authenticated, narrowly scoped system interfaces.
Independently verifiable recovery paths with explicit disclosure of destructive actions.
Trusted boot must not depend on a live CDN or GitHub API response. Recovery operations can carry data-loss risk; recovery keys must not be silently uploaded or escrowed.
The proposed distribution is a bootable installer image, not a general-purpose live desktop release. The initial installation model targets an explicitly confirmed full-disk installation.
Review requirements and inspect hardware and firmware.
Choose a disk and review the proposed partition layout and destructive operations.
Configure encryption, generate a recovery key, and confirm it is safely recorded.
Review progress, validation results, and complete with a user-controlled restart.
The current Qt/QML installer is a safe multi-step simulation. It can demonstrate navigation, confirmation, and progress reporting without partitioning, formatting, or installing an operating system.
A future full-disk installer will erase the selected destination. Back up important data before testing any disk-writing release.
Development is iterative. These milestones describe intended work, not committed release dates.
Navigation, dock, themes, window behavior and app framework.
Files, Preferences, Terminal and essential utilities.
Real services, authorization boundaries and Wayland shell integration.
Assemble and boot the base system in a virtual machine.
Storage, encryption, authenticated updates and recovery workflows.
Graphics, networking, input, suspend/resume and physical installation testing.
Explore the design, follow the development milestones, and see how Obsidian evolves from a desktop prototype into an integrated operating system experience.
Back to top ↑