How to verify history

Last updated: September 20, 2026

Each trading day’s BuyTrend-On / BuyTrend-Run / BuyTrend-Off list is sealed with a SHA-256 checksum in a daily ledger. If you want to confirm a download was not altered, compare the sealed file for that as-of date to its checksum. The seal timestamp shows when that day’s list was recorded.

Live publishing since 2026-09-14. Earlier sessions are sealed reconstructions under the same BuyTrend-On / BuyTrend-Run / BuyTrend-Off rule.

Off reasons in the download

BuyTrend-Off rows carry reason: psi20_trail (organic trail), roster_drop (left the momentum roster while long), or insufficient_tape (no admissible session tape while long). See How it Works for how to treat forced exits in evaluation.

`publication_kind`

History CSV/JSON includes publication_kind: live or reconstructed. Same signal language throughout; the column is for code that needs provenance.

Steps

Download Complete signal history (CSV or JSON) from your account.
Email support@tapesight.com and ask for the sealed files for as-of date T: public_signals.json and manifest.json.
Hash the public file and confirm it matches manifest.files["public_signals.json"].
Confirm your download’s rows for T match that public file.

shasum -a 256 public_signals.json

Use support@tapesight.com for sealed-file and verify requests (not hello@tapesight.com). Include the as-of date(s) you want.