The Malleable Computer Is Here. Now Who Holds the Keys? Tony Malott · Published 2026-09-01 https://shareplane.malott.ai/artifacts/omarchy-agent-native-workstation/ Agent-native computing / research snapshot / 30 August 2026 The Malleable Computer Is Here. Now Who Holds the Keys? Omarchy may be the first desktop operating environment to treat AI agents as first-class operators. That makes it more significant than another Linux distro, and exposes the unsolved architecture of agent authority. SharePlane Special Omarchy 4.0.1 Evidence > assertion Architecture first Public-source analysis SharePlane visual analysis. The thesis is not that Linux learned AI. It is that the desktop is being made legible enough for an agent to operate on. Full-resolution PNG ↓ Work identity SP-SPECIAL-OMARCHY-2026-08-30 Lifecycle Local UAT / Unpublished Evidence 16 verified public-source references Relations 8 typed semantic connections Synthesis boundary Independent analysis → SharePlane lens The thesis Omarchy matters because it turns the desktop into inspectable, scriptable state that an AI agent can understand and alter. Its next decisive problem is not usability. It is authority: who may change what, under which policy, with what evidence, and how the machine proves what happened. 100k+ ISO downloads / 7 days Project-reported on 28 Aug 2026. Downloads are not active installs. $10m Omacom Foundation funding Ten founding patrons at $1 million each, per the project. 1 shell Quattro consolidation Quickshell now carries the bar, launcher, notifications, lock UI, policy UI and plugins. 11 days 4.0 → 4.0.1 A security-heavy fast-follow exposed both responsiveness and immature trust boundaries. 01 / Category shift 02 / Quattro 03 / Agent-native 04 / What is inherited 05 / Windows reality 06 / Lifecycle 07 / Security wake-up 08 / Platform trust 09 / Plugin boundary 10 / Enterprise fit 11 / What must come next 12 / SharePlane lens 13 / The future 01 / Category shift This stopped being “DHH’s Arch dotfiles.” That description was once directionally fair. In August 2026 it is technically amusing and strategically obsolete. Omarchy is still built from conventional Linux primitives: Arch Linux, systemd, Wayland, Hyprland, pacman, Btrfs, LUKS, Quickshell, KVM and a large body of ordinary open-source software. It did not invent a new kernel or new graphics stack. The innovation is the contract binding those pieces together. That contract now covers installation, defaults, shell behavior, package channels, migrations, themes, plugins, agent launchers, snapshots, recovery, a Windows fallback and a growing hardware story. The project itself describes Omarchy as “the malleable OS for the age of agents.” That positioning is not decorative. It names the architectural idea that separates Omarchy from a conventional distribution. The relevant question is no longer “Is this Arch with opinions?” It is “Has someone finally productized Linux as an agent-addressable workstation?” The answer is increasingly yes. 02 / Quattro Quattro changed the category. Omarchy 4.0, released 14 August 2026, replaced a typical Linux desktop assembly with one persistent Quickshell process called omarchy-shell . Waybar, Walker, Mako, SwayOSD, hyprlock, hypridle, swaybg and polkit-gnome were removed from the default composition. The bar, launcher, menus, notifications, OSDs, panels, lock screen and polkit agent moved into a common shell and plugin model. Quattro’s architectural move: fewer independently composed desktop daemons, more coherent platform surface. Coherence improves programmability but increases the importance of runtime isolation. This is a real architectural simplification. A coherent shell is easier to theme, script, introspect and modify. It also means Omarchy increasingly owns a platform-level trust boundary. Once a shell mediates notifications, authorization prompts, plugins, menus and system interaction, it is not “UI glue.” It is security-sensitive platform code. 03 / Agent-native computing Textual state is AI infrastructure. The most important Omarchy feature is not a widget. It is legibility. User configuration is concentrated in conventional files under ~/.config . Hyprland configuration is Lua. Omarchy shell state is JSON. Hooks are executable files in predictable directories. The omarchy CLI exposes machine operations. Coding-agent launchers for Codex, Claude Code, GitHub Copilot CLI, OpenCode and others are explicitly first-class. That changes the interaction model. A traditional GUI forces automation through bespoke APIs or brittle interface manipulation. Omarchy makes a surprising amount of workstation state readable as files and commands. An agent can inspect the current state, infer the desired change, edit configuration, invoke a command and verify the result. Windows and macOS mostly add AI to the operating system. Omarchy is exploring an operating environment designed so AI can operate on the system itself. This distinction is strategically important. Natural language begins to sit above declarative machine state. “Move the bar to the other monitor,” “make this repository’s development environment work,” or “build me a distraction-free writing profile” can become intent that an agent resolves into actual configuration. SharePlane target architecture. Omarchy has much of the legible lower substrate. The missing enterprise-grade layer is capability-scoped authority between agent reasoning and machine mutation. 04 / What Omarchy actually owns Integration is the innovation. Dismissals that list the upstream components miss the same point critics once missed about Rails. A product can be architecturally novel because of the constraints, defaults and interfaces it composes, not because every primitive originated inside the project. Inherited primitive Omarchy differentiation Why it matters Arch + pacman Curated mirror, channels, migrations, package repository Turns rolling Linux into an opinionated lifecycle. Hyprland + Wayland Complete keyboard/workspace grammar and Lua configuration Desktop behavior becomes structured and agent-readable. Quickshell omarchy-shell and plugin architecture Creates a coherent programmable desktop surface. Btrfs + Limine Automatic update snapshots and restore workflow Provides practical failure recovery without inventing a new filesystem. AI CLIs Pre-wired lazy launchers and OS workflows Moves agents from optional apps toward platform actors. KVM / Docker / RDP Productized Windows fallback Accepts that compatibility sometimes means running Windows rather than pretending it disappeared. The result is best described as a curated, mutable workstation platform , not merely an Arch install script. 05 / Windows reality Omarchy does not make Windows disappear. The Linux compatibility renaissance is real, but Omarchy does not make Win32 applications “native.” Games benefit from the broader Wine/Proton/Vulkan ecosystem. Native Linux and web applications are preferred where they fit. For software that genuinely requires Windows fidelity, Omarchy offers a Windows 11 VM using KVM and a Docker-managed environment surfaced through RDP. That is the right kind of pragmatism. The VM shares sound, microphone, clipboard and a bounded ~/Windows directory, and its network ports are localhost-bound. Omarchy also documents the limitation clearly: the default setup has no GPU passthrough and is therefore inappropriate for high-performance Windows gaming or video editing. Native Linux / terminal / web app → use directly Windows game with good compatibility → Proton / GE-Proton ecosystem Windows business application needing fidelity → KVM Windows VM GPU-heavy Windows-only workload → still a gap in the default architecture The strategic point is not that every Windows application now runs on Linux. It is that the workstation can choose the lowest-friction execution substrate per workload. 06 / Lifecycle This is not raw bleeding-edge Arch. Omarchy’s stable channel uses its own Arch mirror that normally trails upstream by roughly one month. The intent is straightforward: allow incompatibilities to surface before they reach ordinary stable installations, while selectively advancing important fixes. Omarchy itself ships as pacman packages and runs migrations during updates. Every Omarchy update also creates a Btrfs snapshot. Through Limine, users can boot and restore an earlier root filesystem. The limitation matters: /home , including ~/.config , is not rolled back. That protects personal data but can produce a restored operating system paired with newer user configuration. Snapshots are recovery. They are not full deterministic reconstruction. For enthusiast and developer systems, this is a strong compromise. For governed fleets, it needs more: defined security-patch SLAs, a formal advisory process, configuration provenance, drift detection, reproducible or attested builds, and machine-readable update evidence. 07 / Security wake-up The product vision is ahead of the security model. Eleven days after Quattro, Omarchy 4.0.1 shipped as a security-heavy fast-follow. Its release notes include fixes for agent bypass behavior, a video-title command-injection path, installed-theme code execution, predictable temporary authentication material, notification action execution, Docker-group privilege, Git transport handling and other trust-boundary problems. An independent security critique published at the same time was severe, arguing that several bugs reflected predictable unsafe handling of untrusted input rather than obscure edge conditions. The rhetoric is deliberately sharp. The important analytical point is that Omarchy’s own release notes corroborate multiple vulnerability classes at issue. Security issues were found quickly Positive signal The project created a security team and disclosure channel Positive signal Several bugs crossed command-execution / privilege boundaries Serious Quattro expanded the shell’s responsibility at the same time Raises blast radius Fast remediation proves mature security architecture No Both interpretations can be true: the response speed is encouraging, and the bug classes are evidence that the trust architecture is still young. 08 / Platform trust Secure Boot and TPM are the clearest enterprise stop sign. The current Omarchy installation guide instructs users to disable Secure Boot and/or TPM and characterizes them as Microsoft security schemes. That characterization is incorrect. Secure Boot is part of the UEFI platform standard; TPM is standardized by the Trusted Computing Group. This is not a pedantic terminology complaint. On managed endpoints, Secure Boot and TPM support measurable trust properties: boot-chain verification, measured boot, device-bound credentials, key protection and device-health signals used by modern conditional-access and zero-trust systems. For a personal workstation, disabling Secure Boot may be a choice. For a high-assurance fleet, it is an architectural disqualifier until an equivalent supported trust path exists. Omarchy does offer LUKS disk encryption and hardware-authentication options. Those are useful controls. They do not substitute for a complete measured and attested platform-boot architecture. 09 / Plugin boundary The plugin model is brilliant and dangerous for the same reason. Quattro’s shell plugins are simple to create and distribute. A third-party plugin can be cloned from Git, validated and enabled without modifying Omarchy’s core source. The manual explicitly warns that third-party plugins run as arbitrary, unsandboxed code inside the long-lived shell process with the user’s permissions. This is exactly the tradeoff that makes agent-assisted personalization explode. It is also a familiar platform trap: extensions quietly become applications before the permission model evolves to treat them as applications. A mature endpoint architecture needs a manifest of requested capabilities, brokered access to privileged operations, runtime isolation, update provenance, policy decisions and auditable receipts. “Read the source before enabling it” is useful advice for enthusiasts. It is not a fleet-control model. 10 / Enterprise fit Pilot aggressively. Trust conservatively. Omarchy is already a strong candidate for AI development workstations, personal power-user desktops, homelabs and disposable development VMs. The farther the workload moves toward privileged administration, regulated computing or high assurance, the more the unresolved authority model dominates the decision. Current SharePlane deployment judgment, 30 August 2026. This is an architectural readiness assessment, not a quality score for Omarchy as a personal desktop. 37signals’ announced three-year migration of Ops and Ruby programming teams is meaningful dogfooding. It proves a sophisticated software company is willing to depend on the environment. It does not establish regulated-industry readiness, formal endpoint-support lifecycles, EDR certification, GxP suitability or enterprise validation evidence. 11 / What must come next Authority has to become a first-class subsystem. Omarchy’s biggest opportunity is to preserve its malleability while refusing to equate “agent can technically do it” with “agent is authorized to do it.” The future control plane should make every meaningful mutation pass through explicit capability and evidence semantics. 1. Human intent → desired outcome and boundary 2. Agent plan → proposed operations, inputs and expected effects 3. Policy broker → capability, scope, consent, identity and risk decision 4. Transactional executor → snapshot, diff, mutation, verification, rollback 5. Evidence receipt → what changed, why, by whom, from which source state That architecture would turn Omarchy’s current strength into something much larger. Instead of an AI-friendly desktop, it could become a reference design for how agents safely operate personal computers. Minimum enterprise evolution Control plane Required evolution Outcome Platform trust Supported Secure Boot + TPM / measured boot Device identity and boot integrity become attestable. Agent authority Capability-scoped policy broker Models cannot silently inherit ambient user power. Plugins Permission manifest + sandbox + signed provenance Extension ecosystem can scale without scaling trust blindly. Lifecycle Security SLA, advisory feed, SBOM/provenance and enterprise channel Fleet change becomes governable and auditable. Recovery Transactional OS + configuration rollback Restore becomes deterministic rather than partially temporal. Fleet control Declarative policy, drift detection and evidence export Endpoint state becomes manageable at scale. 12 / SharePlane lens Malleability is not authority. Authority is not durability. SharePlane synthesis. This section is an architectural interpretation built on the Omarchy analysis above. It is not an Omarchy product claim, affiliation, or endorsement. Omarchy supplies a piece that the agent-computing conversation has largely ignored: an endpoint substrate that software agents can actually understand and reshape. That does not make Omarchy a governance plane, and it does not make the workstation the durable system of record. The cleaner architecture separates those responsibilities. Omarchy is the malleable execution environment. GhostMesh is the authority and context plane that decides what an agent may do, under which conditions, against which evidence. SharePlane is the durable Work plane that preserves accepted results, provenance, relationships and projections after execution is complete. SharePlane synthesis, not an Omarchy claim. Three responsibilities that should cooperate without collapsing into one trust boundary: execution, authority and durability. Execution / Omarchy Make the machine adaptable. Legible configuration, CLI surfaces, plugins, snapshots and a coherent desktop give agents something they can inspect and operate. Authority / GhostMesh Decide what may happen. Context, claims, leases, boundaries, recovery, verification and receipts prevent capability from silently becoming authority. Durability / SharePlane Preserve what was accepted. Artifacts, provenance, semantic relationships and versioned projections keep Work durable after the agent session and workstation state have moved on. The cooperation loop Human states the desired outcome. Intent begins the process without pretending natural language is authorization. Agent reasons against current context. Repository, endpoint and prior Work become evidence-bearing inputs. GhostMesh evaluates authority. Capability, scope, identity, policy and recovery conditions are resolved before mutation. Agent acts on the Omarchy endpoint. The workstation supplies the readable and mutable execution substrate. GhostMesh verifies the result. Observed state is reconciled against the authorized outcome and evidence is emitted. SharePlane preserves accepted Work. Artifacts, provenance and semantic relationships survive the execution session. Durable context informs the next intent. The loop compounds knowledge instead of repeatedly rediscovering state. Comparison: different systems optimize different control surfaces Qualitative SharePlane architectural interpretation of typical current deployments. This is not a benchmark, certification, or vendor score. Omarchy 4.0.1 Agent legibility Strong Malleability Very strong Platform trust Current gap Fleet governance Early Windows 11 Agent legibility Partial Malleability Moderate Platform trust Strong Fleet governance Strong macOS Agent legibility Partial Malleability Moderate Platform trust Strong Fleet governance Strong NixOS Agent legibility Strong Declarative state Very strong Transactionality Very strong Turnkey desktop coherence Variable Fedora Atomic desktops Agent legibility Moderate Immutable/atomic base Strong Platform trust Strong Enterprise ecosystem Strong Semantic graph Typed relationships around this Work Linux / Windows compatibility Related evidence thesis Agent-native computing Primary concept Endpoint security Constraint / risk boundary Context as Code Informs execution context Omarchy Agent-Native Workstation Provenance & receipts Required evidence relationship GhostMesh architecture Complementary authority plane Durable Work SharePlane preservation model Declarative systems / NixOS Comparative architecture Omarchy makes the endpoint operable by agents. GhostMesh makes agent action governable. SharePlane makes accepted Work durable. The architecture becomes stronger when those jobs remain separate. Reserved companion thesis Beyond Omarchy: The Governed Agent-Native Workstation The follow-on should design the enterprise-grade endpoint that results when malleable execution, bounded authority and durable Work are treated as distinct cooperating planes. 13 / The future Omarchy may matter even if Omarchy does not win. There are three plausible outcomes. Omarchy could become a durable developer and enthusiast distribution. It could become the leading implementation of an agent-native personal computer. Or its ideas could be absorbed by larger platforms while the project itself remains comparatively small. The recent momentum makes the second and third outcomes more credible than they were a year ago. The Omacom Foundation reports $10 million in funding. It is directly sponsoring Hyprland, Quickshell and mise. Omarchy reported more than 100,000 ISO downloads in a week and more than a thousand plugins in Quattro’s first week. These are project-reported momentum signals, not proof of durable installed base, but they materially change the project’s ability to fund upstream dependencies and survive beyond a hobby cycle. The enduring idea is simple: the operating system should become legible enough for an agent to operate, but governed enough that the agent never becomes accidental root. That is a much bigger thesis than “Linux looks good now.” It is a new endpoint-control problem arriving in plain sight. Evidence rail Omarchy home Project positioning: “malleable OS for the age of agents.” Omarchy 4.0.0 release Quattro: one Quickshell process replaces the prior desktop-daemon constellation. Omarchy 4.0.1 release Security-heavy fast-follow released August 25, 2026. Omarchy AI manual Coding agents are first-class launchers, including Codex, Claude, Copilot CLI and others. Dotfiles manual User-owned state lives under ~/.config, including Hyprland Lua and Omarchy shell configuration. Shell plugins manual Third-party plugins execute as unsandboxed user code inside the long-lived shell. Updates manual Stable channel uses an Omarchy Arch mirror roughly one month behind upstream. System snapshots Every Omarchy update creates a Btrfs snapshot; root can be restored through Limine. Getting started Current install documentation requires Secure Boot and/or TPM to be disabled. Windows VM manual Windows 11 can run through a KVM/Docker VM with RDP integration for fidelity-dependent apps. 100,000 downloads Project-reported ISO downloads exceeded 100,000 in one week; this is not active-install telemetry. Omacom Foundation Foundation funding reached $10 million from ten founding patrons. 37signals adoption 37signals announced a three-year migration plan for Ops and Ruby programming teams. Independent critique A sharply critical security review published after Quattro; claims are weighed against Omarchy’s own 4.0.1 fixes. UEFI Secure Boot Secure Boot is defined by the UEFI standard, not a Microsoft-only security scheme. Trusted Computing Group TPM 2.0 is standardized by the Trusted Computing Group. Research rule: project-reported adoption and funding are labeled as such. Independent security claims are corroborated against first-party release notes where possible. SharePlane publication wrapper Research, graph, evidence, and portable Work. This layer is deliberately separate from the editorial thesis. It makes the publication inspectable: sources are linked to their originating material, semantic relationships are exportable, the cooperation model is explicit, and the full artifact can travel with its evidence instead of becoming another orphaned web page. Primary Work Self-contained HTML The complete publication master with embedded active visuals. Hero master Full-resolution PNG The approved agent-native workstation visual as a standalone asset. Evidence Evidence ledger Claim boundaries, source classes, caveats, and visual provenance. Verification Source index JSON Sixteen public references with claim purpose and source classification. Graph Relationship graph JSON Typed semantic edges connecting this Work to adjacent architecture. Portable package Download everything HTML, visual assets, manifests, source index, graph data, and evidence ledger. Verification index 16 public-source references · links re-opened 30 Aug 2026 · project-reported claims explicitly labeled S01 Omarchy home Project positioning: malleable OS for the age of agents. Verified link S02 Omarchy 4.0.0 / Quattro Unified Quickshell shell replaces the prior desktop-daemon constellation. Verified link S03 Omarchy 4.0.1 Security-heavy fast-follow released 25 Aug 2026. Verified link S04 AI manual Coding agents are first-class launchers and operating tools. Verified link S05 Dotfiles manual User-owned state under ~/.config is readable and editable. Verified link S06 Shell plugins manual Third-party plugins execute as unsandboxed user code in the shell. Verified link S07 Updates manual Stable channel uses an Omarchy-controlled Arch mirror and migrations. Verified link S08 System snapshots Updates create Btrfs snapshots with Limine recovery. Verified link S09 Getting started Current installation guidance disables Secure Boot and/or TPM. Verified link S10 Windows VM manual Windows fallback uses KVM/Docker/RDP integration. Verified link S11 100,000 downloads in a week Project-reported download momentum; not installed-base telemetry. Verified link S12 Omacom Foundation funding $10M foundation funding is project-reported. Verified link S13 37signals adoption Three-year internal migration plan from the project creator and 37signals. Verified link S14 Independent security critique Dissenting security analysis; vulnerability classes cross-checked against 4.0.1. Verified link S15 UEFI 2.11 Boot Manager Standards reference for Secure Boot architecture. Verified link S16 TPM 2.0 Library Standards reference for TPM 2.0. Verified link Verification means the cited destination was reachable and matched the represented source at the publication-prep snapshot. It is not a guarantee that an external page will remain unchanged. Cooperation and semantic relations Execution, authority, and durability remain separate trust responsibilities Omarchy Execution substrate GhostMesh Authority & context SharePlane Durable Work SP-SPECIAL-OMARCHY-2026-08-30 → Agent-native computing PRIMARY_CONCEPT SP-SPECIAL-OMARCHY-2026-08-30 → Linux / Windows compatibility RELATED_EVIDENCE SP-SPECIAL-OMARCHY-2026-08-30 → Endpoint security CONSTRAINED_BY SP-SPECIAL-OMARCHY-2026-08-30 → Context as Code INFORMED_BY SP-SPECIAL-OMARCHY-2026-08-30 → Provenance & receipts REQUIRES SP-SPECIAL-OMARCHY-2026-08-30 → GhostMesh architecture COMPLEMENTS SP-SPECIAL-OMARCHY-2026-08-30 → Durable Work PRESERVED_AS SP-SPECIAL-OMARCHY-2026-08-30 → Declarative systems / NixOS COMPARED_WITH SharePlane verdict Significant. Omarchy is not enterprise-ready because it is already enterprise software. It is not. It is significant because it exposes what the next enterprise workstation will eventually have to solve: agent-readable state, transactional change, capability-scoped authority and evidence of every consequential mutation. SharePlane Special / 30 August 2026 Evidence behind the thesis Check the work, not just the conclusion. Public research, authority, lineage, and author testimony are labeled separately. Sources can corroborate, challenge, or bound the argument; they do not replace Tony Malott's judgment. Portable public record Take the complete artifact with you. The deterministic package contains a self-contained offline article, the exact public-route snapshot, canonical public metadata, receipt, source text when available, plain-text context, claim ledger, source records, and a member-hash manifest. Download full artifact package Read plain-text context Inspect package manifest 17 public sources Sources, authority, and lineage Each record states the role it plays. Research support and governance provenance are not treated as interchangeable. First Party Documentation Omarchy home Project positioning: malleable OS for the age of agents. Project positioning: malleable OS for the age of agents. Open source First Party Documentation Omarchy 4.0.0 / Quattro Unified Quickshell shell replaces the prior desktop-daemon constellation. Unified Quickshell shell replaces the prior desktop-daemon constellation. Open source First Party Documentation Omarchy 4.0.1 Security-heavy fast-follow released 25 Aug 2026. Security-heavy fast-follow released 25 Aug 2026. Open source First Party Documentation AI manual Coding agents are first-class launchers and operating tools. Coding agents are first-class launchers and operating tools. Open source First Party Documentation Dotfiles manual User-owned state under ~/.config is readable and editable. User-owned state under ~/.config is readable and editable. Open source First Party Documentation Shell plugins manual Third-party plugins execute as unsandboxed user code in the shell. Third-party plugins execute as unsandboxed user code in the shell. Open source First Party Documentation Updates manual Stable channel uses an Omarchy-controlled Arch mirror and migrations. Stable channel uses an Omarchy-controlled Arch mirror and migrations. Open source First Party Documentation System snapshots Updates create Btrfs snapshots with Limine recovery. Updates create Btrfs snapshots with Limine recovery. Open source First Party Documentation Getting started Current installation guidance disables Secure Boot and/or TPM. Current installation guidance disables Secure Boot and/or TPM. Open source First Party Documentation Windows VM manual Windows fallback uses KVM/Docker/RDP integration. Windows fallback uses KVM/Docker/RDP integration. Open source First Party Project Reported 100,000 downloads in a week Project-reported download momentum; not installed-base telemetry. Project-reported download momentum; not installed-base telemetry. Open source First Party Project Reported Omacom Foundation funding $10M foundation funding is project-reported. $10M foundation funding is project-reported. Open source Creator Company Statement 37signals adoption Three-year internal migration plan from the project creator and 37signals. Three-year internal migration plan from the project creator and 37signals. Open source Independent Dissenting Analysis Independent security critique Dissenting security analysis; vulnerability classes cross-checked against 4.0.1. Dissenting security analysis; vulnerability classes cross-checked against 4.0.1. Open source Standards Body UEFI 2.11 Boot Manager Standards reference for Secure Boot architecture. Automated re-open returned HTTP 403 on 2026-08-31 without contradicting the accepted reference. Standards reference for Secure Boot architecture. Automated re-open returned HTTP 403 on 2026-08-31 without contradicting the accepted reference. Open source Standards Body TPM 2.0 Library Standards reference for TPM 2.0. Standards reference for TPM 2.0. Open source Owner Semantic And Implementation Authority Issue #687 owner authority Owner Creative Lock, source identity, publication scope, and bounded candidate authority; not independent corroboration. Owner Creative Lock, source identity, publication scope, and bounded candidate authority; not independent corroboration. Open source Claim discipline What is asserted—and how it is bounded Research, author analysis, and personal testimony remain distinct. Supporting links and caveats stay attached to each claim. Claim claim:687:agent-legibility Support Omarchy home AI manual Dotfiles manual Omarchy 4.0.0 / Quattro Claim claim:687:authority-gap Support Shell plugins manual Omarchy 4.0.1 Independent security critique Issue #687 owner authority Claim claim:687:platform-trust Support Getting started UEFI 2.11 Boot Manager TPM 2.0 Library Claim claim:687:momentum Support 100,000 downloads in a week Omacom Foundation funding 37signals adoption Claim claim:687:three-layer-synthesis Support Issue #687 owner authority Public boundary. Public-source technical analysis. Project-reported adoption and funding remain labeled as such; comparison judgments and the Omarchy / GhostMesh / SharePlane cooperation model are SharePlane synthesis, not Omarchy claims or measured benchmarks. 17 sources 5 governed claims 1 portable package SOURCE REFERENCES Omarchy home https://omarchy.org/ Omarchy 4.0.0 / Quattro https://github.com/omacom/omarchy/releases/tag/v4.0.0 Omarchy 4.0.1 https://github.com/omacom/omarchy/releases/tag/v4.0.1 AI manual https://omarchy.org/manual/ai/ Dotfiles manual https://omarchy.org/manual/dotfiles/ Shell plugins manual https://omarchy.org/manual/shell-plugins/ Updates manual https://omarchy.org/manual/updates/ System snapshots https://omarchy.org/manual/system-snapshots/ Getting started https://omarchy.org/manual/getting-started/ Windows VM manual https://omarchy.org/manual/windows-vm/ 100,000 downloads in a week https://omarchy.org/news/2026/08/100000-downloads-in-a-week/ Omacom Foundation funding https://omarchy.org/news/2026/08/omacom-foundation-funding-hits-10m/ 37signals adoption https://world.hey.com/dhh/all-in-on-omarchy-at-37signals-68162450 Independent security critique https://blog.happyfellow.dev/merchants-of-insecurity/ UEFI 2.11 Boot Manager https://uefi.org/specs/UEFI/2.11/03_Boot_Manager.html TPM 2.0 Library https://trustedcomputinggroup.org/resource/tpm-library-specification/ Issue #687 owner authority https://github.com/pinklon/shareplane-platform/issues/687