Foundations¶
In this chapter
Position in the corpus¶
The foundations establish the lowest abstraction layers required by later architecture, kernel, compiler, graphics, networking and emulation chapters.
matter and physical models
↓
mathematical tools required by the physical model
↓
electric charge, field and potential
↓
circuit quantities and network laws
↓
energy storage, transients and AC behavior
↓
high-speed signaling, noise and power delivery
↓
semiconductor electrostatics
↓
MOSFET and CMOS
↓
logic levels and Boolean abstraction
↓
combinational arithmetic
↓
sequential state, clocks and memory cells
↓
representation
↓
complexity
↓
data structures
↓
systems algorithms
Physical and electrical foundations¶
The canonical sequence is:
- matter, atoms and physical models;
- vectors and complex-number tools required later by field/circuit analysis;
- electric charge, field, potential and energy;
- voltage, current, resistance, energy and power;
- Ohm's law, Kirchhoff's laws and circuit analysis;
- capacitance and inductance;
- RC, RL and RLC transients;
- AC signals, phase, frequency and impedance;
- electromagnetic induction and transformers;
- transmission lines and differential signaling;
- noise, grounding and signal integrity;
- power delivery, regulation and decoupling.
These topics define the physical assumptions behind semiconductor and digital behavior.
Semiconductor and digital foundations¶
The device sequence is:
- crystal structure, bands and doping;
- p-n junctions;
- MOS capacitor electrostatics;
- MOSFET and CMOS;
- CMOS delay and power;
- logic thresholds, fan-out and noise margins;
- Boolean algebra;
- binary number systems;
- combinational logic;
- arithmetic circuits;
- sequential logic;
- latches and flip-flops;
- registers, counters and state machines;
- clock timing;
- SRAM and DRAM.
The transition from electrical voltage ranges to abstract Boolean state is therefore explicit.
Representation and algorithms¶
The software-foundation sequence is:
- discrete mathematics: sets, relations and functions;
- proof, invariants and induction;
- data representation, layout and pointers;
- algorithmic complexity and systems cost models;
- recursion, recurrences and amortized analysis;
- arrays, lists, stacks and queues;
- hash tables;
- trees, heaps and tries;
- graphs and disjoint-set union;
- bitmaps, rings and free lists;
- sorting and searching;
- graph algorithms;
- string and parsing algorithms;
- algorithms implemented by ChrisOS.
Dependency rule¶
A later chapter may assume a concept only when one of the following is true:
- the concept is defined in an earlier curriculum chapter;
- the chapter contains a bounded local derivation sufficient for its use;
- the concept is marked as a forward reference rather than treated as established knowledge.
This rule prevents hidden jumps between physical, mathematical and software abstractions.
Implementation linkage¶
Foundational theory is connected to current implementation at the first appropriate boundary.
Examples include:
| Foundation | Later implementation |
|---|---|
| finite-width arithmetic and flags | ChrisCPU arithmetic semantics |
| registers and state machines | ChrisArchitectureState |
| bitmaps | PMM allocation state |
| ring buffers | VirtIO queues and kernel job queues |
| trees/graphs | filesystem, compiler and dependency structures |
| charge/capacitance/timing | physical limits beneath memory and CPU timing models |
A foundational chapter does not claim that ChrisOS directly implements the underlying physical device.
Evidence rule¶
Physical and mathematical chapters distinguish:
- normative equations and definitions;
- model assumptions;
- illustrative numerical examples;
- limits of the model;
- later architectural consequences;
- current ChrisOS linkage.
Source-linked claims are revision-bound. Physical-device claims rely on primary technical references rather than inference from kernel code.