Sample output
What a Proof Harbour pack preview looks like
Proof Harbour is designed around controlled, reviewable outputs. This page shows a fictional preview of the kind of structure a client should expect.
This is not a live client file. It is not a template. It is not a checklist for self-production. It shows the shape of a controlled evidence pack without publishing the full method.
Why this is not a generic AI output
AI drafts text. Proof Harbour is being built around a controlled evidence process: scope, payment gate, matter reference, secure evidence route, evidence log, redaction discipline, human approval, and retention review.
The value sits in the controlled process and reviewer-ready structure, not in a single document written from a prompt.
Fictional example
Sample client: Alex
Alex holds a modest digital asset position and has one bank request. The case is fictional and uses no real wallet address, transaction ID, bank statement, exchange statement, or identity document.
Likely route
Bank and Lender Evidence Pack
Likely complexity
Simple one-wallet case
Evidence sources
One exchange and one wallet alias
Excluded from sample
No real client data
1. Scope extract
This preview shows the type of scope note that sits at the front of a pack. The real wording is confirmed after the client route, recipient, evidence position, and limits are reviewed.
Fictional extract
Purpose: support a bank review by setting out the evidence trail for one digital asset holding and one related funding path.
Boundary: this pack does not provide legal advice, tax advice, investment advice, custody, lending, broking, transaction execution, or wallet access support.
2. Evidence index extract
A pack should help a reviewer see what has been supplied, what it supports, and what remains outside scope.
| Ref | Fictional record | Purpose | Status |
|---|---|---|---|
| E-01 | Exchange account statement | Shows acquisition source | Requested after payment |
| E-02 | Wallet ownership proof | Links client to wallet alias | Controlled process |
| E-03 | Redacted movement summary | Explains flow at high level | Reviewer-ready extract |
| E-04 | Missing evidence note | Shows gaps and limits | Open item |
3. Narrative extract
A pack should turn evidence into a clear explanation. The narrative must stay tied to supplied records and must not invent missing facts.
Fictional extract
The available records indicate a simple acquisition and holding pattern. The supporting evidence is organised by source, wallet alias, movement summary, and gap note. No unrelated wallets or unrelated balances are included in this preview.
4. Missing evidence extract
Missing evidence is not hidden. It is recorded so the client and reviewer understand what has not been proved.
- Exchange statement period needs to cover the full acquisition window.
- Wallet ownership proof needs to match the wallet alias used in the pack.
- Bank-facing summary needs final approval before external issue.
5. Redaction and privacy controls
Proof Harbour is built around minimal disclosure. A pack should show the evidence needed for the stated purpose without exposing unrelated wallets, unrelated balances, or access material.
Shown where needed
Fictional wallet alias, evidence source, purpose, scope, and review status.
Not accepted
Private keys, seed phrases, recovery material, wallet passwords, bank logins, or files that give control over funds.
6. Review and approval point
Draft outputs are reviewed before use. Final issue requires human approval and a controlled release record.
Fictional approval note
Draft reviewed against scope, evidence index, missing evidence note, privacy boundary, and external issue purpose.
The public sample is deliberately limited
The full method is not published here. Proof Harbour does not publish complete templates, full evidence request lists, internal scoring logic, or complete pack wording.
The aim is to show the standard and shape of the work while protecting the process that makes the output controlled and reviewable.
Register interest
Register interest in the planned free evidence checkup and product routes.
View proof standards
See the rules behind privacy, evidence, approval, and controlled release.