AUDITEDTRADER / STATEMENT RECONSTRUCTION
Chain of Custody and Redacted Trading Statements
Preserve exact files while making privacy and source provenance explicit.
Separate acquisition from integrity
A digest can identify exact bytes for a later comparison. It cannot establish where those bytes came from. Record acquisition method, issuer, date, account scope and the untouched original independently from the hash. A matching digest can preserve an incorrectly labelled file just as faithfully as a genuine export.
The browser workbench performs local SHA-256 hashing. It does not contact a broker, verify account ownership or create a trusted historical timestamp. A filename is a user label, not evidence of provenance or the period described by the file.
Hash originals and derived copies separately
Redaction, spreadsheet conversion and changing line endings can change the byte sequence. The redacted or normalized copy should have its own digest and a documented relationship to the original. Do not describe different versions as byte-identical because their visible totals agree.
The teaching packet includes a small authored text fixture and a byte-changed version for software integrity checks. Neither is a broker statement. Their purpose is to demonstrate that a matching algorithm output says something about bytes, not about financial authenticity.
Retain access and transformation records
A custody log should state who handled which version, which fields were transformed and what was preserved under controlled access. Public exhibits can redact sensitive details while a properly authorised reviewer sees the necessary private mapping.
If redaction prevents joining accounts or dates, that limit belongs in the conclusion. Privacy and evidence scope are related but distinct. A public chart without names may still reveal sensitive holdings, so do not assume that removing an account number resolves every privacy concern.
Do not infer historical time from a local digest
Hashing a file today does not prove it existed before a trade outcome. A trusted timing claim requires the applicable proof and exact payload. A computer clock displayed next to the digest is not an independently authenticated anchor.
The workbench never labels a local calculation as a completed OpenTimestamps attestation. Actual proof verification is a separate workflow. No authentic signal payload and proof pair has been tested in this release, and an invented fixture cannot stand in for that missing pair.
Distinguish committed fields from uncommitted fields
A signal commitment covers the exact payload supplied to its hash rule. Fields excluded from that payload are not protected merely because another website displays them nearby. The supplied VR2 format names a limited set of fields; it does not include stop, target, quantity or actual fills.
A later timing proof cannot independently establish a complete trade population or customer arrival. Those claims need different records. Keep submission, completed anchor and subscriber delivery time separate when inspecting an actual production evidence package.
Publish an integrity conclusion only
An appropriate digest conclusion says that a specified byte sequence produced a specified hash under the named algorithm. It does not say a broker endorsed the file or its performance was audited. Preserve filename, size and input-version labels with that narrow conclusion.
The source dossier remains a separate record of provenance and assurance questions. A reader can reproduce the educational hash fixture without receiving confidential account material. That usefulness does not justify attaching an independent audit certificate to a historical personal or model claim.
Original reference material
Checked 14 October 2026 for its identified technical or reporting scope. These references do not certify this publication, its teaching examples or any private account.
Inspect the corresponding complete records
The authored packet provides every monetary input and its expected output, individual movement categories and document states. Preserve the declared convention when reproducing it. Do not replace an unknown source or a missing interval with an assumed zero. Financial evidence and software fixture counts remain separate.
Complete teaching packet | Original ten-field source dossier