Developer
How can I evaluate DaemonCore as a technical practitioner today?
Start with the architecture and a real execution trace.
The runtime contains executable services, a CLI and compiled operating definitions. This public site provides reference material and recorded evidence; it does not distribute an installer or grant repository access.
How it is engineered
Specification-driven
Governance is defined before execution — and the project is built the same way. The canonical architecture distinguishes operating contracts from the runtime that implements them.
Explicit composition
Role, Profile and Persona are independently reusable. A deterministic compiler projects their definition into an operating prompt with source provenance.
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 uses static HTML with JavaScript for its interactive explorers and diagrams. Evidence rendering requires the genuine capture files.
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.
Working with an authorised checkout
The canonical repository documents these development entrypoints:
pip install -e .
daemon --help
daemon up
daemon smokeThese commands require the runtime repository and its configured environment. This website does not provide a self-service download. Check access information →
Evaluate the configured enforcement mode and the actual execution path. A compiled definition or an admission record alone does not establish that a task completed safely.
Where to go next, depending on what you want to evaluate: