FOUNDING NOTES / VISION
Small enough to explain.
Asterhold began with a question: could you follow a system from firmware entry to an application’s first instruction, and explain who owns each resource along the way?
I / PURPOSE
Build to understand
Starting with a blank kernel makes every dependency a choice. We can teach the reason for an entry stack, watch the processor deliver a fault and test what survives when an application ends. Rust is the first choice for implementation; assembly is reserved for the boundaries where the CPU requires it.
II / METHOD
Make the claim observable
Each mission asks a question small enough to answer in a real VM. A printed message alone cannot prove that an app ran in user mode. Independent register and page-table inspection can corroborate it. A timeout must be recorded as a failure when the guest was expected to regain control.
III / HORIZON
A Kingdom in the stars
The celestial identity expresses a long view: small systems, explicit resource budgets and the ability to operate locally. Space is an inspiration, not a claim of flight qualification. The first practical destination is a VM that can host useful applications and services.
Kingdoms host applications; Realms are meant to hold people’s belongings. Giving a program a place to run should never silently give it access to someone’s documents.
See the release objectives