Docs
Canonical documents, proof records, and current downloads.
This is where the project becomes explicit. The public site stays concise; the docs page is where the README, master plan, constitution, and supporting bundles become legible as a real working record.
Each document does a different job. The README is the front door, the master plan is the machine-facing implementation map, the constitution carries the law layer, and the downloads keep the current public bundle usable offline.
README
The outward-facing statement of what the project is, what exists now, and what the current proof is trying to establish.
Open README →Master Plan
The deeper canonical structure behind the project’s phases, names, roles, and current-body architecture.
Open master plan →Constitution
The formal and quasi-legal layer: offices, authority, ratification, crisis distinctions, and governance doctrine.
Open constitution →Linux 7.0 custom kernel
A dedicated home for the Huey Core kernel path: the public writeup, build notes, stable command sequence, current bundle, and the packaged iMac 5K audio fix.
Open kernel page →Raw files
Curated access to the current docs, kernel notes, constitution chapters, research notes, playlist exports, and archival references.
Open downloads →Supporting papers
Hierarchy, node models, storage, safety, bifurcation, Ozymandias, and the future-facing note set.
Open research →Atlas-1 and continuity material
Archival transcripts and continuity documents help show how the project actually evolves instead of pretending every decision appeared fully formed.
What this page is doing
The site introduces the work. The documents explain it. The master plan tracks implementation. That division keeps the project legible.