Documentation

These pages render the actual repository documentation — the same markdown that governs development — copied verbatim at build time. If a doc says something is planned, it is planned.

Architecture docs/ARCHITECTURE.md What exists now — system shape, crate boundaries, boot contract, observability — and the boundaries later milestones build inside.
Build and Run docs/BUILD_AND_RUN.md Reproducible environment, build, and QEMU instructions for a Windows host. Every command is the exact command used in verification.
Testing docs/TESTING.md The test pyramid: host unit tests, QEMU boot smoke, in-kernel selftests, negative cases — and the failure classification contract.
Security Model docs/SECURITY_MODEL.md The central principle — AI has intelligence, not authority — trust boundaries, V0.1 concrete requirements, and the future capability model.
Threat Model docs/THREAT_MODEL.md Assets, adversary/failure assumptions scoped to V0.1 development reality, mitigations, and explicit non-threats.
Known Limitations docs/KNOWN_LIMITATIONS.md The honest current state: what the kernel does not do yet, updated continuously.
Roadmap docs/ROADMAP.md Milestones V0.1 through V1.0, sequenced by dependency, not calendar. No fabricated dates.

Additional internal records (requirement matrix, unsafe inventory, ADRs, session logs) live in the repository and will become browsable when source access opens. See source access.