—Sovereignty Over Silicon / The Protocol Rebel
YesLibre: The Violent Awakening of Desktop Engineering
The digital landscape has fallen into a deep slumber of corporate-driven desktop sanitization, and it is time to wake up. YesLibre is an uncompromised, hyper-lightweight desktop environment engineered natively, aggressively, and exclusively for the XLibre protocol layer. For years, the industry claimed that Rust-based tooling and heavily over-engineered display frameworks were the only path forward. We ask you: What was Rust? A temporary, corporate-backed compromise. Today, YesLibre is the definitive future.
Built as a raw, calculated offensive against the bloated Wayland ecosystem and its hyper-monitored environments, YesLibre strips away modern display-server telemetry to restore fluid dynamic tiling and absolute interface authority to local silicon. By decoupling from the standard infrastructure and optimizing directly for XLibre, we are dragging the core principles of the classic display architecture out of legacy obsolescence. We are forging it into the ultimate high-performance, untracked hacking environment. No tracking, no forced paradigms, completely serverless—YES, It's Libre.
—The Technical Reality: Architecture Without Compromise
The XLibre Protocol Synergy
YesLibre bypasses the layers of abstraction that plague modern desktop environments. By binding natively to the XLibre protocol layer, it completely eliminates the translation overhead introduced by modern display-server wrappers. This architecture explicitly breaks away from conventional infrastructure: there are absolutely no daemons present in this system. Instead, execution and process lifecycles are managed strictly by specialized background turtles operating asynchronously across a unified local IPC channel. YesLibre integrates every new protocol advancement directly from XLibre, ensuring that every frame is rendered with near-zero latency.
Minimal Expected Machine Conditions
System Memory: 3GB RAM baseline minimum for unhindered operational runtime.
Processor Architecture: Standard x86_64 or ARM64 Quad-Core CPU.
Graphics Hardware: Dedicated GPU or high-performance integrated silicon capable of driving hardware-accelerated XLibre contexts.
Display Target: 2K resolution or better screens preferred, optimized natively for smooth 60-to-120fps outputs.
Network Infrastructure: Zero external socket requirements. Completely localized loopback operations only.
Engineering Lifecycle & Fork Freedom
YesLibre is established as a permanent, one-fork-only departure from the XFCE desktop environment for X11. By executing this definitive split, we absorb the proven structural core of the environment, keeping all future security enhancements, codebase optimizations, and architectural control strictly within our own ecosystem from this moment forward.
Our deployment pipeline follows a rigorous release cadence synchronized with upstream protocol milestones:
Feature Integration: Major update cycles transition to production every 3-to-6 weeks following major XLibre releases.
Security Maintenance: Hotfixes and vulnerability patches are deployed through frequent, standalone security updates.
| Feature | YesLibre + XLibre | Wayland / Hyprland |
|| Memory Overlords | Absolute local memory allocation | Bloated runtime environments
| System Surveillance | Zero telemetry / Completely untracked | Corporate-driven metrics and logging
| Configuration Model | Single static configuration file | Fragmented, multi-layered dependencies
| Architecture Basis | Hardened, optimized local silicon | Centralized, corporate-backed infrastructure
Repository Architecture & Git Freedom
MitsuoLabs does not bow to industry-standard corporate semantics or compliance-driven git conventions. In alignment with our engineering mandates, the repository structures for YesLibre completely eliminate the standard naming paradigms enforced by central platforms.
Development Hub: We do not use branch main nor master.
The Root: All core development, pristine commits, and source code lineages reside exclusively on the indie-branch.
The MitsuoLabs Axiom: MitsuoLabs follows no master, nor do we accept the sanitization of our version control. The software infrastructure must reflect absolute independence at every level—from the first commit to the compiled binary.
The Paradigm Shift
Engineering Mandate: Software should serve the user, not a remote telemetry server. YesLibre enforces this by refusing to compile if any external network hooks are introduced into the core rendering pipeline. It is sandboxed by design, lightning-fast by necessity, and sovereign by choice.
How to Contribute: Joining the Independent Lineage
We do not operate on corporate consensus, bureaucratic pull-request pipelines, or central platform mandates. If you want to contribute to YesLibre, your code must match the absolute autonomy of the architecture.
Where to Contribute
The official homes for development, issue tracking, and peer review are located across our distributed source roots:
GitHub Node: github.com/MitsuoLabs/YesLibre
GitLab Node (Alexandria's Clause): gitlab.com/MitsuoLabs/YesLibre
The Contribution Protocol
Target the Root: All patches, optimizations, and features must be submitted directly against the sovereign-branch. Any merge requests targeting standard corporate branch names will be automatically rejected by our linting hooks.
Turtle Implementation: If you are adding background utilities, they must be written as self-contained, asynchronous turtles utilizing local IPC channels. Do not introduce parent/child daemon architectures.
Zero-Dependency Mandate: Contributions must not pull in external runtime dependencies, tracking libraries, or heavy centralized frameworks. Keep the footprint raw, local, and optimized for XLibre silicon.
Code Quality: Ensure your code is thoroughly documented locally and verified to maintain the 3GB RAM baseline optimization.
Contributor's Oath: By submitting code to YesLibre, you certify that your work is completely free of telemetry, respects total user authority, and answers to no master.
Where to Download?
YesLibre is currently undergoing intensive internal initial development. To ensure the architecture meets our absolute performance and sovereignty standards, the source code and installation binaries are not yet available to the public.
Availability Roadmap
Public Alpha/Beta Access: Open availability is targeted for late 2026 or the beginning/first half of 2027.
Targeted Environments & Platforms
When the deployment pipelines open, YesLibre will officially target and support the following independent, systemd-free, and highly customizable operating systems:
Linux Ecosystem: The Lunduke Computer Operating System, Slackware, Devuan, OpenMandriva, Artix Linux, Vendefoul Wolf and Omarchy (even though they traditionally prefer the Hyprland/Wayland environment, YesLibre will offer a fully optimized XLibre alternative).
BSD Ecosystem: GhostBSD, OpenBSD, and NetBSD.
