Getting started with DaemonCore
DaemonCore is a governed agent kernel and execution platform. Start by separating the architectural model from the behaviour demonstrated in a particular runtime capture.
Understand the operating identity
An Agent Definition composes three independent dimensions:
- Role: responsibility, expertise and the associated authority boundary.
- Profile: contextual specialisation or operating mode. It cannot add authority absent from the Role.
- Persona: communication and interaction disposition. It grants no authority or specialist competence.
Project scope, worker, vendor and session identity are separate runtime inputs. Host profiles are also distinct from the Profile used in an Agent Definition.
Inspect the evidence
RUN-001 is a partial recording of admission into an Execution. The gate was advisory, no model executed and the final outcome was not captured. It should not be read as a successful end-to-end run.
Working with an authorised checkout
The canonical repository’s development entrypoints are pip install -e ., daemon --help, daemon up and daemon smoke. These require access to the runtime repository and its configured environment; this website does not distribute a standalone runtime installer.
Deterministic configuration and prompt compilation do not make model responses deterministic.
Choose your next step
- Architecture — explore the system and its boundaries.
- Developers — inspect the implementation model.
- Proof — distinguish illustrative explanations from recorded behaviour.
- Early access — current availability information.