Developer
How can I evaluate DaemonCore as a technical practitioner today?
By reading the specification and inspecting real evidence — not by installing anything.
There is no package to pull and no repository to clone. The kernel specification is public; the reference implementation is not. You do not need it to judge the engineering: the governance model, the boundaries it enforces, and a genuine execution passing through them are all inspectable now. This page shows what is real today and is explicit about the gap, so you can decide whether DaemonCore is worth your attention.
How it is engineered
Specification-driven
Governance is defined before execution — and the project is built the same way. The kernel specification is published and stable while the implementation is still being prepared.
Governed & deterministic
Deterministic boot, capability ceilings that only ever narrow, template-constrained operations and an audit trail. These are specified and operational in V1, not aspirational.
Evidence-first
Claims are backed by genuine recorded executions rather than marketing. Where something is not proven — or ran advisory, or was not verified — the site says so plainly.
Validated by construction
Every build validates the knowledge graph and the architecture graph, and the public site ships zero client-side JavaScript by policy. Discipline enforced by the build, not by good intentions.
What you can inspect today
Three artefacts, all genuine: the public kernel specification in the Documentation; the layered design and its explorable graph on Architecture; and a real recorded execution admitting a request through the governance gate. The recording is the one to start with — you can step through it event by event and inspect each moment against its provenance.
Governance Before Execution — Recorded Admission — Replay the recorded admission
Replay the first genuine recorded DaemonCore execution (RUN-001): a code_review_request passing through identity, publication, claim, the governance gate and Execution creation.
RUN-001 is genuine but partial: the admission phase only, gate advisory, no model executed, unsealed and not independently verified. Those limits are stated in full on Proof.
What is intentionally not yet public
The runtime, tooling and production components are under active private development. None of the following exists publicly today:
- A public repository or source. The reference implementation is being prepared for long-term community use and is not yet released.
- An install path, package, SDK or client library. There is nothing to install, and no clone-and-run instructions — they would not work, so they are not offered.
- Extension or plugin APIs. None are published.
- Licensing and release timing. Not yet decided; no date is committed.
Further capabilities — such as cryptographic action signing and hardware-backed attestation — are planned, not available. When the supporting work is ready, this page will change with it.
Where to go next, depending on what you want to evaluate: