An operating system in which every piece of hardware is a capability that can be granted, revoked, delegated and audited — with a record of every change of state. Built on a formally verified microkernel, and designed from the outset to be operated safely by software rather than retrofitted for it.
SynthOS is an active research and development programme, not a product available for purchase. A provisional patent application covering the architecture was filed in March 2026. This page describes design intent and the problem being addressed. It is published for the benefit of prospective partners and collaborators, and no part of it should be read as a representation of shipping capability.
A modern server is not a single processor with attached memory. It is dozens of computing elements — cores, accelerators, network controllers, management processors — each with its own view of the machine. Conventional operating systems still present the fiction of one shared pool of memory that everything cooperates over, and then spend enormous effort defending that fiction with locks, mitigations and patches.
“Many small little processes working together on a big problem can make massive progress when smartly organized and orchestrated, and I think the future of operating systems will reflect this.”
— Jonathan Colby, design notes, March 2026
The second premise is about who is driving. Increasingly, the entity operating a system is not a person at a terminal but software acting on their behalf. Every operating system in service today was designed on the assumption that the operator is human, trusted, and accountable. None of them can express the sentence “this component may never touch that piece of hardware, and here is the proof that it did not.”
In SynthOS, access to a hardware resource is not a policy setting that a privileged process can consult and override. It is an unforgeable token. A process that does not hold the token cannot reach the device — not because it is denied at a check, but because it has nothing to reach with. Exclusion is a property of what a process possesses, rather than of a rule someone remembered to write.
| Design principle | What it means in practice |
|---|---|
| Verified foundation | Built on the seL4 microkernel, which carries mathematical proof that it correctly enforces the capability boundaries it is configured with. |
| Exclusion by non-possession | Sensitive hardware is placed beyond reach of automated components by withholding the capability, rather than by a policy that could be misconfigured or bypassed. |
| Auditable state change | Grants, delegations and revocations are recorded to a transparency log, so the question “what had access to this device, and when?” has an answer. |
| Human authority at the top | The most privileged role in the architecture is a person, holding authority that no software component can grant to itself. |
| Message passing for control | Components coordinate by explicit messages rather than shared mutable state, removing an entire category of concurrency and side-channel failure. |
| Synthesized to the machine | Rather than one binary that adapts at runtime to every possible configuration, the system is composed for the specific hardware it finds at boot. See NexusFabric. |
The seL4 microkernel provides a mathematically proven guarantee that the kernel correctly enforces the capability boundaries it is configured with. That guarantee does not extend to the correctness of user-space components, orchestration logic, or any code Enerdyne has written. Enerdyne does not claim that SynthOS as a whole is formally verified.
The intended environments are those where the cost of an undetected compromise is measured in physical consequences rather than data loss: industrial control, energy infrastructure, defence systems, and any deployment where automated software is given authority over equipment and the operator must be able to prove afterwards what that software could and could not touch.
Enerdyne's own Virtual Plant Operator is the first intended workload. That product runs today on conventional hardened server hardware; SynthOS is its future target platform, not a dependency.
A United States provisional patent application covering the architecture — including per-instance hardware topology synthesis, the approval-token protocol, and capability-enforced exclusion of automated components — was filed on 25 March 2026 by Enerdyne LLC, inventor Jonathan West Colby. Related applications cover the encoding and signature methods used within the system. Detailed architecture documentation is available to qualified partners under non-disclosure.
Enerdyne is interested in conversations with organisations working on verified systems, secure hardware, and infrastructure where provable isolation matters.
Contact Enerdyne