Product · Verification

Evidence anyone can check, without trusting us.

Every record is Ed25519-signed and hash-chained. dh verify checks a whole session offline against a key you pinned. Witnesses countersign the chain, so rewriting history takes more than one stolen key.

Why it matters

The gap it closes

Logs are written by the system being audited, so auditors have no reason to trust them. Evidence has to be checkable by someone who doesn't trust the operator, including us.

What it does

Capabilities

Offline verification

dh verify checks signatures, order, hash links and completeness. It exits non-zero on any problem.

Catches the real attacks

Reordering, truncation, a dropped closing record, splicing, a forged record under the right key id, and an action with no outcome.

Pinned keys only

The public key comes from you, never from the records.

Witness quorum

Separate witness processes countersign the chain head. Require k of n, even before an action runs.

Public verifier

Check a chain in the browser at verify.decisionhorizon.dev.

SIEM export

Send records to your SIEM as OCSF or CEF, or to any OpenTelemetry collector as spans.

Get started

In practice

From the documentation.

dh verify ~/.dh/records/<session>.jsonl --pub ~/.dh/signer.key.pub
dh replay ~/.dh/records/<session>.jsonl --html replay.html --pub ~/.dh/signer.key.pub
Stated limits

What it doesn't do

  • Tamper-evident, not tamper-proof: an alteration is detected, not made impossible.
  • Witnesses countersign the chain, not its content. A key holder can still write a false record in real time.

See it on one of your own workflows.

We'll put Decision Horizon in front of a real agent workflow of yours and replay the record with you.