Source Access

ITISYOU OS is developed in a single monorepo. The source repository is private. It has been made public only briefly, so that GitHub CI could run for releases, and the owner decides when it opens. Published releases, their checksums and the engineering evidence are on this site.

Repository status

PRIVATE

Visibility: private — public only briefly, for release CI runs
Opens: the owner decides — no date or condition promised
Stars / forks / CI badges: none shown — none would be real
License: none published

What is public is the evidence: every release’s version tag, commit and CI run; since v0.8.1, its boot images with SHA-256 checksums; the engineering documents; and the status and development ledger generated from the repository.

Public record // now

v1.0.0 · experimental · 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.

The requirement matrix, ADRs, unsafe-code inventory and QEMU evidence artifacts live in the repository; this site carries the engineering documents and the release evidence drawn from them.