Crypto Backtest Data Workbench
Freeze venue history, token membership, product terms and causal data joins. A current crypto directory does not define the universe available in the past.
Your evidence states are not a provider score, audit opinion or performance finding.

Primary reference documents
References support source definitions and mechanisms, not a completed review, measured return or endorsement. The questions are this publication's editorial record design.
Make each reference identify its vintage
The original ten-field workbench records evidence state, reference and notes. A real reference should name venue, product family, historical membership interval, dataset identity and access rights. Preserve source event time separately from availability and account receipt. Current metadata can document present syntax but cannot settle past eligibility. A note that quotes a vendor feature is not a complete historical source. The form's documented count measures the entered record state only, not actual verification, profitable research or deployed production. No field turns a missing crypto archive into an independently validated model.
Bring the outage and settlement packets as exercises
The new JSON packets can illustrate unit and state mistakes without serving as genuine inputs to a financial study. Their prices, costs and relative incident steps are invented. Keep that classification beside every imported note. Actual fill, order and account evidence needs original authentic records with selected contract and quantity scope. A cancelled remainder does not certify a closed position, and a coin valuation is not an executed cash conversion. The workbench remains a source checklist rather than an order reconciler or backtesting engine. It stores no production credential and owns no live data refresh.
Completion remains a separate research obligation
A genuine instrument task goes through the canonical factory and independent master, including the correct asset-class integration. Entry identity is frozen before one selected exit and its financial checks. A component checklist or software pass cannot replace that completion. Missing evidence remains unresolved even if all notes are neatly filled. JSON import identity checks and formula-safe CSV support document handling, not economic certification. Public hosting is managed-cloud owned, with no personal-computer fallback. TODO(Darren): supply licensed eligible crypto data and authentic account scope before any stronger strategy, provider or deployment claim is made.