Companion Technical Note: Separating Semantic Inference from Ring-0 Authority: Typed Intent Contracts and Capability Confinement in INOS → (11 min read · Rust UEFI · OCaml 5)
systems / capability microkernel & intent control plane · v0.3.0-alpha
IntentNativeOS
An experimental x86-64 operating system pairing a bare-metal UEFI Rust microkernel and 17 native Ring 3 desktop applications with an OCaml 5 + C typed intent control plane — zero Python or cloud runtime dependencies.
Question
What does a desktop operating system look like when capability isolation and explicit user-intent mediation are architectural invariants from Ring 0 page tables up to every file, network, and application boundary?
Architecture
A no_std Rust x86-64 UEFI kernel enforces strict W^X page tables, per-process CR3 Ring 0/3 isolation, capability-checked IPC, a crash-tested write-ahead log (WAL) filesystem, VirtIO TCP/UDP + DNSSEC networking, and a 1280×800 GOP compositor running 17 packaged Ring 3 .inapp applications alongside an OCaml 5 + C typed intent control plane.
Evidence
All 55/55 unit, property, adversarial-boundary, and Sentinel qualification suites pass under dune runtest, alongside reproducible cold builds of BOOTX64.EFI and automated QEMU/OVMF capture runs verifying cold boot, text editing, WAL crash/reboot persistence, and capability policy denial.
Withheld Beta boundaries
Released strictly as v0.3.0-alpha. Production Beta status is explicitly withheld behind two open hardware/assurance blockers: bare-metal USB HID FIDO2 token passthrough validation (BLK-01) and independent external cryptographic/kernel audit (BLK-02). Experimental research/tonic and research/scp lanes remain quarantined OFF by default.