Replay artifact checksum inspector
Compare exact reference bytes. A match is not a strategy validation.
Identity is narrower than authenticity
The expected map names five exact objects from the completed synthetic replay. SHA-256 is applied to received bytes, not parsed JSON or a normalised CSV. A matching digest and length identify the same bytes as the public reference. They do not establish who produced a file, when it existed, whether the receipt is financially representative, whether the engine was independently rerun or whether a holdout remained unseen. A mismatch remains a useful comparison finding, not an automatic trading-system failure.
JSON spacing, key order, byte order marks and line-ending changes can produce a different digest. Preserve the original object before formatting or interpreting it. The comparison records expected and observed identities and the selected artifact kind. Choosing the wrong reference can yield a legitimate mismatch. No payload/proof pair, signature, calendar receipt or completed Bitcoin attestation is verified here. The record should not be promoted into a cryptographic timestamp claim.
A bounded browser operation
Selected local files are read in browser memory, with a one-megabyte limit. Empty, oversized or unreadable files leave no exportable result. The public reference command fetches only this edition's fixed local artifact path. There is no arbitrary URL fetch, broker connection, account lookup, upload endpoint, browser storage or production scheduler. The exported comparison contains no local pathname. Reset and reference changes invalidate outstanding asynchronous reads so an older result cannot quietly return.
The browser uses its native Web Crypto SHA-256 implementation. This is a byte-comparison tool, not another hand-written trading engine. The replay source, pinned engine settings, complete transaction population and independent software checks are separate objects. A reference hash loaded from this publication cannot on its own certify an independent third party or compensate for missing data rights. Reproduction belongs to the declared environment and source; financial validation belongs to the authorised research process.