Skip to content

About

Experimental operating system for people and software agents, with a native workspace and bounded execution research.

Resources

Contributing

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

18 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Anomalous

Anomalous is an experimental operating system for people and software agents. It currently combines a Rust kernel, its own x86-64 boot loader, capability-oriented execution research, and an accessible desktop whose human and machine views share explicit state and policy.

Status: pre-alpha research. This is a source release for contributors and researchers. It is not a production operating system, an installable daily-use desktop, or a security boundary for sensitive workloads.

What is implemented

  • Threshold boots a BIOS disk image into a separate Rust x86-64 kernel.
  • Bounded proofs exercise physical-memory ownership, page-table construction, ring-3 execution, interrupt delivery, preemption, fault containment, and supervised replacement.
  • A development workspace provides software-composited windows, mouse and keyboard interaction, two workspaces, Light/Dark themes, an Appearance panel, and a Graphics Lab. These are built-in demonstrations in one workspace vessel, not general application processes.
  • Native application, document, editor, and runtime fixtures explore bounded loading, service ownership, persistence, and workspace integration.
  • Linux ELF planning and interpreter/service-boundary proofs exercise an unchanged Linux interpreter with constrained userspace policy. They do not yet run general Linux applications or Electron.
  • Host-side libraries explore typed session routing, shared semantic scenes, presentation acknowledgement, and recovery.
  • Eidolon supplies an independent Python reference codec for lossless framebuffer traces and an optional experimental Ny implementation.
  • Oculus (Matrix desktop) and Archon (Matrix security tooling) are early language/runtime scaffolds, not replacements for the existing Rust proofs.

General application support, a production filesystem, authentication, networking, package management, and broad foreign compatibility remain research goals. Ny is the official language direction; verified Rust and assembly remain authoritative until separately qualified replacements meet the migration gates. The current-state notebook and execution-readiness gates distinguish implemented mechanisms from proposals. Dated test results describe the recorded checkpoint; they are not a claim that this public export was rebuilt on every supported host.

Build and boot

The current bring-up host is x86-64 Linux. Install rustup, GNU Make, Bash, GNU binutils, and QEMU (qemu-system-x86_64). The pinned Rust toolchain and required components are listed in rust-toolchain.toml. VirtualBox 7 is an optional interactive route.

git clone https://github.com/exec-software/exec-anomalous.git
cd exec-anomalous
make image
make smoke
make workspace-run

make image creates build/anomalous.img; make smoke runs a bounded headless boot check. make workspace-run builds a separate development image and opens QEMU. It uses KVM when available and falls back to software emulation; set ANOMALOUS_QEMU_ACCEL=tcg to select software emulation explicitly. Close QEMU to stop the guest. Do not write development images to a physical disk.

The basic Rust boot path does not import the optional Ny SDK or an AI model. Language experiments and external-binary proofs need separately provisioned inputs; see optional runtime requirements. Build outputs under build/ and target/ are ignored. For a shared workspace, use a disposable checkout and keep generated artifacts outside the source tree you intend to publish.

See the development guide for the complete target matrix, desktop controls, VM workflow, and checkpoint history. Hardware-facing changes need the relevant native proof in addition to unit tests. Full validation with make check also constructs strict Linux-loader fixtures and requires the exact separately provisioned system binaries recorded by those runners. It is not a prerequisite for trying the basic boot image on an arbitrary Linux host. The full foundations workflow is manual until its qualified host fixtures are provisioned. Automatic CI runs the source-security audit and portable tooling checks; these do not claim guest boot, full-matrix, or SDK qualification.

Architecture and documentation

Topic Start here
Design direction Vision, architecture overview
Kernel and execution Kernel, execution readiness
Security boundaries Threat model, security policy
Accepted and proposed decisions Architecture decisions
Technical research and measurements Notebook guide, notebook index
Terms Nomenclature
Language experiments Optional runtime, Eidolon, Oculus, Archon

Project terms have defined technical meanings: a vessel is an isolated service or execution owner, a sigil represents scoped authority, and a rite is a typed operation. Planned Reliquary artifacts, Covenant package transactions, and general compatibility veils remain under design; the bounded loader and userspace-policy fixtures do not establish broad compatibility. Human and agent clients must respect the same authorization boundary.

Contributing

Read CONTRIBUTING.md and AGENTS.md. Preserve narrow unsafe and assembly boundaries, document invariants, and include evidence for hardware or security claims. Report vulnerabilities privately using SECURITY.md.

Created by Nathan Young. Execute Software and community contributors are recognized in CONTRIBUTORS.md; AUTHORS.md records project attribution.

The repository uses Execute rolling versions (v1, v2, and so on) in VERSION. Cargo component versions describe API compatibility and are independent of the repository release number.

Support and enterprise inquiries

Support development through Ko-fi. For enterprise licensing and support, contact admin@executesoftware.com.

Enterprise agreements may cover support, certification, warranties, indemnity, managed distribution, and lifecycle commitments. Availability and terms require an explicit agreement; donations do not purchase those services or change the open-source license.

License

Anomalous is available under the MIT License, copyright 2026 Nathan Young. Separate enterprise agreements do not reduce the rights granted by MIT.

About

Experimental operating system for people and software agents, with a native workspace and bounded execution research.

Resources

Contributing

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages