Don't trust the agent. Trust the proof.

Overview

DCL evaluates AI-agent actions against a security policy and records each decision as an audit event. This Board publishes those records and the payment data attached to them. It shows what DCL exported; it does not verify the records itself.

What each metric counts

Audit Events

Rows in each service's audit chain (Trust Oracle, Bazaar) plus Sentinel events. Canonical events produced by integration demos (Shasta, Tenjin) come from outside those databases and are not included.

Recorded Payments (USDC)

Sum of the payment amounts attached to COMMIT audits for Trust Oracle and Bazaar, plus all Sentinel payments. Payments attached to audits whose verdict is not COMMIT are not included. Amounts are as recorded by each service; this Board does not check them against the chain.

Not COMMIT

The export's no_commit_count. In the exporter source it is calculated as total audits minus COMMIT audits, so it counts every verdict other than COMMIT. Only the row-level events below show the actual verdict value of each audit; Technical details lists the values seen.

Paid Verifications

Not shown. The export does not link every audit to a settled payment, so a count would not be reliable.

On-chain Executions

Not implemented. No execution evidence exists yet.

Evidence explorer

Each row is one audit event. Open a row to see the decision, payment, allowance, and execution evidence separately. The Board does not authenticate the caller and does not independently verify identity claims. Identity fields are shown as exported.

Loading events…

1. Loading events…

Verification architecture

DCL connects a paid security evaluation to a recorded decision. The target design adds a signed authorization and an enforcement contract. Only the first three steps run today.

1. An AI agent requests a security evaluation.Recorded
2. The request is paid through x402. Amount and settlement reference are recorded where the export carries them.Recorded
3. The DCL Trust Oracle evaluates the action and records COMMIT or NO_COMMIT as an audit event (DCL Audit Event v1.0).Recorded
4. An approved decision produces a signed, narrowly scoped Proof of Allowance.Planned
5. A guarded smart contract verifies the allowance before running the protected action. Base is the intended first EVM environment.Planned
6. The execution result is linked to its decision and payment evidence.Planned

How evidence is labelled

One status never stands in for the whole lifecycle. A recorded decision can exist without a verified payment, and a payment can exist without any allowance.

Two different hashes

DCL audit hash

The proof.tx_hash field. A local hash of the audit record, computed by DCL. It is not a blockchain transaction and cannot be looked up on a chain.

Settlement transaction

The payment.tx_hash field. The on-chain transaction that settled an x402 payment. For Base it can be inspected on a block explorer.

Planned: authorization and enforcement

These sections describe evidence the Board will show once the Security Gas flow exists. No allowance or execution record exists today. Fields appear here only when real records back them.

Technical details

What this page loaded, how rows were combined, and where the raw files are.

Raw data

metrics.json is the latest export and carries the counts and canonical events. audit_history.json is the archive of earlier rows. Event fields follow DCL Audit Event v1.0 (dcl.audit.evaluated); identifiers are shown as exported.