All use cases
Tamper-evident audit trail

Answer "what did the agent know?" — provably

It's the first question in every AI incident review and every enterprise security questionnaire. A hash-chained, append-only log answers it — without trusting application logs that could have been edited after the fact.

Every eventwrite · read · block
Hash + linkchain to prior
Verifyrecompute chain
Replaywhat it knew
Every decision — including the ones that blocked an action — is written as a hash-chained event. Re-computing the chain from stored fields reveals any entry that was edited after the fact.

The risk

"What did the agent know when it did that?" is the first question in every AI incident review, every regulator inquiry, and every enterprise security questionnaire. If the answer lives in application logs that could have been edited after the fact, it isn't an answer a regulator or a customer will accept.

You need a record that's convincing precisely because it can't have been quietly rewritten to match the story you'd prefer to tell.

How Governed Memory handles it

  1. 01
    Every decision is an event

    Writes, reads, quarantines, policy checks, and blocked actions are all recorded — not just the happy path an application chose to log.

  2. 02
    Hash-chained and append-only

    Each entry carries a SHA-256 hash over its own contents and the entry before it. There's no in-place edit that leaves the chain consistent.

  3. 03
    Tampering is detectable

    Verification re-computes the chain from stored fields, so it catches an entry that was altered after it was written — not only one that was deleted.

  4. 04
    Replayable months later

    You can reconstruct exactly what the agent saw and why it acted, long after the fact, without trusting the application that produced the events.

Read the full technical walkthrough → Self-host it