The Governance Forum’s Audit Problem
DeAgenticAI’s Agentic Control Plane enforces cryptographic policy over AI agent authority — separating what an agent can do from what it is authorized to do — in Web3 and enterprise financial environments. For DAO governance forums, this means every treasury agent action comes with a cryptographic record of what was authorized.
The quarterly treasury review was routine until a new committee member asked the question no one had prepared for. The DAO’s treasury agent had executed 200 transactions over the previous quarter — yield deployments, protocol allocations, rebalancing operations. The treasurer pulled up the activity log: 200 rows, each with a timestamp, amount, destination address, and protocol. Every transaction was there.
‘How do we know the agent was authorized to make each of those?’ the committee member asked. ‘Where’s the proof the spending limits were enforced?’
The activity log couldn’t answer. It recorded what the agent did — not what the agent was authorized to do, or proof those authorization parameters were enforced at the signing layer before each execution.
DAO governance forums need a policy enforcement record — not just a transaction log — showing each agent action was cryptographically authorized at signing.
Activity Log vs Policy Enforcement Record
An activity log records what happened — transactions submitted, amounts, destinations, outcomes. Standard DAO tooling maintains activity logs. They answer: ‘what did the agent do?’
A policy enforcement record records that each action was cryptographically authorized before it happened — and provides verifiable proof. It answers: ‘was the agent authorized to do what it did, and how was that authorization enforced?’
Governance forums need the second document — especially when reporting to stakeholders who didn’t participate in the governance vote that defined the agent’s parameters.
For background on the spending limit parameters that get recorded, see the guide on setting on-chain spending limits for an AI agent managing DAO treasury. For the override controls the record must capture, see the guide on DAO treasury automation without losing override control.
The Three Components of a Policy Enforcement Record
A policy enforcement record for a policy-governed AI agent contains three distinct elements. Together they answer the governance forum’s accountability question completely.
Component 1: Policy version record. Which version of the Policy DSL governed each transaction. This includes the specific spending limit parameters in effect — per-transaction cap, daily cap, recipient allowlist, protocol allowlist, time window. A governance forum can verify that a transaction executed under the policy version the forum voted to approve.
Component 2: Intent Sanitization record. That each transaction proposal passed Intent Sanitization validation before reaching the signing layer. Intent Sanitization checks that the agent’s proposed transaction matches its declared intent — catching orchestrator-level manipulations before signing. The record confirms the proposal was validated, not just that the transaction was submitted.
Component 3: Signing verification record. That each signing node independently verified the policy authorisation hash before contributing its partial signature. This is the cryptographic proof that policy was enforced at signing — not configured in advance and trusted, but independently verified at execution time.
[Visual: 3-component diagram — policy version hash / Intent Sanitization record / signing verification record as stacked layers within each transaction record]
Each transaction in a policy-governed treasury carries all three components. The enforcement record is not a summary — it is a per-transaction proof set.
DeAgenticAI’s Implementation: Records Generated by Architecture, Not Maintained by Operators
The governance accountability property that matters most: the record is generated by the enforcement infrastructure, not maintained by the operator.
A Gnosis Safe activity log is maintained by the Gnosis Safe UI. If the UI’s record-keeping is incomplete or unavailable for a particular operation, the activity record may have gaps. It is a separately maintained log that reflects what the UI observed.
DeAgenticAI’s policy enforcement record is generated by the Agentic Control Plane’s enforcement layers as a byproduct of enforcement itself:
Layer 2 (Intent Sanitization) produces the validation record as it validates each proposal. Layer 3 (Policy DSL) records the policy version hash as it evaluates each transaction against spending parameters. Layer 7 (Intent-Evaluated MPC) records the signing node verifications as each node verifies the policy hash.
None of these records are written separately from the enforcement operation. The record is the enforcement. A governance forum cannot have enforcement without a record, and cannot have a record that doesn’t reflect actual enforcement.
[Visual: Comparison table — Activity Log (Safe UI) vs Policy Enforcement Record (ACP) — rows: what it records / what it proves / generated by / external verifiability]
This is what makes the enforcement record useful for governance accountability — not just as documentation, but as proof.
What Governance Forums Can Do With a Policy Enforcement Record
Three practical use cases for the DAO Treasury Lead.
Stakeholder reporting. When reporting to token holders or institutional stakeholders, the governance forum presents the enforcement record alongside transaction history. Not just ‘the agent executed 200 transactions’ — but ‘each transaction was executed under Policy DSL version X, passed Intent Sanitization, and was verified by signing nodes against the policy authorisation hash. Here is the verifiable record.’ Stakeholders who didn’t participate in the governance vote can independently verify that the agent operated within authorized parameters.
External audit and compliance. The enforcement record can be provided to external auditors as cryptographic proof of policy-governed execution. An external auditor verifying the record does not need to trust the DAO’s log maintenance practices — only the cryptographic record produced by the signing infrastructure.
Override and escalation verification. The enforcement record includes records of blocked and escalated transactions alongside executed ones. A governance forum can verify that transactions exceeding spending limits were correctly escalated, that out-of-window transactions were blocked, and that escalation paths functioned as specified. Absence of escalation records for a clean quarter is itself a compliance signal.
See the DAO Treasury Automation pillar for full context on the policy-governed treasury architecture.