THE NATIVE RECORD

VERIFIED.

Not promises. Not concept art. The bounded pieces of Mira OS that have actually passed native acceptance on real BesideHQ hardware.

Mira OS is unusual enough that words are cheap. This page exists to separate the destination from what has actually been proven today.

WHAT VERIFIED MEANS

Verified does not mean the entire operating system is finished. It means a specific bounded native slice met its acceptance conditions on the real machine without Windows or Linux supplying that slice underneath it.

Scope matters. A verified firmware startup is not the same thing as a connected network. A verified storage primitive is not the same thing as a finished general filesystem. We keep those boundaries explicit.

CURRENT FRONTIER · NATIVE NETWORKING

Intel AX211 hardware access, startup, and firmware ALIVE are physically verified on BesideHQ.

The active edge is exact SKU and PNVM handling, native firmware command transport, scanning, router association and authentication, then IP, DHCP, DNS, sockets, TLS, and native Brain/provider transport.

Firmware is running and replying, but Mira OS is not yet connected to Wi-Fi. No router connection, IP address, or provider transport is claimed yet.

MOSC_NATIVE_VERIFIED

Kernel + Execution

Secure Boot native entry
BSP heartbeat and native timing
27 application processors online
Per-CPU descriptor and interrupt state
Cooperative scheduler work
Ready-work redistribution
Timer-driven preemption
Ring-3 userspace
Native syscall return
Capability-checked IPC
Native service processes

MOSC_NATIVE_VERIFIED

Storage + State

NVMe read path
Native durable writes
Flush, readback, and reboot restore
Named Home state files
Atomic state replacement
Conversation-store fixtures
Append storage and recovery
Process-owned file access
Process durable state writes
Reusable state pages

MOSC_NATIVE_VERIFIED

Networking

AX211 PCI/MMIO hardware access
AX211 native startup
AX211 firmware ALIVE and bounded DMA stop