Documentation
Where do I find the information I need?
DaemonCore is specification-driven: the system is defined in writing before it is built, and this is where you read those definitions. The public kernel specification describes the architecture, the core concepts and the governance model — the material to read if you are evaluating whether DaemonCore's approach fits your system.
The kernel specification is public. The public reference implementation is being prepared for long-term community use and is not yet available, so this documentation describes how DaemonCore is specified to behave rather than how to install and run it. Everything linked below exists; nothing is stubbed out to fill a table of contents.
How it is organised
Show the documentation disciplines behind the public spec
Behind DaemonCore sit distinct kinds of documentation, each with a different job. You do not need to read them all — knowing they exist is what tells you the project is documented deliberately.
Specifications
The published kernel specification — architecture, concepts and governance. This is what you can read here.
Constitutional & design documents
The approved documents that govern what DaemonCore and its website must be. They keep the product honest and consistent.
Evidence
Genuine recorded executions, classified and traceable. Surfaced on Proof rather than as prose here.
Implementation reports
A traceable record of how each change was delivered and validated — governance you can follow after the fact.
Where to start
New to DaemonCore? Begin with Getting Started. Evaluating the design? Read the Architecture Overview. After quick answers? The FAQ covers the common questions. The published specification:
How it connects
The specification is one level of detail among several. Architecture explains the same structure conceptually; Proof demonstrates it with a genuine recorded execution; Developer covers what is actually available to build against today. Read the specification for precision, and those pages for context.