Architecture reference
DaemonCore combines declarative operating contracts with executable runtime services. The contracts describe required behaviour; runtime implementation and deployment configuration determine which checks a particular path applies.
Agent composition
Role + Profile + Persona → Agent Definition. These are independently reusable dimensions. Role supplies responsibility, domain competence and its authority boundary. Profile specialises its application. Persona shapes communication and interaction without adding authority or expertise.
Worker, vendor, model, project and session identity remain separate runtime inputs. Host profiles and Agent Definition Profiles are distinct concepts.
Runtime binding and provenance
The runtime compiles model-facing operating prompts from the canonical definitions and reports source provenance. Current worker binding uses project persona records matched by role ID, alias or archetype. Eligible workers describe possible bindings; observed live routing is separate evidence.
The Role/Profile/Persona authority cutover does not replace the entire kernel, vendor and project boot chain. Do not treat a projection compiler as the complete boot implementation.
Messaging and execution
MAX Bus routes structured work through role-scoped queues. A message can be published, claimed and admitted into an Execution before the downstream work has completed.
The configured governance mode matters. Advisory findings and blocking rejections are different behaviours. The published RUN-001 capture records advisory admission only.
What to verify in a deployment
- Which operating definitions and configuration sources were resolved?
- Which worker and runtime actually performed the action?
- Which decision point mediated it, and in what mode?
- Which tools and credentials were reachable outside that path?
- Does the evidence include the final result, or only admission?
Explore the system relationships or inspect the evidence catalogue.