The TempleOS Successor, Reforged for the East
xHunOS is an independent 25MB bare-metal operating system that inherits TempleOS's Ring-0, single-address-space design and extends it with native Chinese ideographs, DaoFS contiguous storage and the xLang compiler.
TempleOS is one of the most unusual operating systems ever written: a single-address-space, Ring-0 system built by one person, with no networking, no paging and a compiler that lives inside the shell. When Terry A. Davis died in 2018, the question became whether that architectural lineage would end with him.
xHunOS is an answer to that question from the East. It keeps the parts that made TempleOS coherent — flat memory, deterministic timing, air-gapped operation and source-as-system — and replaces the language, character model, filesystem and cosmological layer with a native Chinese design. This page explains exactly what is inherited, what is changed, and how to evaluate the claim.
What xHunOS Preserves From TempleOS
Ring-0, single address space
There is no user/kernel split. Every task, driver and application runs at the highest privilege level, and all physical memory is identity-mapped 1:1. No page tables, no page faults, no TLB thrashing.
The shell is the compiler
Source code is not built into binary artifacts. Each line typed into the terminal is compiled in memory into native x86-64 machine code and executed immediately.
Air-gapped by design
The kernel carries no TCP/IP stack. xHunOS cannot phone home, download updates or run telemetry daemons, because the architecture has nowhere to put them.
DolDoc hypertext
Text, code, links and interactive elements live in one document format. A help page can execute its own examples and jump directly to kernel source.
Deliberate graphical simplicity
A fixed 640×480 framebuffer keeps the entire display path readable. There is no compositor stack, no GPU driver bureaucracy and no animation framework between the programmer and the pixels.
One-person intelligibility
The whole system stays small enough to read: roughly 25MB for the kernel, GUI and tools, rather than tens of millions of lines.
What xHunOS Changes
A native 16-bit corpus
xLang and the system lexer treat UCS-2 code units as first-class tokens, so Chinese ideographs align to 2-byte machine words instead of variable-length UTF-8 slices.
xLang instead of HolyC
xLang keeps the HolyC idea of an instant, shell-native compiler but rebuilds the grammar and keyword set around Chinese tokens such as 常数, 变量 and 函数.
DaoFS instead of RedSeaFS
Files occupy contiguous 2048-byte sectors with no inode tree and no seek penalty. Storage geometry is designed for raw SPI flash rather than rotating media.
TaiChu instead of Adam
The immortal root task remains pinned to Core 0, hosting the global symbol table, font tables, window manager and entropy pollers for every child task.
ZAsm and sovereign registers
The assembly layer aliases general-purpose registers to the Heavenly Stems and condition flags to the Eight Trigrams, giving low-level code a mnemonic system rooted in the I Ching.
An Eastern cosmological model
Where TempleOS encoded one religious vision, xHunOS encodes another: yarrow-stalk entropy, BaZi ephemeris, pentatonic synthesis and Daoist breath pacing are part of the native toolchain.
TempleOS vs xHunOS at a Glance
| Dimension | TempleOS | xHunOS |
|---|---|---|
| Kernel model | Ring 0, single address space | Ring 0, single address space |
| Memory | Identity-mapped, no paging | Identity-mapped, no paging |
| System language | HolyC | xLang (HolyC descendant) |
| Character model | 8-bit extended ASCII | 16-bit UCS-2 ideographs |
| Filesystem | RedSeaFS | DaoFS (contiguous 2048-byte sectors) |
| Root task | Adam | TaiChu (太初) |
| Assembly layer | Standard x86-64 mnemonics | ZAsm + TianGan / BaGua aliases |
| Networking | None | No TCP/IP stack in kernel |
| Distribution | Public ISO | Coming soon (kernel v0.2 in progress) |
| Codebase | Roughly 100,000 lines | Roughly 25MB system image |
TempleOS Successor — Common Questions
Is xHunOS a TempleOS fork?+
xHunOS is best described as an architectural successor rather than a fork. It re-implements the same design ideas — flat Ring-0 memory, a shell-native compiler, no networking — with a new language, filesystem and character model.
Why call it a successor if the code is different?+
Operating-system succession is about constraints and ideas, not a copied source tree. TempleOS's defining constraints are preserved: one owner, one address space, no paging and no network. If a successor had to mean the same files, the lineage would have ended in 2018.
Can I run HolyC or Linux programs on xHunOS?+
No. xHunOS does not execute ELF/PE binaries or provide a Linux ABI. Programs are written in xLang and compiled in memory, so porting means re-implementing the program against the xHunOS memory and DolDoc model.
Is xHunOS available today?+
The kernel is in active development at v0.2. There is no public ISO yet; the download page tracks release status. The Tianming Box is the first planned deployment.
Read the architecture, not the marketing
The whitepaper documents the Ring-0 memory model, DaoFS geometry and the yarrow entropy proof. The xLang page documents the language that replaces HolyC.