Current Build

This page is generated from status/current.json at build time. A status is derived from evidence, not marketing intent — the website cannot display claims the repository does not record.

Current Build

LOCALLY-VERIFIED

VERSION: v0.2.0-dev
MATURITY: pre-alpha
MILESTONE: V0.2 — Userspace Foundation
ARCH: x86_64
ENVIRONMENT: QEMU (BIOS + UEFI/OVMF)
COMMIT: cc29cda
LAST VERIFIED: 2026-09-02T07:35:00Z
TRUTH SOURCE: status/current.json

Fields marked “—” have no verification evidence yet and are reported as absent rather than estimated.

Kernel modules

Kernel modules with their current evidence-backed status
Module	Subsystem	Status
boot	Boot path (BIOS + UEFI via bootloader crate)	VERIFIED
serial	Serial console & structured boot stages	VERIFIED
cpu	CPU identification	VERIFIED
memory-physical	Physical memory manager	VERIFIED
memory-virtual	Virtual memory / paging (kernel + user W^X)	VERIFIED
heap	Kernel heap allocator	VERIFIED
interrupts	GDT/IDT, exceptions, PIC/PIT timer	VERIFIED
scheduler	Kernel tasks & cooperative scheduler	VERIFIED
vfs	VFS & embedded initramfs	VERIFIED
shell	Interactive serial shell (14 commands)	VERIFIED
elf-loader	ELF64 loader (strict validation, W^X)	VERIFIED
ring3	Ring 3 execution & privilege isolation	VERIFIED
syscalls	Syscall ABI (write/exit/yield/getpid)	VERIFIED
process	Process lifecycle & crash containment	VERIFIED
process-isolation	Per-process page tables (concurrent processes)	PLANNED
input-keyboard	PS/2 keyboard input	PLANNED
test-harness	QEMU boot/regression harness	VERIFIED

What the statuses mean

CONCEPT

Documented direction only. No active work; exists to constrain interface design.

PLANNED

Committed for the milestone, not started.

RESEARCH

Under active investigation; outcome may change the plan.

IN DEVELOPMENT

Work ongoing in the current session/phase.

IMPLEMENTED

Code exists and builds, but automated verification has not yet passed.

VERIFIED

An actual QEMU/host test run proved it, with retained evidence (serial log + JSON result).

EXPERIMENTAL

Works in narrow conditions; deliberately outside the release-critical path.

BLOCKED

Cannot proceed without an external input; reason is recorded.

“Implemented” and “Verified” are not interchangeable. Nothing on this site is marked Verified until the harness has produced evidence for it.

How a status becomes Verified

The QEMU harness boots the selftest kernel, which runs in-kernel checks, emits [ITISYOU:TEST] events and a [ITISYOU:SELFTEST] pass=N fail=M summary, then exits QEMU through isa-debug-exit.

The harness requires all expected stages, fail=0, pass>0, and QEMU exit code 33. A hang, panic, or missing summary can never pass.

// evidence retained per run

artifacts/qemu/<label>.serial.log

artifacts/qemu/<label>.result.json

// outcome, exit code, stages seen/missing,

// test events, duration, full command line

Failure classification (tools/qemu-runner)

QEMU harness outcome classification
Outcome	Meaning
success	expected markers + clean exit (selftest: exit 33, fail=0)
selftest-failed	in-kernel test failure (or exit 35)
panic	[ITISYOU:PANIC] observed
timeout	deadline exceeded; QEMU killed; serial tail preserved
missing-markers	exited without required stage/summary markers
launch-failure	QEMU process could not start
unexpected-exit	exit status outside the contract (e.g. reset loop)

No QEMU verification matrix has completed yet for this build — which is why every field above that depends on it reads “—” or Not Yet Verified.

Build & run instructions Testing doc Engineering process