1
Request
A protected request was proposed
FusionWall records a fingerprint of the protected outbound view—not the original private values in this public example.
Synthetic receipt · browser walkthrough
See what FusionWall records—and what it does not.
This fictional example shows how one approved AI request becomes a private, linked receipt. It contains no customer information and is not an external audit opinion.
The receipt story
Five checkpoints explain the action.
2
Policy
The built-in floor was applied
The receipt identifies the active policy decision and whether stronger customer rules also participated.
3
Approval
A person chose to proceed
The action records that the exact protected view passed the human checkpoint before the provider call.
4
Outcome
The provider call completed
Provider, model, route profile, request count, outcome status, and response fingerprint are preserved.
5
Chain
The event linked to prior evidence
The receipt carries its preceding event hash and its own event hash so later chain changes can be detected locally.
Readable evidence
The important fields, grouped by purpose.
Who and what
- Actor role
- Owner
- Action
- Governed AI turn completed
- Recorded at
- 2026-08-31 · synthetic
Where it went
- Provider
- Example provider
- Model
- Example model
- Route
- Pinned provider profile
Why it could proceed
- Decision
- Allow after human approval
- Safety floor
- Applied
- Human review
- Exact outbound view reviewed
What protection recorded
- Categories
- Email, account, custom term
- Raw values in receipt
- No
- Restoration
- Performed locally
What this proves
Useful local evidence—not magic.
Helps establish
A visible sequence of decisions
- Which protected request fingerprint was approved
- Which provider, route, model, and policy were selected
- Whether the provider call completed
- How this event linked to the preceding local receipt
Does not establish
An external or absolute guarantee
- That detection found every sensitive value
- That the provider followed obligations outside FusionWall
- That a full local administrator could never replace state
- That a regulator, auditor, or third party certified the event
Show technical detail
The sample represents a locally stored receipt with action metadata, provider and model identifiers, policy hashes, protection categories, protected-request and response fingerprints, outcome state, previous-event hash, and event hash.
Fingerprints support comparison without publishing the underlying protected request or restored response here. The linked chain is locally tamper-evident; external notarization is not included.
Continue the review
Put the receipt back into context.
See how the request crossed the boundary or return to the complete Trust Center.