When auditors ask "who approved this and why?", most organisations scramble. They search email threads, check Slack messages, dig through shared drives, and piece together a narrative from fragments scattered across a dozen tools.
The decision ledger eliminates this problem entirely.
What is a decision ledger?
A decision ledger is an append-only, immutable record of every governance action taken within an organisation. Every time a decision passes through the Governax governance pipeline, a ledger entry is created automatically. This entry captures the complete context of the decision:
Append-only by design
The decision ledger is append-only. Once an entry is written, it cannot be modified or deleted. This is enforced at the database level, not just the application level. There is no admin override, no backdoor, no "edit decision" button.
Why is this important? Because audit integrity depends on it. If decision records can be modified after the fact, they lose their evidentiary value. An append-only ledger means that what was recorded at the time of the decision is exactly what auditors will see - no matter when they look.
Hash verification
Every ledger entry includes a cryptographic hash generated from the entry's contents. This hash serves as a tamper-detection mechanism. If any byte of the entry were changed, the hash would no longer match, immediately revealing the alteration.
For organisations subject to SOX compliance, financial audits, or regulatory examinations, this level of integrity is not optional - it is required.
Retention policies
Different types of decisions require different retention periods. Financial approvals might need to be retained for seven years. Routine access grants might only need one year. The decision ledger supports configurable retention policies:
Retention policies are attached to decision types, not individual entries. When a decision is recorded, the appropriate retention period is applied automatically based on the policy configuration.
Why this matters for compliance teams
Compliance teams spend a disproportionate amount of their time on one activity: reconstructing decision history. With a structured decision ledger, this reconstruction is unnecessary. Every decision is already recorded, with full context, in a format that auditors can query directly.
The shift from "audit difficulty" to "audit readiness" is not about adding more process. It is about having the right infrastructure in place so that every governance action produces a verifiable record automatically.