The integrity of a forensic engagement is determined before the trace begins — in the discipline of documentation.
Every artifact — TXID, screenshot, derivation step — is logged, hashed, and timestamped. A reviewer should be able to reconstruct our reasoning without speaking to us.
Heuristic outputs are documented with inputs, versions, and thresholds. A second analyst running the same pipeline should arrive at the same conclusion.
A report is read by an exchange compliance officer, a police unit, a lawyer or a court, and it is structured for those four. Formatting requirements differ by jurisdiction; the lawyer running the proceedings is the one who states them.
A cluster is named when the evidence names it, and left unnamed when it does not. What the chain shows and what we infer from it are marked as two different things.
Jurisdiction identified. Evidentiary standard selected. Chain-of-custody template opened. All inputs hashed on receipt.
On-chain trace executed with full logging. Heuristic thresholds, clustering rules, and attribution sources all documented in-line.
Primary report, technical appendix, methodology note, and hash-verified evidence bundle, prepared for the exchange, the police unit and the lawyer who will use them.
The material goes to the partner lawyers admitted in the jurisdiction, who run the proceedings. StarCompliance does not practise law; it answers their questions about the analysis for as long as the case runs.
Response within two business hours. Confidential. Success-fee terms on recovery work.