A NEW DESKTOP EXPERIENCE · IN DEVELOPMENT

Clover
Splash.

A desktop operating system project by Woods Studio. Built around Obsidian—a distinctive interface, an integrated application family, and a security-focused architecture.

Early developmentx86-64 UEFI targetLinux-based architecture
01 / Introduction

Designed as one cohesive experience.

Clover Splash brings together a streamlined desktop, consistent applications, and a planned system foundation designed for predictable updates and recovery.

◈

Distinctive by design

Floating navigation, custom window controls, consistent iconography, thoughtful motion, and adaptive appearance.

▣

System reliability

A planned read-only system architecture with separate user data and alternate system images.

◇

Control and clarity

Explicit installation decisions, visible system status, and recovery workflows designed around user control.

ⓘ
Development preview

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.

02 / Obsidian

Meet your new desktop.

Obsidian is the planned graphical environment for Clover Splash, with floating controls, a centered application dock, and a unified visual language.

See Obsidian in a new light ✨

Try changing the appearance to explore the different official wallpapers.

Clover◈   FilesFile   Edit   View
◉   10:24
Files× − □
⌂   Home
▤   Documents
▧   Downloads
◇   Devices
Welcome to Obsidian.

A preview of the intended window layout, floating navigation, and glass surfaces.

Illustrative interface · not a functional file manager

FilesClover StoreTerminalCalendarClockCalculator

Conceptual desktop composition using official Clover Splash assets. Features shown are not necessarily implemented.

☷

Floating navigation

Three dedicated controls for the Clover menu, active application, and application commands.

▦

Independent windows

Custom window controls, app switching, and planned workspace behavior across displays.

◐

Adaptive appearance

Auto, Light, and Dark themes with official Obsidian wallpapers.

03 / Applications

Made to work together.

Explore the planned first-party application family. Official icon assets are included where available; functional implementation varies by app.

The application collection

One dock. A whole world of apps.

Tap the dock to reveal the Clover Splash application family. Every icon is part of the Woods Studio visual identity.

20 applications on the roadmap

Application icons and launcher previews do not indicate completed functionality.

04 / Architecture

A considered foundation.

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.

01
Firmware & bootx86-64 UEFI, verified boot components, recovery selection
02
Kernel & base systemLinux kernel, drivers, service management, devices and networking
03
Graphics & shellWayland integration, Obsidian desktop, dock and window coordination
04
System servicesAuthorized settings, updates and device management
05
ApplicationsWoods Studio apps and future supported third-party software
Proposed GPT storage layout

Separate. Verify. Recover.

Alternate system and recovery images are intended to support staged updates and controlled fallback, with personal data stored separately.

EFIBoot
System ARead-only
System BAlternate
DataLUKS2 target
Recovery ARecovery
Recovery BAlternate
!
Specification, not installer capability

Current prototypes do not implement this partition layout or write to physical disks.

05 / Security & recovery

Trust should be verifiable.

The security model is designed around authenticated components, narrowly scoped privileges, encrypted personal data, and recoverable system updates.

♢

Authenticated boot

Planned verification of boot-critical components through an appropriate signed boot chain.

▤

Immutable system

Read-only images and integrity validation to protect operating system components.

⇄

Signed updates

Validated update artifacts staged into an inactive system slot with a fallback path.

⌑

Encrypted data

Planned LUKS2 protection and a recovery mechanism controlled by the device owner.

⊞

Authorized services

Privileged operations restricted to authenticated, narrowly scoped system interfaces.

↶

Recovery and rollback

Independently verifiable recovery paths with explicit disclosure of destructive actions.

!
Security features are planned, not yet verified

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.

06 / Installation

Clear choices at every step.

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.

Welcome & compatibility

Review requirements and inspect hardware and firmware.

Destination selection

Choose a disk and review the proposed partition layout and destructive operations.

Encryption & recovery key

Configure encryption, generate a recovery key, and confirm it is safely recorded.

Install & verify

Review progress, validation results, and complete with a user-controlled restart.

Installer development

Prototype first. Disk writes later.

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.

!
Future installation will erase data

A future full-disk installer will erase the selected destination. Back up important data before testing any disk-writing release.

07 / Development

Building it, one layer at a time.

Development is iterative. These milestones describe intended work, not committed release dates.

Obsidian desktop foundation

Navigation, dock, themes, window behavior and app framework.

Prototyping
Core applications

Files, Preferences, Terminal and essential utilities.

Planned / incremental
System integration

Real services, authorization boundaries and Wayland shell integration.

Planned
Bootable OS image

Assemble and boot the base system in a virtual machine.

Not validated
Installation, security & recovery

Storage, encryption, authenticated updates and recovery workflows.

Architecture target
Hardware validation

Graphics, networking, input, suspend/resume and physical installation testing.

Future milestone
Woods Studio · Clover Splash

A new desktop is taking shape.

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 ↑