AI Governance Hub

Accountable evidence, not a black-box score

Turn AI approvals into a reviewable decision trail.

Record who was accountable by role, what was decided, which evidence supported it, which conditions apply and when review is due. Export a portable JSON bundle whose SHA-256 chain can be verified locally.

Important boundary: hash-chained means tamper-evident when verified—not immutable, notarized or digitally signed. This governance log does not replace technical system logs, legal review or an enterprise record-retention system.
0Records
0Conditions open
0Reviews due
EmptyChain state

Add a governance decision

Privacy: records stay only in this tab until you download them. Do not enter personal data, secrets, passwords, OTPs, customer content, medical data or confidential evidence. Use internal reference IDs.

Decision trail

No root hash

    No sealed decisions yet. Add the first accountable record.

    Verify an exported decision log

    Select a JSON bundle produced by this page. Verification happens locally; the file is not uploaded. Maximum file size: 512 KB.

    What this evidence proves—and what it does not

    Useful evidence

    • Ordered governance decisions and review dates
    • Accountable organizational role
    • Referenced evidence and open conditions
    • Detectable changes to an exported chain

    Not proven

    • Identity of the person who entered a record
    • Authenticity or quality of referenced evidence
    • Trusted timestamp, signature or immutable retention
    • Technical AI events, outcomes or control effectiveness

    Framework orientation: the EU AI Act addresses technical record-keeping for high-risk systems, while the NIST AI RMF Govern playbook addresses documented roles and responsibilities. This tool is not a compliance determination.

    Frequently asked questions

    Can someone recalculate the chain after changing every record?

    Yes. This is an integrity check, not authentication. A trusted signature, timestamp or controlled record system is required to prove who created the log and when.

    Why can I not edit one sealed record?

    Editing would silently rewrite history. Correct a mistake by adding a new superseding decision, or reset the entire unsaved in-memory draft.

    Does the CSV include the integrity chain?

    It includes each record hash for review, but JSON is the canonical verifiable bundle. Spreadsheet exports may alter formatting.