How is GenOS coming along?

Reading the progress bar

We are working toward a useful console system. Here is the overall progress on our roadmap checklist, including plans beyond the first console release:

59% [###########---------] 59% (77/130)

The bar counts checked boxes in the source roadmap. Each box describes a particular task or test; boxes do not all represent the same amount of work. It is a checklist count, not a measure of how close GenOS is to a finished release. Partial means some work in that area exists, but more work, testing or integration remains. A checked box covers only the work or evidence it describes.

Experimental / ALPHA. There is still plenty to do. Please do not use GenOS for production, daily use, important data, secrets or hostile workloads.

Work in progress

Checked and open items in each part of the roadmap. Storage / S2 also includes S1 and the storage baseline. Section names and status notes come from the source roadmap.
Section	Done	Open	Progress	Notes from the roadmap
F0 F0 — Green, reproducible verification	9	1	90% `[##################--] 90% (9/10)`	Checks published, enforced and integrated; independent reproduction remains open.
F1 F1 — Complete exception and interrupt entry	9	2	81% `[################----] 81% (9/11)`	Base entry delivered; extended context/containment open.
F2 F2 — Hardware-enforced page protections	4	1	80% `[################----] 80% (4/5)`	Protection bits and selected mappings proven; alias policy partial.
F3 F3 — Transactional physical and virtual memory	8	1	88% `[#################---] 88% (8/9)`	Bounded owner/generation grants, mapping pins and rollback delivered; sharing/device policy incomplete.
F4 F4 — Kernel ownership and decomposition	4	2	66% `[#############-------] 66% (4/6)`	Decomposition adapters implemented; retained full regressions pass on their recorded sources, while F4.1/F4.2 qualification remains open. F4.4 has local unsafe-boundary review evidence.
F5 F5 — Explicit single-core and concurrency model	5	2	71% `[##############------] 71% (5/7)`	F5.1/F5.3 have retained local evidence for the BSP policy; F5.4 lacks retained combined dynamic-TX delivery/reset proof, and complete-span/mixed-workload latency remain partial under F5.2.
F6 F6 — Test boot, release boot, fuzzing, and fault injection	7	1	87% `[#################---] 87% (7/8)`	Coverage-guided campaigns have local evidence; single-boot long-run qualification remains incomplete.
F7 F7 — Reviewable delivery process	2	2	50% `[##########----------] 50% (2/4)`	Process defined; enforcement/evidence must accompany each release.
S2 Stage 4 continuation — Storage integrity and useful capacity	6	2	75% `[###############-----] 75% (6/8)`	Partial. S1 fixes current failure semantics; S2 depends on S1 and F3/F4.
N1 Stage 5.4E — Concurrent and production-oriented TCP	2	4	33% `[######--------------] 33% (2/6)`	Partial, not unstarted. Extension depends on R1 and C1 stream/authority contracts.
N2 Stage 5.5 — IPv6 dual stack	1	4	20% `[####----------------] 20% (1/5)`	Partial; control-plane and bounded kernel UDP/AAAA foundations have local evidence; application/host completeness remains open.
SEC Stage 6 — Security, identity, and trusted distribution	0	6	0% `[--------------------] 0% (0/6)`	Partial SEC1/SEC2 slice; other gates planned beyond current capability/protection foundations. Required before corresponding hardened, sensitive-data or network claims.
C1 C1 — Native application, memory and stream contracts	6	0	100% `[####################] 100% (6/6)`	Implemented
C2 C2 — Terminal input and command execution	5	0	100% `[####################] 100% (5/5)`	Implemented
C3 C3 — Composable jobs and scripts	3	1	75% `[###############-----] 75% (3/4)`	Implemented, Partial
C4 C4 — Session, shutdown and recovery	4	0	100% `[####################] 100% (4/4)`	Implemented
C5 C5 — Stable console reference acceptance	2	6	25% `[#####---------------] 25% (2/8)`	Partial.
H Stage 8 — Modern hardware, SMP, and power management	0	6	0% `[--------------------] 0% (0/6)`	Partial modern VM network profile; block/console, physical hardware and SMP expansion remain planned.
Stage 9 Stage 9 — Userspace graphics and product experience	0	5	0% `[--------------------] 0% (0/5)`	Deferred until R3 and the required application/security/device contracts.
Stage 10 Stage 10 — Production candidate and daily-use qualification	0	7	0% `[--------------------] 0% (0/7)`	Planned. Evaluated per supported product/profile, including console-only.

Work marked Blocked

Blocked means a task is waiting for a dependency before it can move forward.

F1.2: inventory all process-visible register state. Implement a bounded, CPUID-validated eager XSTATE save/restore policy, with a justified narrower fallback; define initial state and kernel FPU/SIMD use. Test every enabled component through preemption, syscall, fault and reuse.
F1.4: specify and test NMI/machine-check/same-IST nesting, fault-during-return and malformed return state. Recover only where a safe recovery contract is demonstrated; otherwise halt deliberately.
F2.3: extend actual CPU access tests across every mapping family and feature profile, including stale translations, cross-process aliases and failed protection changes.
F3.2: retire references, mappings, translations and device use before scrubbing/reuse. Wrong-owner, stale-generation, duplicate, aliased and pinned releases must leave state and bytes unchanged.

Milestones we are working toward

R1, R2 and R3 are named checkpoints with requirements in the roadmap. A high checklist count does not by itself reach one of these checkpoints.

R1: Not yet achieved.
R2: Not yet achieved.
R3: Not yet achieved.

For the details, please read our roadmap notes and the source tree. That is where we keep the requirements and test records.

New to the terms in the roadmap? Our little glossary may help.

Last modified (page generated): 2026-10-21 19:00:32 UTC. Source: commit 956acde on roadmap/codex-2026-10-14.