Governance layer / in development

Govern autonomous AI.
Without taking autonomy away.

DaemonCore is the governance and control layer for autonomous AI agents — establishing authority, enforcing boundaries and preserving evidence around real agent work.

See it work Inspect the architecture

Enter the system

01 / THE MISSING LAYER

AI agents don’t just answer.
They act.
Instructions alone are not authority.

Orchestration decides what to do. Governance determines whether it is allowed. DaemonCore connects external authority and policy directly into the agent’s operating context, enforces boundaries around execution, and preserves evidence of what happened — without removing the autonomy that makes agents useful.

Why instructions alone aren’t governance

02 / THE OPERATING IDENTITY

An agent does not simply wake up
and start working.

DaemonCore resolves a governed definition, applies the project binding and policy constraints, then selects an eligible runtime worker and assembles its operating context.

Architectural model · illustrative, not a live boot trace

01 / Definition resolves

Definition resolves

Role, Profile and Persona form a governed definition: responsibility, operating posture and interaction — never permission.

Authority is bounded

The Role establishes the authority ceiling. Policy and safety controls can only narrow what the system permits.

Project binding activates

The definition is placed in project scope with its local restrictions, routing and effective operating selection.

Worker eligibility resolves

Candidate workers are evaluated by host, adapter, model, runtime profile and available capabilities against the established identity and authority bounds.

Operating context assembles

Kernel, vendor, project and resolved-definition material settle into the context from which governed work can begin.

03 / OBSERVABLE OUTPUT

RUN-001 · RECORDED · PARTIAL

The system becomes
something you can inspect.

A genuine recorded run of the DaemonCore runtime: a code_review_request published under an established identity, admitted through the governance gate and recorded as an Execution.

RUN-001 / RUNTIME LOGGOVERNANCE.GATE / ADVISORY

TRACE IDENTIFIEREVID-e9b58172EXECUTIONexec-a41c2c95cbc8

[INFO] [Enforcement] Config loaded: mode=advisory, strict_domains=(), threshold=10
[WARN] [EnforcementGate] Advisory: No skill match: No candidates found in any registry
[INFO] [Execution] Created exec-a41c2c95cbc8 | intent=code_review_request | trigger=queue_message:EVID-e9b58172 | participant=reviewer
[INFO] [MaxBusBridge] Dispatched EVID-e9b58172 -> execution exec-a41c2c95cbc8 (admission only; outcome pending)

ADMITTED / OUTCOME PENDINGReplay the evidence

RUN-001 is partial: admission was recorded, but no model executed; the gate was advisory and the recording has not been independently verified. The full illustrative walkthrough (GOV-001) is on the Proof page.

04 / CONTROL, MADE EXPLICIT