Architecture overview
Aurora's long-term technical direction is described in project-level architecture material. This public website repository does not contain sufficient product source evidence to assert the current operational state of the OS or browser.
Published project direction
The project-level direction identifies Aurora OS as a from-scratch Rust operating system using a capability-based microkernel architecture. Treat this as architectural direction, not a verified implementation report. The public website repository does not contain the OS source needed to validate kernel mechanisms, service boundaries or runtime behavior.
Explicit capabilities
Design resource access around explicit authority, narrow grants and revocation semantics. A specification must define capability representation, transfer and enforcement.
Small trusted core
Keep privileged code and trusted computing base responsibilities constrained. The actual kernel boundary must be supported by design documentation and source evidence.
Service contracts
Define ownership, IPC contracts, lifecycle and error behavior for services before claiming modularity or isolation.
Containment and recovery
Specify what happens when a service crashes, becomes unresponsive or is compromised, including the limits of recovery.
Questions an architecture description must answer
- Which component owns each resource?
- Where are privilege boundaries enforced?
- How are services discovered and authenticated?
- What happens when a service fails or is compromised?
- Which invariants are tested, and by what test environment?
Evidence boundary
The website's accepted architecture is recorded in ADR-001. Product architecture claims require supporting OS or browser specifications and source references before publication.