A completed simulation is the moment to document what was tested. The purpose of a Blueprint Draft is archival: it creates a Compliance Artifact and Auditable Record of parameters, indicator weightings, and configuration DNA so the exact setup can be reviewed later.
Run the simulation and review the recorded snapshot for that exact moment in time. This step documents the parameter set that produced the historical output without turning the run into a forward-looking claim.
Save a Blueprint Draft to create a Compliance Artifact containing the exact settings, auditable parameters, and configuration DNA used in that simulation.
When the strategy is reviewed again, use the archived Blueprint Draft as the Auditable Record. Re-validation is about checking whether the current configuration still matches the stored record before any later review or operational step.
Launch BitThor to run a simulation and save the matching Blueprint Draft, or review the audit-trail terminology before you archive the next configuration snapshot.
Start In BitThor Review Audit Trail SignalsThis page and the Blueprint Draft feature describe the archival process only. A saved Blueprint Draft is a Compliance Artifact and immutable record of parameters, indicator settings, and configuration DNA; it is not a rating, approval, forecast, or recommendation.
Simulation outputs are based on historical data, platform state, and user-selected inputs. They are purely hypothetical, do not predict future performance, and do not guarantee any outcome. Past performance does not guarantee future results.
Cryptocurrency trading involves substantial risk of loss, including loss of principal. BitThor provides software tools only and does not provide investment advice.