⚠
Legacy Sentinel Extension Surface (v1.33.0). This walkthrough covers the browser extension audit lifecycle. For Enterprise CLI audit trail, see vai ci evidence --signed and the Enterprise Workspace.

audit lifecycle walkthrough · v1.33.0

From Prompt to Receipt

Step-by-step: how VerifAIer captures, analyzes, and receipts an AI interaction. Every stage runs locally in the browser. No data leaves the machine.

local-first no cloud runtime deterministic replay-safe

Select a scenario

Lifecycle Steps Select a scenario
Select a scenario above to begin.
Step Detail
◆ Press Next or D to begin the walkthrough
Generated Receipt SHA-256 · tamper-evident authoritative_for_wiw=false
Select a scenario above to view its receipt.

Governance Design Invariants

🔒
What Is NOT Stored

VerifAIer's audit vault never stores the raw prompt text or the raw AI response. Only the SHA-256 hashes are written: input_hash, result_hash, diagnostics_hash. The data cannot be reconstructed from the receipt alone, by design. Privacy is a structural guarantee, not a policy setting.

◆
Why authoritative_for_wiw=false

The field authoritative_for_wiw is hardcoded false in audit_receipt.js. It signals that a VerifAIer receipt is governance evidence, a tamper-evident record of what the rule engine detected, not a legal determination or authorization of the underlying interaction. Human reviewers make that judgment. The tool assists; it does not decide.

↻
Replay-Safe Semantics

replay_safe: true means that submitting the identical prompt again will produce the identical receipt_hash. The hash is a function of the content, not the time. This property allows compliance auditors to independently verify a receipt by replaying the interaction, without needing to trust VerifAIer's runtime state or any server.