Source Access

ITISYOU OS is developed in a single monorepo. The repository is private during early development and will open once the V0.1 foundation and its verification evidence stabilize. No public repository link exists yet — this page will carry it when it does.

Repository status

PRIVATE

Visibility: private — early development
Opens: when V0.1 evidence stabilizes — no date promised
Stars / forks / CI badges: none shown — none would be real
License: decided before the repository opens

Why private? Early kernel development involves rapid interface churn and half-landed subsystems. Opening the source together with its requirement matrix and verification evidence keeps the public record honest — the same rule this website follows.

Public record // now

v0.2.0-dev · pre-alpha · QEMU-only

Monorepo layout

kernel/

the x86_64 kernel (library + interactive/selftest binaries)
crates/kernel-core

pure host-testable kernel logic (stage/marker contract)
tools/image-builder

builds bootable disk images (pure Rust) + SHA-256 manifest
tools/qemu-runner

deterministic QEMU test harness with JSON evidence
scripts/

doctor / build / run / test / verify / secret-scan gates
design/

preserved Stitch design export (visual source of truth)
website/

this site — the public engineering record
docs/

architecture, requirements, security model, development story, ADRs
status/

machine-readable, evidence-backed project status

Governance

IN DEVELOPMENT

Development follows binding operating rules and an end-to-end implementation plan. Every requirement ends in exactly one state — implemented + verified, blocked, or not applicable — with evidence. Secret scans run before pushes; dependency choices are recorded with rationale; the dependency set is small and pinned.

When the repository opens, the requirement matrix, ADRs, unsafe-code inventory and QEMU evidence artifacts open with it.