#Overview

echOS is the central systems project in AGMA Systems. It exists to answer a direct question: what changes when an operating system is designed as a coherent architecture exercise instead of a pile of isolated subsystems?

#Design goals

keep the kernel surface small and mechanically understandable
make boot, memory, and scheduling decisions explicit
build toward demonstrable behavior rather than theoretical completeness

#Memory model

The current implementation work concentrates on page ownership, allocator layering, and the transition from early boot mappings into a durable kernel address-space model.

Current emphasis

The memory subsystem is treated as the first architectural pillar because every other subsystem inherits its constraints.

#Scheduling direction

The scheduler work is intentionally staged. The first phase validates execution flow, interrupt boundaries, and task state transitions before chasing sophisticated policies.

#Why it matters

The long-term value of echOS is not only the kernel itself. It is also the set of documents, diagrams, and experiments that clarify how low-level decisions accumulate into system behavior.