Verification
A signed, tamper-evident receipt for every action an agent takes. Logs can be edited. Receipts can't be forged.
What it does
- Issues a cryptographically signed receipt after every agent action
- Receipts include: action type, timestamp, agent public key, input hash, output hash
- Signed with the agent's ERC-8004 identity keypair
- Any party with the agent's public key can independently verify the receipt
- Receipts are stored locally and can be exported for audit or compliance purposes
What a receipt proves
A Verification receipt proves three things: that a specific agent took a specific action, at a specific time, and that the output hasn't been altered since. If the receipt verifies, the action happened exactly as recorded. If it doesn't, something changed.
Audit and compliance use
Receipts are the answer to "prove it". If an agent is claimed to have acted outside its authority, the receipts show the exact sequence of actions taken and the policy state at the time. Receipts from compliant actions and blocked actions are both recorded. The full picture is available.
How it fits in
Verification is the final layer in every KOGENT action. After Rules approves, after the skill executes, Verification seals the result. The receipt is the permanent record that ties the action to the agent's identity and the moment it happened.