20 minutes · risk, model risk, audit

See a governed AI action stopped — then verify the proof yourself

This is a working session, not a slide deck. In twenty minutes you see an AI action refused before it executes, the signed record that refusal produces, and that record verified on your own machine with published tooling. The technical sequence takes about three seconds; the rest is your questions.

What we do with the time

  1. 00–02Where second-line coverage stops when the model takes the action rather than scoring it.
  2. 02–08An AI action is attempted. CoreGuard evaluates it against policy before execution.
  3. 08–14The action is refused, and a signed decision record is produced for that refusal.
  4. 14–17You verify the record yourself — offline, with published tooling, nothing calling back to us. We then alter one field and show verification fail.
  5. 17–20What this would mean for your model-risk, audit and examiner workflow, and what a first engagement would scope.

Request the session

We reply within one business day with times. Tell us the workflow you have in mind and who should be in the room — typically a risk or model-risk owner, plus whoever runs the AI system.

Prefer to look first, with nobody on the call? Verify a real production decision at /verify, or run all fifteen attacks against a governed agent at /authority-lab. Both are public and need nothing from us.