1. Content stays in your own system
The integration computes fingerprints of sensitive inputs, outputs, tool arguments and results locally. By design, Azalee only receives these fingerprints and safe control metadata.
2. Real state transitions are sent as events
A normal interaction consists of related lifecycle events: started, model response completed or failed, output delivered or blocked, and interaction completed or failed.
3. Session and hash chain create continuity
session_id, correlation_id, sequence and optionally previousHash order the events. Removing, inserting or replacing a chain link becomes detectable.
4. Merkle batches condense many events
Event hashes are combined into a Merkle root. An inclusion proof can later show that a specific event hash was part of the published batch, without revealing other events.
5. A timestamp binds the batch to a point in time
An RFC 3161 or other supported timestamp binds the cryptographic value to a point in time. A qualified eIDAS status is only stated when the specific trust service provider is verified and activated.
6. Verify answers the specific technical question
| Proof type | Confirms | Does not automatically confirm |
|---|---|---|
| Audit PDF | Byte-identical hash against the stored export receipt | Correctness of every statement in the PDF |
| Event proof | Event hash was part of the published Merkle batch | Truth or permissibility of the action |
| Batch anchor | Merkle root and timestamp were published | Inclusion of a specific event without a proof |
| Contract badge | Current technical validation status of the displayed version | Official certification or a guarantee for every model reply |
7. Exports stay with the user
Audit PDF, CSV, graph, manifest and evidence ZIP can be exported for technical review. Verifiability depends on originals, local fingerprint rules and relevant system records being preserved.