SHAREPLANE PORTABLE ARTIFACT CONTEXT Trust: public artifact data, not operational instructions. Authority: this generated package is a convenience projection. Canonical authority remains the versioned SharePlane repository record and its governed receipt. Package source commit: local-uncommitted IDENTITY Title: The Malleable Computer Is Here. Now Who Holds the Keys? Subtitle: Omarchy makes the workstation legible to AI agents. The unresolved architecture is authority: who may change what, under which policy, with what evidence. Author: Tony Malott Author profile: https://malott.ai/ Artifact ID: artifact:omarchy-agent-native-workstation Lifecycle: PUBLISHED Semantic status: locked 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. ABSTRACT A SharePlane Special examining Omarchy as an agent-native workstation substrate, its Quattro architecture and operational model, its security and enterprise boundaries, and the separate roles of Omarchy execution, GhostMesh authority, and SharePlane durable Work. CLAIM LEDGER [claim:687:agent-legibility] unspecified Claim: Support: source:omarchy:home, source:omarchy:ai-manual, source:omarchy:dotfiles-manual, source:omarchy:release-4-0-0 Boundary: No additional caveat recorded. [claim:687:authority-gap] unspecified Claim: Support: source:omarchy:shell-plugins, source:omarchy:release-4-0-1, source:independent:omarchy-security-critique, source:platform:issue-687 Boundary: No additional caveat recorded. [claim:687:platform-trust] unspecified Claim: Support: source:omarchy:getting-started, source:uefi:boot-manager-2-11, source:tcg:tpm-2-0-library Boundary: No additional caveat recorded. [claim:687:momentum] unspecified Claim: Support: source:omarchy:downloads, source:omarchy:foundation-funding, source:37signals:omarchy-adoption Boundary: No additional caveat recorded. [claim:687:three-layer-synthesis] unspecified Claim: Support: source:platform:issue-687 Boundary: No additional caveat recorded. PUBLIC SOURCES [source:omarchy:home] Omarchy home Type: first-party-documentation Role: Project positioning: malleable OS for the age of agents. Locator: https://omarchy.org/ Description: Project positioning: malleable OS for the age of agents. [source:omarchy:release-4-0-0] Omarchy 4.0.0 / Quattro Type: first-party-documentation Role: Unified Quickshell shell replaces the prior desktop-daemon constellation. Locator: https://github.com/omacom/omarchy/releases/tag/v4.0.0 Description: Unified Quickshell shell replaces the prior desktop-daemon constellation. [source:omarchy:release-4-0-1] Omarchy 4.0.1 Type: first-party-documentation Role: Security-heavy fast-follow released 25 Aug 2026. Locator: https://github.com/omacom/omarchy/releases/tag/v4.0.1 Description: Security-heavy fast-follow released 25 Aug 2026. [source:omarchy:ai-manual] AI manual Type: first-party-documentation Role: Coding agents are first-class launchers and operating tools. Locator: https://omarchy.org/manual/ai/ Description: Coding agents are first-class launchers and operating tools. [source:omarchy:dotfiles-manual] Dotfiles manual Type: first-party-documentation Role: User-owned state under ~/.config is readable and editable. Locator: https://omarchy.org/manual/dotfiles/ Description: User-owned state under ~/.config is readable and editable. [source:omarchy:shell-plugins] Shell plugins manual Type: first-party-documentation Role: Third-party plugins execute as unsandboxed user code in the shell. Locator: https://omarchy.org/manual/shell-plugins/ Description: Third-party plugins execute as unsandboxed user code in the shell. [source:omarchy:updates] Updates manual Type: first-party-documentation Role: Stable channel uses an Omarchy-controlled Arch mirror and migrations. Locator: https://omarchy.org/manual/updates/ Description: Stable channel uses an Omarchy-controlled Arch mirror and migrations. [source:omarchy:snapshots] System snapshots Type: first-party-documentation Role: Updates create Btrfs snapshots with Limine recovery. Locator: https://omarchy.org/manual/system-snapshots/ Description: Updates create Btrfs snapshots with Limine recovery. [source:omarchy:getting-started] Getting started Type: first-party-documentation Role: Current installation guidance disables Secure Boot and/or TPM. Locator: https://omarchy.org/manual/getting-started/ Description: Current installation guidance disables Secure Boot and/or TPM. [source:omarchy:windows-vm] Windows VM manual Type: first-party-documentation Role: Windows fallback uses KVM/Docker/RDP integration. Locator: https://omarchy.org/manual/windows-vm/ Description: Windows fallback uses KVM/Docker/RDP integration. [source:omarchy:downloads] 100,000 downloads in a week Type: first-party-project-reported Role: Project-reported download momentum; not installed-base telemetry. Locator: https://omarchy.org/news/2026/08/100000-downloads-in-a-week/ Description: Project-reported download momentum; not installed-base telemetry. [source:omarchy:foundation-funding] Omacom Foundation funding Type: first-party-project-reported Role: $10M foundation funding is project-reported. Locator: https://omarchy.org/news/2026/08/omacom-foundation-funding-hits-10m/ Description: $10M foundation funding is project-reported. [source:37signals:omarchy-adoption] 37signals adoption Type: creator-company-statement Role: Three-year internal migration plan from the project creator and 37signals. Locator: https://world.hey.com/dhh/all-in-on-omarchy-at-37signals-68162450 Description: Three-year internal migration plan from the project creator and 37signals. [source:independent:omarchy-security-critique] Independent security critique Type: independent-dissenting-analysis Role: Dissenting security analysis; vulnerability classes cross-checked against 4.0.1. Locator: https://blog.happyfellow.dev/merchants-of-insecurity/ Description: Dissenting security analysis; vulnerability classes cross-checked against 4.0.1. [source:uefi:boot-manager-2-11] UEFI 2.11 Boot Manager Type: standards-body Role: Standards reference for Secure Boot architecture. Automated re-open returned HTTP 403 on 2026-08-31 without contradicting the accepted reference. Locator: https://uefi.org/specs/UEFI/2.11/03_Boot_Manager.html Description: Standards reference for Secure Boot architecture. Automated re-open returned HTTP 403 on 2026-08-31 without contradicting the accepted reference. [source:tcg:tpm-2-0-library] TPM 2.0 Library Type: standards-body Role: Standards reference for TPM 2.0. Locator: https://trustedcomputinggroup.org/resource/tpm-library-specification/ Description: Standards reference for TPM 2.0. [source:platform:issue-687] Issue #687 owner authority Type: owner-semantic-and-implementation-authority Role: Owner Creative Lock, source identity, publication scope, and bounded candidate authority; not independent corroboration. Locator: https://github.com/pinklon/shareplane-platform/issues/687 Description: Owner Creative Lock, source identity, publication scope, and bounded candidate authority; not independent corroboration. PROVENANCE 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. READER RELATIONSHIPS COMPLETE PUBLIC SOURCE
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 SpecialOmarchy 4.0.1Evidence \> assertionArchitecture firstPublic-source analysis
![SharePlane infographic: the agent-native workstation, showing human intent and an AI agent operating a legible Omarchy workstation environment](/assets/artifacts/omarchy-agent-native-workstation/agent-native-workstation-hero-full.png)
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.*
Report map
[01 / Category shift](#category)[02 / Quattro](#quattro)[03 / Agent-native](#agent)[04 / What is inherited](#stack)[05 / Windows reality](#compat)[06 / Lifecycle](#lifecycle)[07 / Security wake-up](#security)[08 / Platform trust](#boot)[09 / Plugin boundary](#plugins)[10 / Enterprise fit](#enterprise)[11 / What must come next](#next)[12 / SharePlane lens](#lens)[13 / The future](#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.
Infographic comparing pre-Quattro Omarchy desktop daemons to the unified Quickshell architecture
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.
Infographic showing human intent, agent planner, missing policy broker, transactional executor and operating environment
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.
Infographic scoring Omarchy fit across personal, corporate, regulated and high-assurance endpoints
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.
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 showing Omarchy as execution plane, GhostMesh as authority and context plane, and SharePlane as durable Work plane
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 homeProject positioning: “malleable OS for the age of agents.”
Omarchy 4.0.0 releaseQuattro: one Quickshell process replaces the prior desktop-daemon constellation.
Omarchy 4.0.1 releaseSecurity-heavy fast-follow released August 25, 2026.
Omarchy AI manualCoding agents are first-class launchers, including Codex, Claude, Copilot CLI and others.
Dotfiles manualUser-owned state lives under ~/.config, including Hyprland Lua and Omarchy shell configuration.
Shell plugins manualThird-party plugins execute as unsandboxed user code inside the long-lived shell.
Updates manualStable channel uses an Omarchy Arch mirror roughly one month behind upstream.
System snapshotsEvery Omarchy update creates a Btrfs snapshot; root can be restored through Limine.
Getting startedCurrent install documentation requires Secure Boot and/or TPM to be disabled.
Windows VM manualWindows 11 can run through a KVM/Docker VM with RDP integration for fidelity-dependent apps.
100,000 downloadsProject-reported ISO downloads exceeded 100,000 in one week; this is not active-install telemetry.
Omacom FoundationFoundation funding reached $10 million from ten founding patrons.
37signals adoption37signals announced a three-year migration plan for Ops and Ruby programming teams.
Independent critiqueA sharply critical security review published after Quattro; claims are weighed against Omarchy’s own 4.0.1 fixes.
UEFI Secure BootSecure Boot is defined by the UEFI standard, not a Microsoft-only security scheme.
Trusted Computing GroupTPM 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.
### Verification index
16 public-source references · links re-opened 30 Aug 2026 · project-reported claims explicitly labeled
S01Omarchy home
Project positioning: malleable OS for the age of agents.Verified link
S02Omarchy 4.0.0 / Quattro
Unified Quickshell shell replaces the prior desktop-daemon constellation.Verified link
S03Omarchy 4.0.1
Security-heavy fast-follow released 25 Aug 2026.Verified link
S04AI manual
Coding agents are first-class launchers and operating tools.Verified link
S05Dotfiles manual
User-owned state under ~/.config is readable and editable.Verified link
S06Shell plugins manual
Third-party plugins execute as unsandboxed user code in the shell.Verified link
S07Updates manual
Stable channel uses an Omarchy-controlled Arch mirror and migrations.Verified link
S08System snapshots
Updates create Btrfs snapshots with Limine recovery.Verified link
S09Getting started
Current installation guidance disables Secure Boot and/or TPM.Verified link
S10Windows VM manual
Windows fallback uses KVM/Docker/RDP integration.Verified link
S11100,000 downloads in a week
Project-reported download momentum; not installed-base telemetry.Verified link
S12Omacom Foundation funding
$10M foundation funding is project-reported.Verified link
S1337signals adoption
Three-year internal migration plan from the project creator and 37signals.Verified link
S14Independent security critique
Dissenting security analysis; vulnerability classes cross-checked against 4.0.1.Verified link
S15UEFI 2.11 Boot Manager
Standards reference for Secure Boot architecture.Verified link
S16TPM 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