A log is not a receipt.

What HELM proves that logs, gateways, and identity do not.

Most tools tell you an action happened. HELM decides whether it may happen, and leaves proof you can check yourself.

Audit log vs HELM receipt

Capability	Audit log or gateway	HELM receipt
Evidence it leaves	A log line or dashboard row	A signed receipt bound to the effect
Verifiable offline	No — tied to the vendor console	Yes — anyone can check it without us
Tamper-evident	Usually editable after the fact	A content hash detects any change
Failure mode	Fail-open: records what happened	Fail-closed: no verdict, no execution
What it records	That traffic moved	Whether the action was authorized under policy

Agent frameworks: They decide what an agent should attempt. HELM decides whether the side effect may run, and records a signed receipt.
Gateways: They route and observe tool and MCP traffic. HELM decides whether the side effect may run, and records a signed receipt.
Identity: They prove who or what is acting. HELM decides whether the side effect may run, and records a signed receipt.
Observability: They reconstruct what happened from logs and traces. HELM decides whether the side effect may run, and records a signed receipt.
Governance & risk: They organize policy and compliance records. HELM decides whether the side effect may run, and records a signed receipt.