Action domain

Action Proof & Non-Repudiation

The core DAR domain: prove an action occurred at execution time, with integrity guarantees that make later alteration detectable. DAR preserves facts, not intent or correctness.

Receipt moment

Issue a DAR at the exact point the system commits an action (or decision) that could later be disputed.

issueReceipt({ actor, action, object, ref, ts, policy? })

Preserved fields

actor · action · object · timestamp · stable reference · integrity proof
Optional: policy/config version, environment tag, correlation reference

Common integration surfaces

Payments, identity, security enforcement, workflow approvals, and automated operations. In each case, the receipt is a durable artifact that can be exported or referenced later without requiring the platform to become the “source of truth” in disputes.

Why this avoids “source of truth” liability

Without receipts, platforms are pressured to explain what happened using mutable logs and interpretive dashboards. With DAR, the platform can provide a verifiable record of the action and leave interpretation to the customer, auditor, regulator, or court.

Example events

payment_authorized refund_initiated access_granted config_applied workflow_approved

Back to hub

Action Domains → #nonrepudiation