Why a capability-based microkernel direction?
The project's stated direction is to make resource authority explicit, constrain privileged responsibilities and organize system functionality behind defined service boundaries. A capability-based design makes authority grants a central part of the architecture; a microkernel-oriented design aims to keep the privileged core narrow. These are design goals, not claims that particular mechanisms are already implemented or verified.
Constrained privileged core
Define which responsibilities must remain privileged and which can be delegated to services. The actual boundary requires public design and implementation evidence.
Explicit capabilities
Specify how authority is represented, granted, transferred, restricted and revoked. Concrete capability semantics remain to be documented and verified.
Defined service contracts
Document ownership, IPC contracts, lifecycle and failure behavior before claiming isolation or fault containment.
Evidence-led progress
Publish source references, test environments, acceptance criteria and limitations for each subsystem when they can be reviewed publicly.
What is publicly established today?
The public information currently establishes the project's language and architectural direction, but it does not establish a supported CPU list, a verified boot path, a usable shell, storage behavior, driver coverage or an installable system. Those details should be published only when the project can point to concrete specifications, implementation and repeatable test results.
Repository access and contribution
The Aurora OS repository is private. The public Aurora Website repository contains the source for this website, not the OS implementation. The project's future source-availability policy and any timeline for changing repository visibility have not been published. See Getting started for the current contribution entry points.
Further technical information
Read the architecture overview, the security direction and the development status register. These pages distinguish project direction from implementation evidence.