ChrisOS Research Project¶
In this chapter
Source branch: main
Documentation baseline:
e05a17fd7633
Publication model: static / revision-bound
Abstract. ChrisOS is an experimental systems ecosystem containing an x86-64 kernel, ChrisC and CLVM, native compiler/assembler/linker components, ChrisFS, graphics and desktop subsystems, networking, and the ChrisVM/ChrisCPU machine-emulation stack. The documentation is organized as a dependency-ordered technical corpus from physical foundations to operating-system research.
Canonical organization¶
The documentation has two independent organizational layers:
| Layer | Purpose | Authority |
|---|---|---|
| learning curriculum | establishes prerequisite order and conceptual progression | data/curriculum.yml |
| repository collections | provides stable paths and subject-oriented archival grouping | docs/en/* and docs/pt-br/* |
The learning curriculum is authoritative for reading order. Directory numbering is retained for URL stability and repository maintenance; it does not override prerequisite order.
Learning path and current gaps
Developer Guide
Dependency chain¶
The principal dependency chain is:
matter and physical models
↓
mathematical tools required by the physical model
↓
electric fields, circuits and electromagnetic behavior
↓
semiconductor devices and CMOS
↓
Boolean and sequential logic
↓
representation, data structures and algorithms
↓
CPU architecture and platform interfaces
↓
firmware and boot
↓
kernel, memory, concurrency and processes
↓
language systems and persistent storage
↓
graphics, networking and desktop
↓
emulation, virtualization and self-hosting
↓
real hardware, validation and formal specifications
Missing chapters remain visible in the curriculum and are not bypassed by the canonical previous/next sequence.
Curriculum levels¶
| Level | Technical scope |
|---|---|
| 01 · Matter, mathematical tools, electricity, devices and logic | matter, electrostatics, circuits, semiconductor devices, CMOS, Boolean logic, arithmetic circuits, state and memory cells |
| 02 · Representation and algorithms | discrete mathematics, binary representation, complexity, data structures and systems algorithms |
| 03 · Instruction execution and platform | datapaths, microarchitecture, ISA, x86-64, memory hierarchy, PCIe, MMIO, DMA and ACPI |
| 04 · Reset to kernel entry | processor reset, firmware, UEFI, Limine, ELF, linking and higher-half entry |
| 05 · Kernel, memory and execution contexts | trust boundaries, exceptions, PMM, paging, TLBs, concurrency, user mode and process lifecycle |
| 06 · Languages, compilers and runtimes | compiler construction, ChrisC, CLVM, JIT and the native toolchain |
| 07 · Persistent state and filesystems | block storage, ATA/AHCI/NVMe/VirtIO and ChrisFS structures/recovery |
| 08 · Bytes to desktop | framebuffer, 2D graphics, composition, input, windows and applications |
| 09 · Geometry, rasterization and GPUs | transformations, rasterization, VirtIO-GPU, VirGL and programmable shading |
| 10 · Networks and protocol state | Ethernet, IPv4, UDP, TCP, VirtIO-net and sockets |
| 11 · Emulation and virtualization | x86 emulation, ChrisVM/ChrisCPU, VMX/SVM and second-level translation |
| 12 · Bootstrap, validation and research | self-hosting, real hardware, validation, specifications, history and corpus maintenance |
| 13 · Development environment and contribution | Linux, Windows/WSL2, build, debugging, testing, troubleshooting and contribution workflow |
Document structure¶
Technical chapters separate the following evidence classes:
- physical or mathematical theory;
- general systems architecture;
- current ChrisOS/ChrisCPU implementation;
- executable validation or source-derived evidence;
- known limitations;
- future architecture explicitly identified as future work.
A source symbol is not sufficient evidence for feature completeness. Implementation claims are revision-bound.
Navigation semantics¶
Each curriculum chapter exposes:
- curriculum level and module;
- absolute position in the canonical sequence;
- previous and next planned chapters;
- technical prerequisites declared by the chapter;
- authored chapters that depend on it;
- language pair;
- source revision and source files.
An absent previous or next chapter is rendered as an explicit curriculum gap rather than silently skipped.
Repository collections¶
The stable repository collections remain available for reference navigation:
| Collection | Subject |
|---|---|
| Foundations | physical, electrical, digital, mathematical and algorithmic prerequisites |
| Computer architecture | CPU, x86-64, memory hierarchy and platform |
| Boot | firmware, executable layout and kernel entry |
| Kernel | privileged execution, interrupts, processes and kernel model |
| Memory | physical/virtual memory, TLBs, allocation and lifetime |
| Storage | block devices and filesystems |
| Language systems | compilers, runtimes and native toolchain |
| Graphics | framebuffer, 2D/3D graphics and GPU interfaces |
| Emulation | ChrisVM, ChrisCPU and virtualization |
| Networking | network protocols and devices |
| Desktop | windows, input and applications |
| Self-hosting | bootstrap and internal rebuild |
| Real hardware | installation, bring-up and compatibility |
| Validation | tests, gates, faults and measurements |
| Specifications | project formats, ABIs and protocol contracts |
| Architecture history | revision-bound architectural history |
| Developer Guide | workstation setup, build/run/debug, testing and contribution workflow |
Evidence policy¶
- Current source on main.
- Reproducible checks and gates against the same revision.
- Current in-repository specifications.
- Historical material explicitly bound to its source revision.
- Future work explicitly separated from implemented behavior.