A record nobody can quietly change.

Every action your agents take is written to a chained record the moment it happens. Change a line, remove one or reorder them, and the chain shows it. Hand an auditor the export and they can check it themselves, offline.

Book a demoSee the controls at work

An illustration of a decision trace with made-up names. Eight events record a credit limit rise approved by a person. Each event carries the hash of the one before it. If the amount is changed or the approval is removed, the printed record still looks normal, but the hash chain breaks at that point and the seal fails.

Decision traceDENV_01M1YQV8
  1. 09:41:07Openedcredit-agent, for Lena Lindqvist
  2. 09:41:07Identity verifiedLena Lindqvist, by Okta
  3. 09:41:07Sensitive data handled2 values tokenized
  4. 09:41:07Policy evaluatedTiered Approval v3: ask a person
  5. 09:41:07Exception raisedCredit Risk, in Teams
  6. 09:42:31ApprovedTomás Ruiz, Credit Risk
  7. 09:42:32Write performedCredit limit ••4821 set to €15,000
  8. 09:42:32FinalizedAllowed by a person
8 eventsAllowed by a person
Try to change the record:

Move the lamp over the record. Illustrative names and hashes.

Every decision, connected. None of them editable.

Traces are kept in DecisionDB, a database built for one job: recording decisions. It links each one to the people, agents, policies and data it involved, so you can follow any thread, from one approval to every decision that policy ever touched.

  • Browse it as a graph. Start anywhere and step to what’s connected.
  • Immutable by design. Records are only ever added, and each one is sealed when it closes.
  • Yours, in your network. Each tenant stored apart, encrypted at rest if you choose.
DecisionDB
acted foracted bychecked againsttouchedapproved bypart ofmatches
Credit limit raised••4821 to €15,000 · approved
Credit limit raised••4821 to €15,000 · approved
  • acted for
  • acted by
  • checked against
  • touched
  • approved by
  • part of
  • matches
Sealed when it closed. Nothing about it can be edited, only added to.Click any node · illustrative records

Proof the controls actually ran.

A switch that says “on” isn’t proof. TraceMem checks every control you’ve switched on against what the trace actually saw. One that’s on but has gone quiet is flagged as silent, the tell-tale sign of traffic going around it.

Events in the trace, last 6 hours
  • Verified IdentityOn
  • PII ProtectionOn
  • Governed Data AccessOn
  • Model GatewayOnSilent: switched on, no calls in 6 hours
  • Policy and ExceptionsOn
6 hours ago3 hours agonow

All five controls are switched on. Over the last six hours, Verified Identity, PII Protection, Governed Data Access and Policy and Exceptions all wrote events to the trace. The Model Gateway wrote none, so it is flagged as silent.

Each tick is activity a control wrote to the trace. Point at a lane for its count. Illustrative data.

Ask us the hardest question your auditor asks, and watch one record answer it.

Book a demoHow it fits together