FAQ: Architecture, Availability & Philosophy

xHunOS (玄魂) is an independent, roughly 25MB bare-metal operating system for contemplation and metaphysical computation. It runs at processor Ring 0 with a single identity-mapped address space, a fixed-width 16-bit (BMP) Chinese lexer, the DaoFS filesystem and the xLang/ZAsm toolchain.

Yes. It is a research OS with a kernel, filesystem, compiler, window manager and application suite. The kernel is in active development at v0.2; the standalone image is not publicly released yet.

It continues TempleOS's architectural lineage: Ring-0 execution, no paging, no network stack and a shell-native compiler. It is not an official TempleOS distribution; the language, character set, filesystem and cosmological model are new.

Systems programmers, digital minimalists, contemplative practitioners and anyone who wants a small, legible, offline machine rather than another general-purpose computer.

Because isolation is not a goal of the design. With one owner, no network and no untrusted processes, the kernel can give every task full access and spend its complexity budget on determinism instead of protection boundaries.

xHunOS keeps paging enabled, because 64-bit long mode requires it, but maps all physical RAM 1:1 with 1 GiB pages in a single PML4. Every page is present and writable, so the kernel has no page-fault path, no swap and no copy-on-write. What is removed is the work paging normally does, not the paging hardware itself.

The kernel has no TCP/IP stack. There is no browser, no cloud sync and no telemetry channel. Any data movement is deliberate and local rather than a background service.

DaoFS is the xHunOS filesystem. Files occupy contiguous 2048-byte sectors with no inode tree and no seek penalty, matching the geometry of raw SPI flash.

DolDoc is a hypertext document format where text, code, links and interactive elements share one file. Documentation can execute examples and link straight to kernel source.

There is no benchmark, so no multiplier is claimed. What can be derived from published figures: a 25.1 MB image against a 4–20 GB install (≈160–820× smaller) and a 0.1 s boot target against 15–45 s (≈150–450× shorter). Those compare a target with a typical system, not the same workload on the same hardware. Power has not been measured, and the design has no idle governor, so no power saving is claimed either.

xLang is the system language: a HolyC descendant with Chinese keywords and fixed-width 16-bit (BMP) tokenization. Source is compiled in memory to x86-64 machine code in under a millisecond.

ZAsm is the 64-bit assembly layer. It aliases general-purpose registers to the Heavenly Stems and condition flags to the Eight Trigrams.

No. There is no ELF/PE loader and no Linux ABI. Applications are written in xLang and compiled by the system itself.

Not yet. The kernel is at v0.2 and no public ISO has been released. The download page tracks what the first public build will contain.

The target is x86-64 bare metal with a 640×480 framebuffer and raw SPI flash storage. The Tianming Box is the first planned deployment.

The Tianming Box (天命盒), also branded as the YuanYu Destiny Box, is a wooden, air-gapped portable device designed to run xHunOS for hardware-entropy divination.

Release status and architecture notes are published on this site. The whitepaper and the xLang specification are the authoritative technical references.

Physical access, removable media and bugs. The air gap removes remote attack surface, but everything runs in Ring 0, so a parsing bug in a filesystem or image loader is a total compromise. The air gap is an architectural property, not a security guarantee.

Not yet. Encryption at rest is a v0.2 release requirement, not a shipped feature. Today, anyone who removes the flash chip can read the files. Until encryption lands, treat the device as private but not confidential.

It is not guaranteed safe yet. DaoFS compacts on free, which rewrites live extents, so an interrupted compaction can leave a volume inconsistent. Atomic commit and a repair path are release requirements; until they are tested against injected power loss, keep backups and shut down cleanly.

Export is a release requirement. The planned path writes every user file to removable media in a documented plain format, so leaving the system does not require another xHunOS machine. It is not implemented yet.

Only by verifying a signature. Signed releases and an offline verifier are requirements for v0.2. There is no public image today, and any build offered outside the official channel should be treated as untrusted.

Yes. There is no privilege boundary to contain a fault, so any kernel bug can take down or take over the machine. That is an accepted trade for determinism in a single-owner, offline system; it is not a claim that the system is more secure.