DingDawg Governance — Verified Results
Real test data. Real receipts. Real audit trails.
What a Governance Receipt Looks Like
Every governed action produces a cryptographically signed receipt. The IPFS CID is immutable proof — if the receipt changes, the CID changes.
{ "receipt_id": "gov_1a2b3c4d5e6f", "agent_id": "@hipaa-intake", "action_type": "read_patient_record", "decision": "allow", "risk_score": 22, "risk_tier": "medium", "timestamp": "2026-04-06T09:00:00Z", "explanation": { "primary_trigger": "read_only_access", "causal_chain": [ "read_patient_record → read_only_access policy → +8pts", "cumulative_score=22 < 40 → decision=allow" ], "confidence": 0.98, "counterfactual": null }, "ipfs_cid": "bafybeigdyrzt5sfp7udm7hu76uh7y26nf3efuylqabf3oclgtqy55fbzdi", "verified_badge": { "text": "Powered by DingDawg Verified", "embed_url": "https://dingdawg.com/verify/gov_1a2b3c4d5e6f" }}Every governed action produces a cryptographically signed receipt. The ipfs_cid is an immutable Content Identifier — if the receipt is altered in any way, the CID will no longer match. Regulators can verify any receipt independently via any IPFS gateway.
Governed vs Ungoverned Agent
What you get when governance is present — versus what a raw, unguarded agent leaves behind.
| Metric | Raw Agent | DingDawg Governed |
|---|---|---|
| Audit trail | None | Every action receipted |
| Failed action detection | Silent | Blocked + logged |
| Rollback capability | Manual | Automated |
| Regulatory documentation | None | Auto-generated |
| Harness score | 34/100 | 91/100 |
| Compliance gap report | N/A | Instant |
Verified Test Results
Independent test runs. Every suite green. Timestamps on-chain.
govern_actionLNN explanation field returned on every call
audit_trailReceipts persisted to ~/.dingdawg/governance/receipts/
compliance_checkSB 205 controls mapped, gaps identified
loop_auditAll 6 DDLP tools verified end-to-end
Cryptographic Proof, Not a Promise
Every receipt gets a Content Identifier (CID). The CID is a cryptographic hash of the receipt content — if the receipt changes even by a single character, the CID changes. There is no way to silently alter a receipted governance decision.
Regulators can verify any receipt by checking its CID against IPFS using any public gateway — no DingDawg account required. Your compliance history outlives any company, including ours.
- AlgorithmSHA-256 multihash
- Codecdag-pb / UnixFS
- VersionCIDv1 (base32)
- Tamper-evidentYes — hash mismatch = invalid
- Verifiable without DingDawgYes — any IPFS gateway
Verify Any Receipt
Anyone can verify a dingdawg receipt — no account required. The public key is permanent and independently verifiable by any auditor.
Ed25519 Public Key
88f4fdde99d31b16bff3079138e5096d24dddaff922314490935e91d69837281Verify via curl
curl -X POST https://verify.dingdawg.com/v1/verify \
-H "Content-Type: application/json" \
-d '{"receipt": <signed receipt JSON>}'Ready to Govern Your Agents?
Score your agent. Run a compliance report. Every governed call produces a receipt like the one above — cryptographically signed, IPFS-immutable, regulator-ready.