Family offices / illustrative evidence record

Source-of-funds declaration.
A history you can follow.

The declaration, requested documents and human review history remain in one restricted project.

Fictional process, people and events. This is an explanatory example, not a production evidence pack or a prescribed legal checklist.

The later questionWhich declaration was signed, and what clarification was requested before it?
Follow the sequence below, then inspect the document reference and review limits. This is a fictional explanatory record.
The missing context

A declaration and its supporting records sit in separate inboxes when the review is reopened.

The connected record

The declaration, requested documents and human review history remain in one restricted project.

Lindqvist Family Office

Follow the work.
Inspect its record.

Times below are fictional and shown in UTC. A record distinguishes a request, an uploaded file and a person's explicit response.

01

Manager requests declaration

Relationship Manager · 2026-09-28T09:15:00Z · Source-of-funds declaration v2

Recorded
02

Client uploads supporting documents

Family Representative · 2026-09-28T10:15:00Z · Source-of-funds declaration v2

Recorded
03

Reviewer asks for clarification

Compliance Reviewer · 2026-09-28T11:15:00Z · Source-of-funds declaration v2

Recorded
04

Client signs declaration v2

Family Representative · 2026-09-28T12:15:00Z · Source-of-funds declaration v2

Recorded
05

Reviewer records follow-up decision

Compliance Reviewer · 2026-09-28T13:15:00Z · Source-of-funds declaration v2

Recorded
06

Next review assigned

Relationship Manager · 2026-09-28T14:15:00Z · Source-of-funds declaration v2

Recorded
What a reviewer checks

The event is only
part of the evidence.

A production export needs its covered documents, participant and credential references, event hashes, pack signature and timestamp material where required. Device and network context are supporting data, not proof of identity on their own.

Check the protected record

Recompute the covered hashes. Verify the signature against an independently trusted key. Validate the timestamp token and its trust chain. Confirm the export's scope and any missing material.

Try the separate cryptographic demo ↗

This industry example has no cryptographic seal. The linked Maritime demo separately demonstrates protected-content verification with clearly stated limits.