What is your agent really doing?

Atested opens the black box. Atested requires that every action your AI takes has a reason to move forward and records all ALLOWs and DENYs.

Hallucinated a reason to delete that data file? Decided you just have to have a new Mac Mini? Not on Atested's watch. Have an edge case that genuinely needs to run? You approve it, once and done.

Every AI action is recorded

Atested logs but not like most apps log. Atested logs are append-only, signed, immutable, and always available for your inspection or export. One source of truth. When your agent reports success, the record either backs it up or it doesn't.

How the chain works

Action only with good reason

Atested reasons are the obvious kind. Is your AI trying to act outside of its scope? Does it have the authority to use this tool in this way? Questions like this are included in Atested so you don't write policy. No reinvention required. There are instances when Atested cannot classify an action. These are opaque operations and in these cases you decide if it runs. Atested makes this easy for you and it's one and done.

Atested checks the work, not the answer

Answer checking would be magical but, alas, it is beyond our abilities. Atested is just a governance proxy. No one can know whether the action your agent proposes is correct, and neither can Atested. But Atested can require your agent to specify why it thinks the action is correct. Atested does what you would do if you were looking over your agent's shoulder. What does the agent intend to do? Why does it think this is the right move? Atested applies the logic, and if the agent can't answer these basic questions, Atested denies the action. Your agent can reexamine its reasoning, stop being lazy, stop cutting corners, and do it right. Or not at all. Just the way you want it.

Chain record example
record_type:      mediated_decision
timestamp_utc:    2026-04-13T10:58:12Z
original_tool:    Bash
action_type:      write
target:           /Users/you/project/config.json
confidence_tier:  2
matched_rule:     write-source-allow
policy_decision:  ALLOW
record_hash:      sha256:918d0a03...
prev_record_hash: sha256:f3b2e1a8...
signature:        ed25519:c6179129...
signing_key_id:   ed25519:c6179129...

This is a typical chain record produced by Atested. Each record contains the hash from the preceding record enabling detection of a break in the chain. It is impossible to modify these records and you not know.