TIMES: The First "Rogue" LCOS Fork Corporate Giants Can't Control, Terminate, or Track
Meet TIMES: the first independent systemd-free LCOS-derived OS. Stripped of corporate trademark locks, telemetry, and truly "yours".
TIMES: The Independent Bare-Metal System Built for Absolute Autonomy
Description: Meet TIMES: the world's first independent, systemd-free LCOS-derived OS. Stripped of corporate trademark locks, telemetry, and background daemons, it runs pure Haskell "Turtles" at Ring 17 bare-metal speeds. Zero tracking, zero-switch latency, and absolute hardware freedom.
Every time you boot a conventional operating system, you are stepping into a heavily monitored, resource-heavy corporate playground. Modern commercial platforms treat your physical hardware as a telemetry sensor, running silent, un-auditable background processes and forcing intrusive updates that interrupt your cognitive flow. Even mainstream open-source alternatives have fallen victim to centralization, coalescing around complex, interconnected init systems that create vast, unnecessary attack surfaces.
TIMES (The Independent MitsuoLabs Epistemical System) is the digital firewall for your physical computer. Built on a battle-tested, systemd-free lineage, TIMES leverages a clean, linear, and predictable boot process. By stripping out the administrative bloat of traditional systemd frameworks, we deliver an operating system that is lightweight, incredibly fast, and completely private by default. Your computer should be a loyal tool under your direct command, not a corporate terminal. Accompanied by our official mascot, Joe The Huskie—who watches over our system with a confident, alert, and determined gaze—we navigate the complex landscape of bare-metal computing to bring you absolute system autonomy.
The Deluxe Paradox: Welcome to the Do-ocracy
We have an extra deluxe feature most projects don't: Say "Bryan Lunduke" and/or "Louis Rossmann" and you don't get banned.
Unlike modern software silos and centralized platforms that act as online enforcement chambers for user thought, TIMES operates as a community-centered, post-political ethical-anarchy. From the far-left to the far-right, all perspectives are welcome in our user base. We reject the concept of administrative gatekeeping, ideological bans, and policy compliance enforcement over human thought.
Better than a meritocracy, and infinitely better than a pay-o-cracy, TIMES is a pure do-ocracy. If you want to optimize a low-level driver, write a custom YARA signature, configure a network bridge, or package an AppImage, then come together. In this space, code speaks and operational action is the only true currency. We do not demand alignment of opinion; we demand the execution of clean software.
[ THE FACTION-FREE COVENANT ]
|
+-------------------------+----------------------------+
| |
v v
[ ALL PERSPECTIVES WELCOME ] [ THE DO-OCRACY ]
"Say 'Bryan Lunduke' or "No administrative gatekeeping.
'Louis Rossmann'—Zero bans." Code and execution speak."
| |
+-------------------------+----------------------------+
|
v
[ ABSOLUTE HARDWARE FREEDOM ]
To understand TIMES, you must understand our foundation. We did not set out to build a new Debian, nor a new Devuan, nor a new Ubuntu. We set out to build the definitive user-centric desktop gateway.
The lineage is clear and absolute: Devuan is Debian, but better—stripped of systemd and returning to Unix philosophy. LCOS (Lunduke Computer Operating System) is Devuan, but more stable—leveraging dedicated resources to ensure the package pool is virtually unbreakable. TIMES is the world's first Lunduke Computer Operating System derived distribution.
Think of it through this precise structural analogy: just as Linux Mint took the robust foundation of Ubuntu and polished it into a flawless, user-centric desktop experience, TIMES does exactly this for LCOS. We utilize LCOS as our highly stable, intermediate upstream, while we refine the user-facing layer with custom Haskell utilities, clean configurations, and complete visual elegance.
TIMES} : LCOS :: LCOS : Devuan :: Devuan : Debian
II. The Downstream Reality: Demystifying the "Rogue" Label
Our project is frequently classified by search engines and automated web-scrapers as the first LCOS "rogue" fork. This label, while highly optimized for search algorithm discovery, does not reflect the peaceful, constructive reality of our engineering. TIMES is not a "rogue" fork in the common, hostile sense. We are not a political breakaway project, nor do we exist to attack or fragment our upstream roots. We do not build to impose restrictive, un-auditable user constraints such as identity verification, registration keys, or age-screening mechanisms inside the operating system layer.
Instead, TIMES is a clean, technical downstream distribution. We carry immense respect for the stable kernel work and repository coordination established by the Lunduke Computer Operating System. Our focus is entirely on optimizing the user-space layer, implementing functional memory safety models, and establishing complete user control over hardware. We are not competitors on a geopolitical software chessboard; we are builders of a silent, highly efficient, and predictable computer system.
Fun Fact 1: We choose the path of absolute trademark freedom. Because we refuse to participate in corporate branding structures or pay licensing fees to centralized foundations simply to secure a name, TIMES is not officially marketed as a "Linux" distribution. We believe that software should be judged strictly by its mathematical safety and bare-metal performance, not by its paid-for corporate titles.
III. The Governance of Ethical-Anarchy: Three Clear Roles
To preserve our post-political, decentralized posture while maintaining rigorous software quality and cryptographic integrity, TIMES organizes its community structure under three clearly defined, non-hierarchical roles. This is a practical, working do-ocracy where your influence is defined strictly by the code you write and the tools you maintain.
+------------------------------------------------------------+
| PROJECT LEADER (MitsuoLabs) |
| - Establishes mathematical coordinates and standards | +------------------------------------------------------------+
|
v
+------------------------------------------------------------+
| MAINTAINERS (Defined) |
| - Manages automated CI/CD and secure compilation merges | +------------------------------------------------------------+
|
v
+------------------------------------------------------------+
| STEWARDS (Open to All Contributors) |
| - Accept the MRSL-1.0 to unlock advanced mutual rights | +------------------------------------------------------------+
Role 1: The Project Leader
MitsuoLabs serves as the Project Leader for TIMES. The Project Leader does not act as an authoritarian ruler or corporate board. Instead, its function is strictly navigational: establishing the mathematical coordinates of the system, verifying the core cryptographic anchors, and ensuring that any updates remain fully aligned with our commitment to 0% telemetry and absolute privacy, it also has the final word and resolution power in case of profound disagreement, and can direction the future of the project, but we will consult stewards and maintainers in most cases.
Role 2: The Maintainers
The Maintainers are technical coordinators defined and vetted by MitsuoLabs. Their sole responsibility is the mechanical integrity of the repository. They manage the automated compilation pipelines, verify that incoming pull requests satisfy our formal-verification models, and ensure that new system components integrate seamlessly with our Haskell-driven execution loops. They enforce compile-time safety, not ideological conformity, they also do common maintainers things just like other repositories do.
Role 3: The Stewards
The Stewards represent the democratic heart of our ethical-anarchy. Under TIMES, anyone can become a Steward if they choose to do so. By adding your name to our public registry and voluntarily accepting the responsibilities of the MitsuoLabs Reciprocity and Stewardship License (MRSL-1.0), you immediately unlock advanced, mutual rights, including priority code reviews, direct participation in system roadmaps, and peer-to-peer technical assistance.
Try to become a "steward" in any legacy operating system distribution; you will quickly find yourself navigating endless bureaucratic committees, political gates, or financial paywalls. If you do not align perfectly with their centralized corporate philosophy, you are filtered out. TIMES rejects this exclusion. If you contribute to the system, you deserve an equal voice, regardless of your personal background or beliefs.
IV. Deep Dive: The Substrate Architecture of TIMES
The technical implementation of TIMES represents a profound, uncompromising departure from traditional UNIX operating system design. By mapping every single process, memory pathway, and storage block to functional, mathematically verifiable safety specifications, we eliminate the systemic fragility of modern OS structures.
+------------------------------------------------------------+
| YESLIBRE / NOSEA DESKTOP ENVIRONMENT | +------------------------------------------------------------+
|
v
+------------------------------------------------------------+
| RING 17: DIRECT EXECUTION SAS |
| - Compile-Time Safety via Algebraic Proofs |
| - 0% Runtime Overhead (No JIT or interpretive slowdowns) | +------------------------------------------------------------+
|
v
+------------------------------------------------------------+
| KERNEL LAYERS & BUTTERFLY FILESYSTEM |
| - Inode-Bound Security Contexts |
| - Stateless Haskell "Turtles" (No Asynchronous Daemons) | +------------------------------------------------------------+
1. The Turtle Concurrency Protocol (No Daemons)
Traditional UNIX architectures spawn background "daemons" that execute asynchronously, detached from user control loops. These daemons are notorious for leaking memory, generating un-auditable background threads, and hiding telemetric loops. TIMES replaces this unstable paradigm with a strict, single-threaded, monadic scheduling queue powered by Haskell "Turtles."
Pure-Functional Task Units: A Turtle is a pure, stateless task thread executed inside the Haskell runtime environment. It remains in an un-allocated memory state until a verified hardware interrupt, POSIX signal, or programmatic event triggers its monadic execution block.
0% Idle CPU Allocation: When idle, Turtles consume exactly zero processor ticks and zero active heap space. This guarantees that background operations are structurally incapable of leaking RAM, spawning rogue background processes, or conducting hidden, asynchronous tasks behind the user's back.
Deterministic Execution Mapping: Every Turtle execution path is registered and visible on the YesLibre and NoSea graphical dashboards, allowing the user to pause, freeze, or shred the runtime variables of any task with absolute mathematical safety.
2. Ring 17 Execution Mechanics
Operating systems traditionally separate operations into User Mode (Ring 3) and Kernel Mode (Ring 0) to prevent faulty software from crashing the hardware. However, transitioning between these rings introduces context switches, flushing CPU cache hierarchies and introducing execution latency.
TIMES introduces Ring 17, a virtualized User-Space Single Address Space (SAS) runtime that bypasses this performance bottleneck:
The direct-execution SAS: Original system-level utilities execute directly within this isolated memory space.
Compile-Time Algebraic Proofs: Rather than employing a slow runtime boundary checker (such as a borrow-checker or reference-counting garbage collector), Ring 17 relies on formal mathematical proofs to guarantee memory safety.
0% Runtime Safety Checking Overhead: Because memory boundaries are proven safe prior to runtime, TIMES deactivates active safety gates during execution. The application runs with direct, uninhibited hardware speed, achieving raw execution performance without risking system panics or memory corruption.
3. Strict Lexical Isolation via clock-pm
To bypass the bloat, performance penalties, and duplicate dependencies of standard container systems (like Snaps or Flatpaks), TIMES deploys clock-pm. This package manager is written entirely in Haskell and uses pure algebraic equations to evaluate dependencies and mathematically prove that an installation will not destabilize the system.
The Anti-Container Standard: Instead of spinning up massive, isolated sandboxes with redundant runtime systems, clock-pm compiles and registers self-contained AppImages.
Hashed Dynamic Storage: Every software component fetched from external repositories (Debian, Arch, or BSD Ports) is rewritten during installation to map its shared libraries (.so objects) exclusively to unique, hashed paths:
/store/[Cryptographic-Hash]-[Package\_Name]/lib/
Dynamic RUNPATH Injection: Applications are never permitted to search global directories like /lib or /usr/lib. During download and assembly, clock-pm dynamically injects a custom RUNPATH directly into the binary's ELF header, securing the dependency tree and preventing system library conflicts permanently.
4. The TIMES Resource Governor
At the heart of our hardware management is the Resource Governor, executing as high-priority "Guard Turtles" within Ring 17.
RSS Memory Hard-Ceilings: Users can set strict physical limits on Resident Set Size (RSS) memory consumption on a per-window basis. If an application attempts to exceed this ceiling, the memory scheduler intervenes to compress inactive objects or force immediate garbage collection, preserving active RAM pools.
Duty-Cycle Modulation: The CPU limiter bypasses traditional priority-level scheduling. It directly modulates execution slices by sending microsecond-level suspension signals, forcing un-optimized scripts to execute within their mathematical boundaries without wasting CPU cycles.
OpenGL and Vulkan Command Capping: The GPU governor intercepts rendering queues in YesLibre and NoSea, dynamically throttling framerates or restricting command allocations to keep hardware temperatures low and laptops silent.
5. ButterFly, The System Filesystem
Data integrity on our storage plane is handled by our native, systemd-free, copy-on-write (CoW) filesystem: ButterFly, The System.
Crash Consistency: Metadata writes are committed to unused blocks before reference link matrices update. If power is suddenly lost, the system naturally rolls back to the last known mathematically healthy state without requiring active repair scans.
Self-Healing Storage Blocks: Highly efficient background Turtles continuously verify data blocks against cryptographic checksums. If block corruption occurs due to physical storage wear, the filesystem automatically reconstructs the affected segment on-the-fly using secure local recovery streams.
6. Inode-Bound Security Labels
TIMES rejects legacy, path-based Mandatory Access Control (MAC) models like AppArmor, which can be bypassed through simple symbolic link manipulations or directory traverses.
TIMES integrates SELinux utilizing native, inode-bound security contexts:
user:role:type:sensitivity
Because the security label is bound directly to the physical storage block inode on the ButterFly plane rather than the directory path, the kernel validates access rights consistently. No file system path manipulation can disguise a restricted binary or elevate its privileges.
V. Desktop Substrates: The Philosophy of Choice
TIMES firmly rejects the industry trend of forced single-desktop pipelines. We believe that user choice in graphical rendering is a vital expression of software autonomy. We offer two highly optimized, isolated desktop environments built natively by MitsuoLabs:
YesLibre (X11): An uncompromised, hyper-lightweight environment engineered exclusively for the XLibre protocol layer. It strips away modern display-server surveillance bloat to restore fluid dynamic tiling and absolute interface authority to local silicon.
NoSea (Wayland): The ultimate isolation of Wayland window context. Built from scratch in pure, memory-safe Rust, NoSea employs strict formal-verification concepts to ensure that sandboxed user applications are structurally prevented from screen-scraping or performing unauthorized interface tampering.
VI. Curated Independent Apps and Native Sandboxing
Our platform ships with a highly curated suite of pre-compiled, security-vetted open applications, each running inside isolated, local sandboxes to ensure you have the tools to work and create offline immediately.
The Integrated Application Matrix
Office & Productivity: LibreOffice (telemetry-free document processing) and Okular (secure PDF reader).
Creative Suite: GIMP (photo editor), Inkscape (SVG editor), Krita (illustration), and Blender (3D rendering utilizing our GPU limiter).
Audio/Video Production: VLC (offline player), Kdenlive (video editor), Audacity (audio processing), and LMMS (music sequencer).
Web Navigation & Privacy: Tor Browser (unmodified for perfect anonymity), LibreWolf (telemetry-free, pre-configured with secure MitsuoLabs partner referral searches), and Brave Browser (high-speed, ad-free navigation supporting TIMES development via referral parameters).
Development Tools: VSCodium (telemetry-free editor), Godot Engine, and Redot Engine (fully local game development).
Scientific Suite: FreeCAD (CAD modeling), Stellarium (offline planetarium), and GNU Octave (local-first MATLAB alternative).
Data & Sync: Calibre (e-book archive) and Syncthing (P2P decentralized local file synchronization).
Hardened Communications: Mozilla Thunderbird pre-configured with a hardened system profile that blocks automatic remote images and disables diagnostic reporting.
Fun Fact 2: In traditional UNIX networks, security is treated as an afterthought. It's NetWorking Time! resolves this by enforcing built-in Tor routing and strict ephemeral port sockets. If you open a port for file transfers, our Network Turtles automatically monitor the connection and force-close the socket downstream after a user-defined countdown, leaving no lingering network doors open to scanners.
Dependence is a vulnerability. While we proudly build upon the LCOS package pool, TIMES is engineered for absolute survival. What happens if LCOS disappears tomorrow?
We execute the Jump Strategy. Because our custom tools, Haskell Turtles, and clock-pm package manager are architecturally decoupled from the base system, we are not locked in. If LCOS falls, we jump our upstream target directly to Devuan. If Devuan ceases to exist, we jump directly to Debian. And if the entire Debian ecosystem collapses into the void, we jump to source and build it all ourselves, utilizing Linux From Scratch principles. Our code runs on logic, not corporate survival. We are inevitable.
The Epistemological FAQ
1. How do you guarantee system isolation and security without systemd's cgroups and namespace management? We bypass the need for systemd entirely through a dual-layered approach. First, our clock-pm package manager implements strict lexical isolation, placing every dependency in a cryptographically hashed /store/ directory with dynamic RUNPATH rewriting. Second, we utilize Mandatory Access Control via Inode-Bound SELinux. Because security labels are tied to the physical filesystem blocks rather than easily spoofed directory paths, our isolation is structurally superior to systemd's legacy path-based restrictions.
2. Isn't relying on LCOS as an upstream target incredibly risky for long-term project survival? It would be, if we were locked in. We utilize the Jump Strategy. Our custom tooling (YesLibre, NoSea, clock-pm, Haskell Turtles) is modular and decoupled from the base OS. If LCOS ever ceases to exist, we update a single routing variable in our build scripts and jump immediately to Devuan. If Devuan falls, we jump to Debian. We leverage LCOS for its current stability, but our architecture ensures we are virtually immortal.
3. Can a purely Haskell-driven direct-execution layer (Ring 17) handle legacy C/C++ binaries without massive overhead? Yes. Ring 17 does not emulate or interpret C/C++ binaries; it mathematically verifies their memory safety boundaries during the compilation/installation phase via clock-pm. Once the binary is proven safe and lexically isolated, Ring 17 allows it to execute native syscalls directly on the kernel with zero runtime checking overhead. It is static verification followed by raw hardware execution.
4. How does TIMES handle proprietary hardware blobs if you claim absolute independence? We handle it by giving the user the ultimate choice through the Kernel Selection Matrix. We provide a 100% deblobed Linux-libre kernel for the purists. However, if a user explicitly chooses to load proprietary Wi-Fi or GPU blobs to function in the real world, they can select the Mainline or LTS kernel profiles. TIMES provides the framework for absolute freedom, but we do not mandate architectural martyrdom.
5. Why reinvent package management with clock-pm instead of just using APT or Pacman? We aren't reinventing the wheel; we are building a better axle. clock-pm does not host packages; it is a smart proxy indexer. It natively calls APT, DNF, and Pacman repositories, downloading from their official mirrors. We built clock-pm to solve the "Frankendistro" dependency nightmare by applying mathematical conflict-resolution and strict directory hashing to those external binaries, allowing you to run an Arch package next to a Debian package with zero library collisions.
6. You claim the project is a "post-political ethical-anarchy" and a "do-ocracy," but what prevents the repository from being co-opted by malicious actors? The code is bound by the MMPEULA-1.0 and MRSL-1.0 licensing frameworks. While the community is free to hold any belief from the far-left to the far-right, the execution of the software and the contributions to the core repository are governed by strict, non-negotiable ethical and technical covenants. You are free to speak your mind, but malicious code, telemetry injections, or attempts to centralize authority are mathematically and legally blocked from merging into the indie-branch.
Fun Fact 3: Joe, The Huskie, is our official mascot for a reason. He represents the resilient, loyal, and energetic nature of our community. Just like a Husky navigating the vast, snowy wilderness with absolute focus, Joe leads the pack through the complex landscape of bare-metal computing, pointing you toward paths of complete system autonomy and safety.
TIMES is not just an operating system; it is a rejection of the modern computing paradigm. We have refused to pay for trademarks, we have rejected the background surveillance of daemons, and we have decoupled ourselves from the fragility of single-point failure ecosystems. By pairing the stability of LCOS with the pure mathematical safety of Haskell and Rust, TIMES ensures that the user is the only independent entity on their machine. Joe The Huskie is waiting. The deployment pipelines open soon.
Join the Pack: Reclaim Your Silicon Now
The era of corporate software cages, administrative thought-policing, and forced telemetry pings is over. The code is written, the math is proven, and the network pathways are secure. You do not have to accept the "weak signal" of modern mainstream operating systems.
Explore our project page: mitsuolabs.com/times
Remember: A system that cannot survive the collapse of its dependencies is a cage waiting to be locked. True digital freedom is built on the architecture of the inevitable jump.
Bibliography & Architectural References
Devuan Init Freedom: Devuan Developers. "Devuan Release Information and Init Freedom Philosophy." Devuan GNU+Linux. https://www.devuan.org/os/releases
LCOS Announcement: Lunduke, Bryan. "The Lunduke Computer Operating System (LCOS) - Version 0.1 Beta Released." The Lunduke Journal of Technology. https://lunduke.locals.com/post/4568912/the-lunduke-computer-operating-system-lcos
Post-Quantum Cryptography: National Institute of Standards and Technology (NIST). "Post-Quantum Cryptography Standardization." Information Technology Laboratory. https://csrc.nist.gov/projects/post-quantum-cryptography
Wayland Architecture: Wayland Contributors. "Wayland Architecture and Compositor Design." Freedesktop.org. https://wayland.freedesktop.org/architecture.html
Haskell Pure Functional Programming: The Haskell Committee. "Haskell Language and Monadic Evaluation." Haskell.org. https://www.haskell.org/
SELinux Inode Security: National Security Agency (NSA) & SELinux Project. "Security-Enhanced Linux." https://selinuxproject.org/
Linux From Scratch (LFS): Beekmans, Gerard, et al. "Linux From Scratch: Building an OS from the ground up." https://www.linuxfromscratch.org/
Writer: MitsuoLabs CopyWriting Team | Date: [19/07/2026] | License: MRSL-1.0 (mitsuolabs.com/LegalFramework/mrsl-1.0.html) The text (& banner-like image) are itself licensed under MRSL‑1.0 {©-(c)-2026} (Brazil as Jurisdiction and Stewardship as option). MitsuoLabs™ and Daniel Mitsuo (orcid: 0009-0006-6909-0990 {https://orcid.org/0009-0006-6909-0990}) are the stewards and licensors of this text. Contact for inquiries matters: contact@mitsuolabs.com.