Sample output
A fictional Bank and Lender Evidence Pack preview
This page shows the public shape of a Bank and Lender Evidence Pack for reviewer questions involving digital assets, tokenised assets, wallets, exchanges, and company records.
It is not a live client file, reusable template, self-production checklist, or substitute for a scoped and human-reviewed matter.
Fictional preview
No client data · Not a template · Not for reliance
Every person, organisation, wallet alias, record, and extract on this page is fictional. The page demonstrates structure only and does not disclose the full method, evidence-request logic, scoring, or final bank-facing wording.
Canonical pack shape
Nine sections a reviewer can navigate
This is the public map of the Bank and Lender Evidence Pack. The selected fictional extracts below illustrate parts of the structure without publishing a complete template.
Reviewer can understand
What the records support, which gaps remain, what is outside scope, and whether the pack is ready for human review.
Private by design
Unrelated wallets, balances, identities, documents, and access material stay outside the public preview and the scoped pack.
Human reviewed
Draft support does not become an external output until scope, evidence, gaps, privacy, and release status are approved.
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.
Tokenised assets and new financial rails
The same output discipline applies to tokenised asset questions
Tokenised asset matters can create reviewer questions about records, governance, custody context, settlement trail, rights, issuer documents, collateral, fund interests, securities, protocol activity, or digital-rail activity. Proof Harbour’s public sample does not publish the full method for handling those questions.
The role shown here is evidence readiness and reviewer context: scope, limits, evidence index, missing-evidence note, redaction discipline, approval point, and clear boundaries.
Proof Harbour does not issue tokens, advise on token structure, promote investments, arrange lending, provide custody, recommend protocols, move assets, execute transactions, or verify the investment value, suitability, or regulatory status of a token.
Fictional examples
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
Sample organisation: Mira Ltd
Mira Ltd is a fictional company with a tokenised asset and digital-rail question for a board, lender, or compliance reviewer. The case uses no real company, token contract address, wallet address, transaction ID, issuer document, subscription document, offering document, or legal opinion.
Likely route
Tokenised asset or protocol scoping
Likely complexity
Scoping-first
Reviewer context
Governance, records, rights, and boundary explanation
Excluded from sample
No token issuance or token-structure advice
Selected extract: Cover memo
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, lender, adviser, board, company, KYB, or compliance review by setting out the evidence position for a defined digital asset or tokenised asset question.
Boundary: this pack does not provide legal advice, tax advice, investment advice, token issuance, token-structure advice, financial promotion, custody, lending, broking, protocol recommendation, transaction execution, or wallet access support.
Selected extract: Evidence index
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 or platform account statement | Shows acquisition source | Requested after payment |
| E-02 | Wallet ownership proof | Links client to wallet alias | Controlled process |
| E-03 | Tokenised asset or digital-rail record summary | Explains high-level reviewer context | Scoping-first extract |
| E-04 | Redacted movement summary | Explains flow at high level | Reviewer-ready extract |
| E-05 | Missing evidence note | Shows gaps and limits | Open item |
This is a fictional index extract only. It is not a full evidence request list.
Selected extract: Source-of-funds narrative
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 defined digital asset or tokenised asset evidence question for a stated reviewer purpose. The supporting material is organised by source, wallet or record alias, movement summary, governance context, boundary note, and gap note. Unrelated wallets, unrelated balances, and unrelated asset records are not included in this preview.
Selected extract: Exclusion note
A tokenised asset matter may need a reviewer to understand what kind of record exists, why it is relevant, what governance or documentation trail is available, and what Proof Harbour has not assessed.
Fictional extract
The tokenised asset context is treated as a scoping-first reviewer-readiness issue. The pack may describe the evidence position, governance trail, document boundary, and review limits. It does not confirm token value, token suitability, regulatory status, investment merit, or whether the token should be issued, bought, sold, held, lent, staked, bridged, collateralised, or transferred.
Selected extract: Missing or weak evidence list
Missing evidence is not hidden. It is recorded so the client and reviewer understand what has not been proved.
- Exchange or platform statement period needs to cover the relevant acquisition or movement window.
- Wallet ownership proof needs to match the wallet alias or record alias used in the pack.
- Tokenised asset or digital-rail documentation may need separate scoping before it is referenced in a reviewer-ready output.
- Bank-facing, lender-facing, board-facing, or KYB-facing summary needs final approval before external issue.
Selected extract: Redaction checklist
Proof Harbour is built around minimal disclosure. A pack should show the evidence needed for the stated purpose without exposing unrelated wallets, unrelated balances, unrelated entities, or access material.
Shown where needed
Fictional wallet alias, record alias, evidence source, reviewer purpose, scope, issue boundary, and review status.
Not accepted through public forms
Wallet addresses, transaction IDs, token contract addresses, issuer documents, subscription documents, offering documents, private files, bank statements, exchange statements, screenshots, ID documents, legal opinions, tax memos, or raw evidence.
Never accepted
Private keys, seed phrases, recovery material, wallet backups, wallet passwords, bank logins, exchange passwords, browser-wallet access details, or files that give control over funds, wallets, tokens, assets, or accounts.
Selected extract: Human review readiness status
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, tokenised asset or protocol boundary, and external issue purpose.
Status-only verification
Future paid final outputs are intended to be PDF-first, formal, version-controlled, and capable of status-only verification where that route is approved.
Fictional extract
Document status can be checked without exposing the document contents, client evidence, private matter folders, wallet data, transaction data, token contract data, payment status, or internal notes.
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, full pricing matrix, complete pack wording, exact tokenised asset review logic, or full bank-facing wording.
The aim is to show the standard and shape of the work while protecting the process that makes the output controlled and reviewable.
Fictional preview — not a template. Deliberately limited. Not for reliance, resale, reuse as a template, AI training, AI prompting, or third-party adaptation.
Important boundary
Proof Harbour does not provide legal advice, tax advice, investment advice, token issuance, token-structure advice, financial promotion, custody, lending, broking, protocol recommendation, transaction execution, wallet access, or regulated financial advice.
Proof Harbour focuses on structured evidence support, documentation, reviewable records, governance context, and privacy-conscious presentation.
Register interest
Use the public front door for high-level route finding only. Do not send evidence.
View proof standards
See the rules behind privacy, evidence, tokenisation, approval, and controlled release.
View the Evidence Pack
See the canonical service route, reviewer purpose, public boundaries, and nine-part pack structure.