Component explorer
Trace responsibilities across the system
Component entries connect high-level concepts to the files and phases that shape them, using the generated m3OS phase corpus now published in this site.
Introduced in
Boot FoundationBoot Path
The boot path moves the system from firmware and build tooling into a running kernel with visible early diagnostics.
Introduced in
InterruptsInterrupt Router
The interrupt router connects CPU exceptions and hardware IRQs to the kernel handlers that keep the system responsive.
Introduced in
IPC CoreIPC Engine
The IPC engine is the microkernel core: it turns isolated tasks into cooperating services through message passing.
Introduced in
Memory BasicsMemory Manager
The memory manager owns frame allocation, virtual mappings, and the policies that let later phases isolate work safely.
Introduced in
NetworkNetwork Stack
The network stack grows the OS from a local system into one that can talk to other machines and higher-level services.
Introduced in
Userspace EntryProcess Model
The process model defines what a userspace program is in m3OS and how execution moves into and between processes.
Introduced in
TaskingScheduler
The scheduler decides which runnable work executes next and turns a single control flow into a real operating system.
Introduced in
Userspace EntryTerminal Stack
The terminal stack turns raw console I/O into an interactive environment people can actually use.
Introduced in
Storage And VFSVirtual File System
The virtual filesystem makes multiple storage backends look like one coherent tree to the rest of the OS.