Section A · Writing

The reasoning, written down.

Skyra was designed one note at a time. The notes live in the repository, which is private for now; these are the ones worth reading first. Ask and I will send any of them.

Section B · Start here

Why it exists.

Grips and invariants
The six pains that drove the design, and the invariants they force.
The research question
Can approval move from every action to one grant, while matching a conventional runtime on cost and success and containing strictly more? The metrics, the baseline, the plan.
Where the project is
Properties, patterns, and what runs today.

Section C · Design notes

How it was reasoned out.

The room
Authority derived from state and proposal. A Horizon is an execution context, shared unless narrowed; faults climb to whoever can grant.
A Horizon is a process
The Horizon is the process; OS processes are its workers.
Types by origin, and routes
The runtime computes types; models write routes once per kind of return, at a novelty interrupt.
Crossing the boundary
The questions every new crossing of the trusted boundary has to answer.
The sky dreams
The desktop sky as a projection of the record tree: every pixel derived from a record.
The controller, package by package
Every design decision mapped to the line that implements it.