Feature
Every AI operation generates an HMAC-signed, tamper-evident receipt. Prove to auditors exactly what policies were applied, when, and with what result—with cryptographic certainty.
compliance_receipt.json
{
"receipt_id": "rcpt_a3f2c1b8d4e5f6a7",
"timestamp": "2025-01-01T12:00:00.000Z",
"version": "1.0",
"evaluation": {
"decision": "REDACT",
"policies_applied": ["pii-protection", "content-safety"],
"policies_passed": ["content-safety"],
"policies_triggered": ["pii-protection"],
"duration_ms": 3
},
"content": {
"input_hash": "sha256:a3f2c1...",
"output_hash": "sha256:b4e5d6...",
"pii_detected": ["email", "phone"],
"redaction_count": 2
},
"context": {
"user_id": "user_123",
"session_id": "sess_456",
"endpoint": "/api/chat",
"framework": "langchain"
},
"signature": {
"algorithm": "HMAC-SHA256",
"hmac": "d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9..."
}
}HMAC signature matches. Receipt has not been modified since creation.
HMAC mismatch detected. Someone has modified the receipt data.
Verify a receipt
from tork import ComplianceReceipt
receipt = ComplianceReceipt.load("receipt.json")
# Verify signature integrity
is_valid = receipt.verify(secret_key="your-signing-key")
if is_valid:
print("Receipt is authentic and unmodified")
else:
print("WARNING: Receipt has been tampered with!")JSON files on disk. Simple, no dependencies.
Relational database with full query support.
S3, GCS, or Azure Blob with automatic rotation.
Managed storage with dashboard and analytics.
Real-time delivery to your SIEM or logging system.
Implement your own storage adapter.
Demonstrate continuous monitoring and policy enforcement over time
Records of processing activities with data minimization proof
Track all access to PHI with timestamped evidence
Prove to legal/compliance teams that AI is governed
Forensic evidence for investigating AI-related incidents