{
  "checked": "2026-10-08",
  "site": {
    "code": "BATS",
    "name": "Build A Trading System",
    "project": "buildatradingsystem",
    "domain": "https://buildatradingsystem.pages.dev",
    "theme": "system",
    "lede": "Build a trading system from a falsifiable hypothesis, causal data, explicit execution rules and a reproducible research record.",
    "library": "guides/index.html",
    "dataset": "data/system.jsonld",
    "scope": "Educational research design and invented arithmetic examples. No strategy returns, broker execution or production certification are supplied.",
    "home": [
      [
        "Start with an experiment, not a curve",
        "Write down the behaviour you expect, the observations that could contradict it and the market in which the hypothesis applies. Then declare the signal clock, data availability and order lifecycle. A finished-looking equity curve cannot repair an experiment whose decision rules were chosen after seeing its outcome."
      ],
      [
        "Separate rules from evidence",
        "A complete rule sheet is a specification. A passing unit test establishes a software behaviour. A historical replay estimates an outcome under assumptions. A forward account observes a different environment. Keep those stages labelled so evidence from one is not silently promoted into proof of the next."
      ],
      [
        "Make the next test reproducible",
        "Save the data identity, code version, parameters, decision timestamps, costs and rejection rules together. The research guides cover frozen holdouts, execution assumptions and recovery procedures. The worksheet below examines how costs change a two-outcome expectancy example; it does not discover an edge."
      ]
    ],
    "method": [
      [
        "Hypothesis before optimisation",
        "Describe the cause, expected effect and observable alternative explanation. Decide which experiments can reject the idea before searching for parameters. Record every material research choice, including unsuccessful runs; the best final curve is not the whole research population."
      ],
      [
        "Evidence layers stay separate",
        "Unit tests, historical simulation, out-of-sample research, paper execution and actual account records answer different questions. Software correctness does not establish an independent trading sample. A simulation can be useful while still excluding queues, impact, gaps or unavailable historical features."
      ],
      [
        "Reproducibility before promotion",
        "Keep a run manifest with code, data, environment and policies. Require a second reconstruction of the chosen candidate and a documented operational review before considering real deployment. The examples on this site do not certify a model or authorise live trading."
      ],
      [
        "Publishing boundary",
        "Provider descriptions are adjacent-tool assessments based on public documentation, not independently audited subscriptions. The owner states legal independent ownership; commercial arrangements have not been independently reviewed. The publication does not supply an automatic winner or a fabricated research return."
      ]
    ],
    "sources": [
      [
        "QuantConnect: hypothesis, overfitting and out-of-sample research",
        "https://www.quantconnect.com/docs/v2/cloud-platform/backtesting/research-guide"
      ],
      [
        "QuantConnect: slippage models",
        "https://www.quantconnect.com/docs/v2/writing-algorithms/reality-modeling/slippage/key-concepts"
      ],
      [
        "QuantConnect: live/backtest reconciliation",
        "https://www.quantconnect.com/docs/v2/writing-algorithms/live-trading/reconciliation"
      ]
    ],
    "tool": {
      "path": "tools/trading-system-expectancy-cost.html",
      "kind": "expectancy",
      "title": "Trading-system expectancy after costs",
      "description": "Explore a fixed two-outcome R-multiple example. Inputs are assumptions, not an estimated trading edge.",
      "fields": [
        [
          "winPct",
          "Assumed win rate (%)",
          45
        ],
        [
          "winR",
          "Average winning outcome (R)",
          2
        ],
        [
          "lossR",
          "Average losing magnitude (R)",
          1
        ],
        [
          "costR",
          "Additional average cost (R)",
          0.1
        ]
      ],
      "notes": [
        [
          "A deliberately simple distribution",
          "Expected R equals win probability times average winning R, minus loss probability times average losing magnitude, minus additional average cost. This assumes only wins and losses, with cost entered separately. If the averages already include that cost, leave the extra cost at zero rather than charging twice."
        ],
        [
          "Not a risk-of-ruin model",
          "The worksheet has no serial dependence, changing risk size, tail events, scratches, capacity or estimation uncertainty. A positive assumed mean is not evidence of a profitable strategy. Its break-even rate only solves the entered two-outcome equation; it does not tell you how many observations establish an edge."
        ]
      ]
    }
  },
  "guides": [
    {
      "path": "guides/trading-system-data-availability-contract.html",
      "title": "Write a trading-system data-availability contract",
      "description": "Define what each feature could know at decision time before running the backtest.",
      "sections": [
        [
          "Inventory the observation rather than the column name",
          "For each feature record its source, instrument identity, timezone, observation timestamp, publication timestamp, revision policy and the time at which a strategy can first consume it. A historical file containing a value does not mean that value was available at the trade decision.\n\nA bar stamped at its opening time still contains a high, low and close formed over the following interval. A macro series may later be revised. A company universe may reflect today's surviving members. Each produces a different availability problem that a train/test split alone cannot repair."
        ],
        [
          "Declare the decision boundary",
          "Specify whether the model evaluates after a completed bar, on a quote event or at a scheduled clock. A condition based on the completed close cannot generally fill at an earlier price inside the same bar. If an auction or special order is part of the premise, document its submission deadline and available information separately.\n\nKeep signal time, intended order time and assumed fill time as different fields. Test equality boundaries explicitly: a source published at the decision timestamp may still require a delivery or processing delay. Use a conservative documented rule instead of an implicit join that makes every datum immediately available."
        ],
        [
          "Freeze identities and transformation rules",
          "Save symbol mappings, contract identifiers, corporate actions, normalization mode and universe membership as of each historical point. Do not substitute a current ticker list for a point-in-time universe. A dataset with only surviving assets cannot support claims about the assets that disappeared.\n\nTransformations need their own availability rules. Rolling statistics must use the intended past window, fitted scalers cannot learn from future periods and missing values must not be filled with later observations. Keep warmup observations distinct from the dates on which outcomes are evaluated."
        ],
        [
          "Run adversarial timing checks",
          "Shift a feature one step later and inspect whether impossible early signals disappear. Test a missing release, a delayed release, a duplicated observation and a timezone transition. A strategy should not silently turn stale data into a fresh event. Record the exact behaviour in a small deterministic test.\n\nThese are software and data-integrity checks, not independent return-validation samples. Passing them supports the stated timing contract. It does not establish that the economic hypothesis will survive another period."
        ],
        [
          "Publish a usable contract",
          "A compact contract names each feature, earliest usable time, source vintage, missing-data behaviour, transformation scope and relevant test. Put code and data identities beside it. Someone reconstructing the run should not need to guess whether the time column refers to bar start, bar end or publication.\n\nIf the source cannot supply historical vintages, preserve that limitation. Do not replace the missing source with a plausible synthetic history and present it as observed evidence. Synthetic fixtures belong in labelled software tests only."
        ]
      ]
    },
    {
      "path": "guides/trading-system-frozen-holdout-and-change-log.html",
      "title": "Frozen holdouts and the trading research change log",
      "description": "Keep selection decisions, rejected candidates and untouched evaluation periods auditable.",
      "sections": [
        [
          "Define what is being selected",
          "List the hypothesis family, candidate rules, parameter bounds, input transformations and selection objective before evaluating the reserved period. A search over entry thresholds, exits, universes and reporting windows is larger than a search over entry thresholds alone. Record the real choice set.\n\nSeparate economic ranking from software tests. A candidate that crashes should fail correctness checks. That does not make a test fixture an independent market period or demonstrate that a surviving strategy has an edge."
        ],
        [
          "Give periods one declared job",
          "Use historical development data to build the candidate and a reserved interval to evaluate the frozen choice. State how warmup crosses boundaries and how positions already open at a boundary are handled. Overlapping labels or holding periods can leak information even when rows are assigned different dates.\n\nThere is no universal percentage split or ideal sample size for every market. Dependence, horizon, regime coverage and the number of research decisions matter. Explain the actual design rather than attaching confidence to a convenient calendar division."
        ],
        [
          "Freeze the candidate identity",
          "Save code revision, full parameters, feature definitions, data identities, entry convention, exit policy, costs and acceptance rules. A short model nickname is not enough. Re-running with a corrected timezone or a new exit produces a different experiment even if the nickname stays the same.\n\nHashing a manifest can identify its bytes; it cannot establish that the declared holdout was never viewed. Research access and decision logs supply a different kind of evidence. Keep those claims distinct."
        ],
        [
          "Record failure without reopening the tournament",
          "A failed reserved test is information. Do not repeatedly adjust the candidate against that same interval while continuing to call it untouched. A new hypothesis can be researched, but its exposure to previous results must be acknowledged and its next evaluation designed accordingly.\n\nLog discarded candidates and the reason for each change. A final report that shows only the winning specification hides selection risk. QuantConnect's research guide discusses overfitting and reserved evaluation; this site's manifest checklist is an editorial implementation of that concern, not a statistical certification."
        ],
        [
          "Make the decision trace readable",
          "For each experiment keep a question, predeclared settings, data period, result, known defects and next action. A bug fix may invalidate the original result, while a failed economic hypothesis may remain a valid negative finding. Do not merge those outcomes into a single attractive chart.\n\nBefore any operational use, reproduce the frozen candidate and compare orders with the intended policy. A verified no-deployment decision is preferable to promoting a model whose evidence cannot be reconstructed."
        ],
        [
          "Keep access history beside the manifest",
          "Record when each reserved result first became visible and which decisions had already been frozen. A file hash alone cannot establish that a researcher never viewed a period. Access records and a decision log provide a different evidential layer. If the history is incomplete, describe the evaluation as exposed or uncertain rather than silently restoring the untouched label."
        ]
      ]
    },
    {
      "path": "guides/trading-system-order-state-and-recovery.html",
      "title": "Trading-system order state and recovery checklist",
      "description": "Design idempotency, partial fills, stale signals and restart reconciliation before live execution.",
      "sections": [
        [
          "Separate intention from account state",
          "An intent to buy is not an accepted order, and an accepted order is not necessarily a fill. Model pending submission, acknowledgement, partial fill, filled, cancel requested, cancelled and rejected states as appropriate to the broker API. Preserve broker order identifiers alongside internal intent identifiers.\n\nA timeout creates uncertainty: the request may have failed before reaching the broker or succeeded before the acknowledgement was lost. Blindly submitting another market order can double exposure. Query and reconcile the authoritative account state under a documented policy."
        ],
        [
          "Make duplicate handling explicit",
          "Use a stable idempotency key for one instruction where the API supports it. Otherwise maintain a durable instruction-to-order record and a conservative uncertain-state process. A fresh process identifier should not turn the same stale instruction into a new trade.\n\nTest duplicates before and after acknowledgement, network interruption during submission, and restarts with outstanding orders. Those fixtures exercise software behaviour; they are not simulated trading profits or a production-readiness certificate."
        ],
        [
          "Partial fills need quantity ownership",
          "Track requested, filled, remaining and cancelled quantity. Average fill price is meaningful only with the matching quantity and fee allocation. An exit for the original requested amount can over-close or reverse a partially filled position if the system ignores the actual state.\n\nDecide how the policy treats an entry that remains partly open beyond its expiry. Save cancel requests and later fills that arrive during cancellation. The broker's current API documentation, not a generic state diagram, governs the actual legal sequence."
        ],
        [
          "A restart starts with reconciliation",
          "Reload the last durable state, inspect broker positions and open orders, and reconcile them before permitting new instructions. Identify manual positions separately. Do not infer a flat account from an empty in-memory cache or a missing local file.\n\nFor production, durable state, scheduling and failure reporting must belong to managed cloud services and continue with personal computers off. Local notebooks and this site's browser worksheets are research tools, not production publishers, monitors or fallback execution paths."
        ],
        [
          "Predeclare stop and recovery decisions",
          "Write down who can stop new entries, how open orders are reviewed, how existing exposure is handled and what evidence is needed before resuming. A kill switch that stops the process may leave orders resting at the broker. A control that cancels orders may leave positions open.\n\nKeep an incident timeline and compare intended orders, actual broker fills and accounting after recovery. QuantConnect's reconciliation documentation is a platform example of comparing live and simulated behaviour; it does not certify an unrelated implementation."
        ],
        [
          "Distinguish rehearsal from production evidence",
          "A successful local restart fixture exercises the code paths you simulated. Production requires a real managed-cloud execution, durable state and authoritative account or artifact readback under its actual identity. Do not call code presence, a research LIVE label or an inventory of endpoints proof that the intended subscriber route is deployed and certified."
        ]
      ]
    }
  ],
  "bibliography_notes": {},
  "scope": "Educational research design and invented arithmetic examples. No strategy returns, broker execution or production certification are supplied.",
  "expanded_edition": "2026-10-13",
  "disclosure": "The publication supports a marketing programme for Darren O'Neill and Vector Ridge while teaching research and implementation boundaries. The owner states legally independent ownership. Exact editorial coordination, sponsorship, referral arrangements and compensation were not documented; legal form alone cannot establish commercial neutrality or independent validation. The desk has not operated paid provider accounts, commissioned an external test panel or collected a real user-review population. Adjacent tools and missing source records remain part of the comparison.",
  "expanded_guides": [
    {
      "path": "guides/purging-overlapping-evaluation-labels.html",
      "title": "Overlapping labels and evaluation boundaries",
      "description": "Inspect event spans before treating separated rows as independent financial observations.",
      "sections": [
        [
          "A row boundary can miss a future label",
          [
            "An entry observation can have an outcome that depends on prices several bars later. If its label span crosses a reserved boundary, assigning its start row to development does not prevent later evaluation information from entering selection. Keep label start, label end and producing exit convention, not only a timestamp used for splitting. A historical transformation can also use future observations or revised values. These are different defects. A calendar division is useful only after the actual information and exposure spans are understood; a neat percentage split cannot by itself establish independence or an untouched economic evaluation."
          ]
        ],
        [
          "Use an interval example before a generic gap",
          [
            "Imagine an invented development event beginning at bar 18 whose outcome is known only at 24, while a reserved segment begins at 22. Its label overlaps that segment. A predeclared treatment may exclude that event from selection or choose another design appropriate to the authorised method. The exact treatment and any embargo need the actual horizon and dependence, not an arbitrary gap selected for better results. The scikit-learn time-series split gap is a documented software feature, but it does not automatically inspect every financial label interval, open position or data-release revision for the user."
          ]
        ],
        [
          "Warmup and open exposure need separate treatment",
          [
            "Earlier observations may be used causally to build state without scoring their outcomes, depending on the declared method. A position already open at a boundary is another object that can affect later cash and decisions. Record whether it is carried, excluded or separately measured under the original policy. Do not force an unrecorded liquidation just to make the split look clean. The small teaching replay has only invented observations and no economic holdout. Its warmup, eligible intent range and buffer tail demonstrate software timing, not a financial purging or embargo certificate."
          ]
        ],
        [
          "Preserve the exposed status after a change",
          [
            "Once a reserved result is inspected, changing label horizon, exit rule or split policy using it creates exposure that a new filename cannot remove. Retain the original decision log, source, effective treatment and reason for revision. A correctness fixture can verify that code excludes the specified intervals while remaining irrelevant as an independent market sample. Actual instrument research must follow its full authorised method, resource bounds and separate master requirements. This guide supplies an interval question and explicit missing evidence, not a universal split ratio, sample-size guarantee or permission to optimise a new exit on the same viewed period."
          ]
        ]
      ],
      "case": "The fictional development event spans bars 18 through 24; a reserved boundary is 22. Its start is earlier, but its producing label reaches into the reserved interval. The review marks overlap instead of calling the row independent. A fixed row gap would need its own justified contract. No actual label population, market dependence or economic validation is supplied. The BATS prefix checks concern invented software behaviour and do not resolve this financial evaluation design.",
      "rows": [
        [
          "Event start",
          "18",
          "Insufficient alone"
        ],
        [
          "Outcome known",
          "24",
          "Label end matters"
        ],
        [
          "Reserved boundary",
          "22",
          "Overlap present"
        ],
        [
          "Design treatment",
          "Predeclare for actual method",
          "No universal gap inferred"
        ]
      ],
      "sources": [
        [
          "scikit-learn time-series split and gap parameter",
          "https://scikit-learn.org/stable/modules/generated/sklearn.model_selection.TimeSeriesSplit.html"
        ],
        [
          "QuantConnect research guide",
          "https://www.quantconnect.com/docs/v2/cloud-platform/backtesting/research-guide"
        ]
      ]
    },
    {
      "path": "guides/entry-objective-and-fixed-exit-validation.html",
      "title": "Entry objectives and a fixed exit validation",
      "description": "Freeze entry identity before exit-adjusted measures are used to validate or reject it.",
      "sections": [
        [
          "The objective identifies what is being learned",
          [
            "An entry model has a declared causal learning or ranking objective. Return, profit factor, win fraction and holding-period drift after applying an exit measure another object. Allowing those later measures to define entry identity can silently convert an entry experiment into a combined entry/exit search. The canonical research policy keeps raw causal boundary recovery as the entry objective and freezes entry identity before applying a selected exit. This page explains that separation without changing it, building an asset model or claiming that the website's synthetic crossover is a calibrated proprietary entry candidate."
          ]
        ],
        [
          "Exactly one predeclared exit keeps the question fixed",
          [
            "Choose and record the applicable exit policy before financial evaluation under the authorised method. Exit-adjusted results can validate, reject, size or measure overlap, but should not retroactively choose the entry objective. Do not reopen a tournament of stops, targets and holding clocks after validation or forward data is viewed. A separate new research hypothesis can be recorded with its exposure acknowledged. The teaching packet has one time exit fixed for a mechanics test. It contains no entry training, parameter optimiser, alternative exit contest or unseen market validation, so it cannot be used as evidence that this research-policy gate passed."
          ]
        ],
        [
          "A completed identity boundary",
          [
            "The source launcher freezes 3- and 5-bar rolling windows, one-unit entries and the time exit. A changed stop or window would produce another setting/source identity, even if the same example name were retained. The checksum map can show changed bytes; it cannot prove when the researcher decided to change them or what outcomes were already known. The negative 1.20 cash total stays attached to the original fixture. Selecting a more profitable synthetic variant and calling it an independently validated entry would confuse software illustration, economic evidence and the real decision history."
          ]
        ],
        [
          "Native policy and the full process remain authoritative",
          [
            "An actual instrument task needs appropriate data routing, frozen dependencies, warmup, periods, calibration and independent master requirements. A missing new-asset integration is part of that task, not permission to erase identity guards or route it through an unrelated class. Native minute exits and whole-position/maximum-hold ownership remain separate from the tutorial's chosen time rule. No daily stop manager or production promotion is created by this article. A verified no-model result can be complete under the actual full process; a few software fixtures or an attractive replay do not supply that completion."
          ]
        ]
      ],
      "case": "The fictional teaching specification has a fixed 3/5 crossover and one three-completed-bar time exit. It has no trained entry identity or financial holdout. A visitor proposing another exit after reading its negative result must label that as a new fixture choice, not a second independent validation of the original. Neither version would become a canonical instrument model, alter the raw causal entry objective or satisfy a separate master merely because the simulator runs.",
      "rows": [
        [
          "Entry objective",
          "Canonical causal objective in real research",
          "Not defined by exit P&L"
        ],
        [
          "Teaching entry",
          "Fixed 3/5 crossover",
          "No training"
        ],
        [
          "Exit",
          "One predeclared time rule",
          "No tournament"
        ],
        [
          "Master/promotion",
          "Different full evidence required",
          "Not supplied by fixture"
        ]
      ],
      "sources": [
        [
          "QuantConnect research guide",
          "https://www.quantconnect.com/docs/v2/cloud-platform/backtesting/research-guide"
        ],
        [
          "Backtesting.py official API",
          "https://kernc.github.io/backtesting.py/doc/backtesting/backtesting.html"
        ]
      ]
    },
    {
      "path": "guides/parameter-search-ledger-and-negative-results.html",
      "title": "Parameter search history and negative results",
      "description": "Retain the real choice set rather than presenting only the selected attractive curve.",
      "sections": [
        [
          "A final candidate is not the search population",
          [
            "A research process can consider windows, universes, transformations, entries, exits, cost assumptions and reporting intervals. Those choices matter even when the final rule looks simple. Record what was actually evaluated and the reason for each rejection or revision. A short list of published winners is not the complete research population. Do not invent a candidate count or claim that an unrecorded search was small. Economic selection also differs from software correctness: a candidate that crashes may fail implementation checks without providing a market observation about the hypothesis."
          ]
        ],
        [
          "The teaching fixture does not optimise",
          [
            "The sample uses one fixed 3/5 rule and one time exit over deliberately constructed observations. The library's optimiser is not called. Its negative 1.20 cash is preserved with all six transactions, not replaced by a setting chosen to create a positive screenshot. That establishes a complete single-fixture teaching record, not a financial search ledger. No unseen market evaluation, training period or calibrated objective exists. A reader changing a parameter can create another clearly labelled software exercise, but neither configuration should be marketed as an independently validated strategy discovered from real observations."
          ]
        ],
        [
          "Classify the reason for a change",
          [
            "A source availability bug, arithmetic defect, failed economic hypothesis and operational route mismatch are different findings. A bug fix can invalidate an earlier result, while a properly tested negative market result can remain valuable evidence. Preserve the exact source/data/settings identity, exposed periods, observed defect and next action. A revised file hash identifies changed bytes but does not restore an untouched holdout. Keep old and new records available rather than merging them into a single favourable chart. A copied model nickname or publishing date cannot conceal the actual sequence of research decisions."
          ]
        ],
        [
          "A bounded negative result stays useful",
          [
            "A complete negative finding under an authorised real research process can justify no model or no promotion, but it needs that process's required independent checks. A synthetic negative total is not evidence that a real instrument or family failed the entire factory. Conversely, a synthetic positive variation is not proof of a profitable cause. The publication adds neither a performance league nor a fabricated expert endorsement. Its purpose is to show the records that allow a later reviewer to distinguish selection, correctness, economic rejection and operational readiness without inventing missing periods, counts or audit scope."
          ]
        ]
      ],
      "case": "The fictional decision log has one declared configuration, no optimiser call and six completed simulated transactions. Total net cash is negative 1.20. A proposed change to the rolling windows is recorded as another fixture revision, with the earlier result retained. There is no actual candidate family count, independent financial holdout or verified no-model master. The completed teaching conclusion is that the original software exercise is reproducible, including its unfavourable total.",
      "rows": [
        [
          "Choice set",
          "One fixed fixture rule",
          "No optimiser"
        ],
        [
          "Observed fixture",
          "Six simulated positions",
          "-1.20 net cash"
        ],
        [
          "Proposed revision",
          "New source/settings identity",
          "Old record retained"
        ],
        [
          "Financial rejection",
          "Full actual process required",
          "Not inferred"
        ]
      ],
      "sources": [
        [
          "QuantConnect research guide",
          "https://www.quantconnect.com/docs/v2/cloud-platform/backtesting/research-guide"
        ],
        [
          "Backtesting.py official API",
          "https://kernc.github.io/backtesting.py/doc/backtesting/backtesting.html"
        ]
      ]
    },
    {
      "path": "guides/paper-execution-and-historical-replay.html",
      "title": "Paper execution and historical replay evidence",
      "description": "Compare the producing environments without calling a rehearsal actual account performance.",
      "sections": [
        [
          "Several tools can all be called simulation",
          [
            "A historical engine processes an ordered stored dataset under its own fill and cost rules. A paper execution system may process current events and emulate broker responses under another model. A real account provides actual transactions and operational state. Those environments can all be useful but answer different questions. Identify source, timing, quantity, fees, queue/impact treatment and order-state authority before comparing them. A current product description can document a paper feature without proving its realism or the economic validity of a chosen strategy. This desk did not operate a paid paper or live provider account."
          ]
        ],
        [
          "A completed cross-environment source request",
          [
            "The BATS library fixture supplies next-open simulated fills on 64 invented bars. It has no real receiving delay, partial fill, cancellation race or broker acknowledgement. An invented paper worker might instead record an intent and an emulated acknowledgement but no actual account transaction. The appropriate comparison asks which state and fill rules differ; it does not assign the historical fixture's cash to the paper worker. A real production reconciliation would retain intended orders, actual account state and matching identities. A chart alone cannot establish that both environments applied the same data and execution contract."
          ]
        ],
        [
          "Rehearsal does not imply promotion",
          [
            "A local successful restart or paper run can test selected software paths while leaving managed production ownership untested. An actual promotion requires authority, durable cloud state, scheduling, failure reporting and independent artifact/account readback under the correct identity. A research LIVE label, installed source file or endpoint inventory is insufficient. The website deploys only static educational material; it creates no broker route, local monitor or account fallback. The sample's production-promotion flag remains false even though source, checks and simulated transactions are complete."
          ]
        ],
        [
          "Economic and operational gaps can coexist",
          [
            "A mechanically correct system can lack independent strategy evidence, while an economically promising research result can lack operational readiness. Keep both findings instead of forcing a universal pass score. The original release workbench retains ten separate evidence questions. Documentation can identify an adjacent tool's role while actual paid access, fees or full outcome population remain unresolved. The new checksum inspector adds file equality only, not another independent audit. Retain source identity, environment, exposed periods and known omissions in any comparison, and do not treat an artificial or paper profit as an audited subscriber return."
          ]
        ]
      ],
      "case": "The fictional historical packet has six simulated whole-unit fills under next-open rules; a separate imagined paper worker has only intentions and emulated acknowledgements. Neither supplies actual broker transactions. The review records the different fill and state contracts without transferring the negative 1.20 historical-fixture cash to the paper worker. Real route ownership and economic validation remain absent. The teaching result is a completed environment comparison question, not a production readiness certificate.",
      "rows": [
        [
          "Historical fixture",
          "Stored invented bars; model fills",
          "Software reference"
        ],
        [
          "Paper worker",
          "Emulated live state",
          "Different contract"
        ],
        [
          "Actual account",
          "Transactions not supplied",
          "No broker outcome"
        ],
        [
          "Promotion",
          "Cloud authority/readback required",
          "Not created here"
        ]
      ],
      "sources": [
        [
          "QuantConnect live/backtest reconciliation",
          "https://www.quantconnect.com/docs/v2/writing-algorithms/live-trading/reconciliation"
        ],
        [
          "QuantConnect slippage modelling",
          "https://www.quantconnect.com/docs/v2/writing-algorithms/reality-modeling/slippage/key-concepts"
        ]
      ]
    },
    {
      "path": "guides/cloud-release-and-research-state.html",
      "title": "Cloud release evidence and research state",
      "description": "Separate research labels, code, gates, deployed identity, subscriber routing and certification.",
      "sections": [
        [
          "A filename cannot own production",
          [
            "A file labelled LIVE can describe a research state while never being merged, registered, deployed or routed to subscribers. An endpoint inventory can describe available code without proving which revision executes. A grade map has another purpose. Record research identity, code/merge state, registry gate, deployed revision, actual route and certification separately. The authorised production deployment ledger is the source for actual model state, not an inference from a name. This guide does not read or claim any particular model's live status; it explains the evidence objects a real deployment task would have to inspect."
          ]
        ],
        [
          "A real cloud artifact has a bounded claim",
          [
            "A deployment receipt should identify actual managed execution, its producing revision and durable output, followed by independent readback. The static website release uses a frozen public-file stage and verifies public content, schemas, downloads and private boundaries. That proves publication under its own identity, not a deployed trading model, refreshed data pipeline or subscriber certification. A local test can support development without owning normal production continuity. Production publishers, refreshes, schedulers, monitors and recovery must continue with personal computers and local agent sessions off."
          ]
        ],
        [
          "A completed fictional label mismatch",
          [
            "An invented research folder says LIVE, the code is unmerged and no registry or cloud execution receipt is provided. The correct finding is research label present with deployment unresolved. Renaming the folder, adding an endpoint or producing a local plot would not fill the missing records. A later verified cloud artifact could change a bounded code/runtime finding while subscriber routing and certification still need separate evidence. The teaching replay has false production-promotion status and no actual account, so its complete mechanics cannot be used to bypass that distinction."
          ]
        ],
        [
          "Preserve monitoring and failure ownership",
          [
            "Moving production ownership to the cloud must not erase a required monitor, weaken certification or silently discard an unresolved operational function. A real task needs authoritative cloud state, failure reporting and recovery under the intended owner. The website creates no desktop scheduler, tunnel, unattended agent dependency or PC fallback. Its temporary QA server closes after browser testing. The synthetic source launcher is an optional local teaching reconstruction, not a required input for a running production job or next scheduled refresh. A production claim remains incomplete until the actual cloud and route evidence exists, regardless of how dense the educational page becomes."
          ]
        ]
      ],
      "case": "The fictional record has a research LIVE label and source code but no merged revision, registry gate, cloud receipt or subscriber route. The reviewer does not declare deployment from those first two objects. The BATS website's own cloud publication receipt concerns static educational files only. Its source packet has no production authority. The completed finding separates known research/code context from the missing operational evidence rather than pretending one local run certifies all stages.",
      "rows": [
        [
          "Research label",
          "LIVE text exists",
          "Not deployment proof"
        ],
        [
          "Code state",
          "Unmerged in example",
          "Separate record"
        ],
        [
          "Cloud execution",
          "No actual receipt in example",
          "Unresolved"
        ],
        [
          "Route/certification",
          "Other authoritative records needed",
          "Not inferred"
        ]
      ],
      "sources": [
        [
          "QuantConnect live/backtest reconciliation",
          "https://www.quantconnect.com/docs/v2/writing-algorithms/live-trading/reconciliation"
        ],
        [
          "QuantConnect research guide",
          "https://www.quantconnect.com/docs/v2/cloud-platform/backtesting/research-guide"
        ]
      ]
    },
    {
      "path": "guides/dependency-upgrades-and-reference-regressions.html",
      "title": "Dependency upgrades and reference regressions",
      "description": "Retain the old environment and check changed mechanics before trusting a familiar curve.",
      "sections": [
        [
          "A version change creates a comparison task",
          [
            "A library upgrade can alter warmup, order semantics, fee treatment, finalisation or numerical representation without changing the user strategy source. Pin the original environment and preserve its output before testing the replacement. The fixture uses Backtesting.py 0.6.6 with recorded numerical dependencies and a downloadable requirements file. It does not automatically adopt the globally newest package. A version string identifies software but cannot prove identical behaviour, so the event ledger, cash and failure-state checks remain necessary. No live production dependency is changed by this teaching example."
          ]
        ],
        [
          "Reconstruct exact inputs and bounded outputs",
          [
            "The public map records raw CSV, source and settings identities. Repeated replay under the stated environment must reproduce the same object. Independent Decimal checks reconcile available rolling values, strict crossover intentions, next-open prices, completed holding distance and fees. Future-suffix checks and malformed input fixtures exercise other contracts. An upgraded environment can produce a different identity or result that needs explanation rather than a silent overwrite. A two-decimal display may hide a small numerical residue, so retain the original output and tolerance while distinguishing harmless formatting from a material accounting difference."
          ]
        ],
        [
          "Correctness fixes and economic revisions differ",
          [
            "A parsing bug or unintended future transform may invalidate a prior financial result. Changing a selected exit, data universe or hypothesis after viewing a reserved period is a research revision with exposure, not simply a library maintenance pass. Record the actual reason, affected run and effective source/environment. The synthetic fixture has no economic evaluation, so its tests cannot certify a real model after an upgrade. A production task would also need actual cloud execution, route identity and certification gates. A local successful install or test suite cannot replace those receipts."
          ]
        ],
        [
          "Keep the negative reference and its rights boundary",
          [
            "The original six-position result remains negative 1.20 under its fixed fees. It is not replaced by a setting chosen to flatter an upgraded engine. The downloadable source and package licence support a transparent teaching reconstruction; no rights are asserted over proprietary model code or a paid market dataset. The native site build and local refresh hooks regenerate byte-identical public files from frozen original pages and the expanded edition. Those publication checks are different from a strategy regression suite. Keep the exact object and limitation attached when explaining what changed, what stayed stable and what still needs independent financial or operational evidence."
          ]
        ]
      ],
      "case": "The fictional upgrade review first preserves the original CSV, source, settings and receipt under engine 0.6.6. A proposed newer runtime must be compared against the same event and cash contracts rather than overwriting the negative reference with a new screenshot. The page claims no tested result for that proposed upgrade. Economic evaluation and production route remain absent. The completed original software checks are reproducible without being relabelled as strategy certification.",
      "rows": [
        [
          "Original runtime",
          "Engine 0.6.6; declared dependencies",
          "Frozen reference"
        ],
        [
          "Inputs",
          "Raw data/source/settings IDs",
          "Retained"
        ],
        [
          "Upgrade proposal",
          "No tested replacement here",
          "Separate comparison"
        ],
        [
          "Financial/production gates",
          "Independent evidence required",
          "Not supplied by install"
        ]
      ],
      "sources": [
        [
          "Backtesting.py package and licence metadata",
          "https://pypi.org/project/backtesting/0.6.6/"
        ],
        [
          "Backtesting.py official API",
          "https://kernc.github.io/backtesting.py/doc/backtesting/backtesting.html"
        ]
      ]
    },
    {
      "path": "guides/engine-version-and-fill-contract.html",
      "title": "Engine version and the fill contract",
      "description": "Pin the simulator and identify when an intention can become a simulated transaction.",
      "sections": [
        [
          "The engine is part of experiment identity",
          [
            "A source rule can be unchanged while a library upgrade changes warmup, order priority, fees or finalisation. Record engine version, data format, order semantics, cost policy and environment beside the rule. The teaching packet pins Backtesting.py 0.6.6 and records the actual numerical dependencies. It uses one-unit long market intentions, next-open fills, fixed fees and no forced final liquidation. Those choices define this software fixture; they are not a universal execution model for stocks, futures, crypto or options. A current library manual describes mechanisms, not the actual liquidity that a real broker would provide."
          ]
        ],
        [
          "Keep decision and fill clocks distinct",
          [
            "An intention based on a completed close cannot generally fill earlier inside that same unfinished bar without another order and information contract. In the example, intent bar 7 produces simulated entry at bar 8 open. The entry-fill bar is counted as completed holding bar one, so bar 10 close requests a whole exit and bar 11 open provides the simulated fill. Retain all four IDs, not just one transaction time. The arbitrary UTC labels in the input are invented and do not encode an exchange session, auction deadline or actual subscriber receiving event."
          ]
        ],
        [
          "Fees and termination affect the result",
          [
            "A fixed 0.10 fee is assessed on each entry and each exit, giving 0.20 for a complete one-unit position. There is no separate spread, financing or slippage amount. Automatic final liquidation is disabled. Entry eligibility ends at bar 49, while buffer bars allow outstanding time exits to complete, so the fixture finishes flat rather than using an undeclared closing price. These are explicit constraints of the sample. A real economic study may need another contract, but changing it after viewing results creates a new experiment rather than another reconstruction of the original."
          ]
        ],
        [
          "A fill policy is not financial assurance",
          [
            "The exported trade rows can be checked against synthetic open prices and independent cash arithmetic. That verifies the chosen model behaviour, not actual execution or a profitable hypothesis. The tutorial's next-open convention does not replace canonical VR observation-window fills or native minute exits. A real instrument task must preserve the authorised method, identities and master checks. No queue, partial fill, nonlinear payoff or broker recovery is represented by this small library fixture. The useful conclusion is a reproducible timing contract with named limitations, not a claim that every intended transaction would be achievable in a market."
          ]
        ]
      ],
      "case": "The fictional rule emits intent 7, enters at synthetic open 8 at 99.2, requests its time exit at close 10 and exits at open 11 at 101.9. One-unit gross cash change is 2.7; two fixed fees total 0.20, leaving 2.50 in this simulated position. Five other positions remain in the same packet, including losers. Total net cash is negative 1.20. No real order or target probability is supplied.",
      "rows": [
        [
          "Intent",
          "Bar 7 completed close",
          "No earlier fill"
        ],
        [
          "Entry",
          "Bar 8 open; 99.2",
          "Library simulation"
        ],
        [
          "Exit request",
          "Bar 10 completed close",
          "One fixed rule"
        ],
        [
          "Exit fill",
          "Bar 11 open; 101.9",
          "2.50 net after declared fees"
        ]
      ],
      "sources": [
        [
          "Backtesting.py official API",
          "https://kernc.github.io/backtesting.py/doc/backtesting/backtesting.html"
        ],
        [
          "Backtesting.py package and licence metadata",
          "https://pypi.org/project/backtesting/0.6.6/"
        ]
      ]
    },
    {
      "path": "guides/rolling-window-warmup-and-prefix-invariance.html",
      "title": "Warmup and future-suffix invariance",
      "description": "Test which observations an indicator and decision may consume without claiming an independent market sample.",
      "sections": [
        [
          "Warmup changes the evaluated population",
          [
            "A rolling mean cannot be treated as valid before its intended past window exists. The example has 3- and 5-bar causal means, and the library's first decision is bar 5. Earlier CSV rows are warmup observations, not eligible system outcomes. A library may start one step after the first nonmissing indicator because a crossover also needs a preceding value. Record the observed start and explain the actual rule. A longer parameter window can change which dates or events are evaluated even if another setting shares the same nominal input file. A fair comparison cannot ignore that population change."
          ]
        ],
        [
          "Precomputed does not automatically mean future-aware",
          [
            "An engine may precompute an indicator on a full array while revealing only the current prefix to a strategy. The transformation itself must still be causal. A rolling past mean can satisfy that contract; a centred window, future-filled gap or scaler fitted on reserved observations may not. Do not infer causality merely from the library's interface or an attractive chart. Preserve transformation code, window orientation, fitted scope and missing-value policy. The teaching reference uses past rolling means, while a separate Decimal check reconstructs each available value from exactly the preceding declared window."
          ]
        ],
        [
          "Change later values and compare earlier decisions",
          [
            "The fixture makes four labelled suffix mutations after bars 14, 25, 37 and 49. All earlier indicator and decision records must remain equal. The later rows deliberately change while the prefix is retained, allowing a bounded check of future sensitivity. A changed future source may legitimately change later orders and cash, which are not required to remain equal. The test is not a new financial validation period, and repeated prefixes are not independent market samples. It establishes the tested implementation's behaviour under those specific mutations, not immunity to every possible timing defect."
          ]
        ],
        [
          "Warmup crossing a real boundary needs a rule",
          [
            "An actual reserved evaluation may use earlier observations for causal state while excluding their outcomes from scoring, depending on the predeclared method. Open positions, overlapping labels and source revisions also need handling at the boundary. The synthetic packet supplies no untouched economic holdout or real market. Its first eligible bar and buffer tail are fixture mechanics only. Keep a real evaluation's data, exposure and selection history separately. A passing suffix test cannot repair a missing point-in-time source or prove that a researcher never used the reserved results when selecting parameters or an exit."
          ]
        ]
      ],
      "case": "The fictional input has 64 bars, but decisions start at 5. A 3-bar mean at decision i uses closes i-2 through i, while the 5-bar mean uses i-4 through i. Changing every later bar after cut 25 by an invented price offset leaves all decision records through 25 unchanged. That passes a software-prefix check only. There is no independent unseen market segment, audited return or evidence that a real instrument's historical observations were available at those times.",
      "rows": [
        [
          "Warmup",
          "Input bars before decision 5",
          "Not scored outcomes"
        ],
        [
          "Fast window",
          "i-2 through i",
          "Past and current completed close"
        ],
        [
          "Slow window",
          "i-4 through i",
          "No future close"
        ],
        [
          "Suffix checks",
          "Cuts 14 / 25 / 37 / 49",
          "Earlier decisions unchanged"
        ]
      ],
      "sources": [
        [
          "Backtesting.py official API",
          "https://kernc.github.io/backtesting.py/doc/backtesting/backtesting.html"
        ],
        [
          "QuantConnect warmup periods",
          "https://www.quantconnect.com/docs/v2/writing-algorithms/historical-data/warm-up-periods"
        ]
      ]
    },
    {
      "path": "guides/intrabar-stop-target-ambiguity.html",
      "title": "When a bar touches both stop and target",
      "description": "Record the unresolved path and engine priority rather than selecting the favourable fill.",
      "sections": [
        [
          "A bar summary can omit event order",
          [
            "An OHLC bar records summary prices, not every transaction in chronological order. If a long entry is 100, stop 98, target 104 and the bar spans low 97 to high 105, both levels can lie inside the summary. The summary alone does not establish which was reached first after the relevant entry or whether an order was active at that time. A generic choose-the-profitable-price rule would add information not present in the source. A finer event record or a predeclared conservative engine convention is needed before a single exit can be interpreted."
          ]
        ],
        [
          "Read the exact engine and order contract",
          [
            "A simulator has specific rules for contingent orders, new entries, gaps and ambiguous bars. A current manual is a starting source, while the pinned version and a targeted fixture establish the behaviour actually used. Do not generalise one engine's rule to all brokers or instruments. A stop trigger also differs from an actual execution, and the intended target may never have filled. The BATS reference deliberately uses one time exit with next-open fills, not competing intrabar stop and target orders. It therefore cannot be cited as a test that resolves every contingent-order ambiguity."
          ]
        ],
        [
          "A completed source-bound scenario",
          [
            "Keep the same invented OHLC record and calculate the two conditional amount branches separately. A stop-price liquidation at 98 gives negative two price units per held unit before costs; a target-price liquidation at 104 gives positive four. Neither is selected as observed truth. Assign no probability without evidence. A real transaction study would need entry activation time, order state, actual event or tick path, fills, fees and complete eligible positions. The two conditional calculations explain the missing object instead of pretending a favourable historical curve establishes the order of events."
          ]
        ],
        [
          "Do not reopen the exit choice after evaluation",
          [
            "The treatment of ambiguous bars belongs in the frozen execution policy before a financial evaluation. Choosing an optimistic priority only after seeing whether it improves the holdout changes the experiment and exposes that period. Preserve the old source, policy and result if a correction is necessary. An implementation test can show deterministic priority without proving it realistic in a market. The actual canonical method and native exit owner remain separate from this teaching discussion. No daily profit floor, new proprietary stop manager or alternative exit tournament is introduced by explaining the two unresolved branches."
          ]
        ]
      ],
      "case": "The invented long has entry 100, stop 98, target 104 and a summary bar low 97/high 105. Conditional stop-price change is negative 2; conditional target-price change is positive 4. The packet contains no event order or transaction evidence, so the completed finding is path ambiguity rather than a winning trade. The BATS library fixture uses only its declared time exit and does not test this contingent-order case as if it were a real broker fill.",
      "rows": [
        [
          "OHLC range",
          "Low 97 / high 105",
          "Both levels inside"
        ],
        [
          "Stop branch",
          "98 - 100",
          "-2 per unit before cost"
        ],
        [
          "Target branch",
          "104 - 100",
          "+4 per unit before cost"
        ],
        [
          "Chronology",
          "Not supplied",
          "No favourable branch selected"
        ]
      ],
      "sources": [
        [
          "Backtesting.py official API",
          "https://kernc.github.io/backtesting.py/doc/backtesting/backtesting.html"
        ],
        [
          "QuantConnect slippage modelling",
          "https://www.quantconnect.com/docs/v2/writing-algorithms/reality-modeling/slippage/key-concepts"
        ]
      ]
    },
    {
      "path": "guides/synthetic-data-and-point-in-time-history.html",
      "title": "Synthetic fixtures and point-in-time market history",
      "description": "Use invented data for software tests without laundering it into a historical trading source.",
      "sections": [
        [
          "The source category is a field, not an impression",
          [
            "The reference CSV is deliberately constructed data with arbitrary UTC timestamps. No exchange, licensed feed, real ticker, corporate action or historical universe supplied it. Its completed shape makes it useful for deterministic software tests, not for measuring a market hypothesis. A familiar date format or professional chart does not change the classification. Keep invented status in the CSV description, replay receipt, visible workbook and machine records. Never substitute plausible synthetic rows for missing historical data and report them as observed evidence because the downstream simulator accepts the file."
          ]
        ],
        [
          "Historical identity includes availability and revisions",
          [
            "A real data contract needs instrument identity, producing source, observation and availability times, timezone, relevant revisions, normalization and point-in-time membership. Current survivors cannot automatically describe an older universe, and a revised release may not be what a decision could originally know. Individual futures contracts and separately labelled continuous research references also have different scope. A toy file containing generic prices does not resolve those routes. The authorised instrument process must select and verify the actual source before a stronger financial conclusion, without erasing identity guards or treating unavailable individual contracts as a universal blocker to reference research."
          ]
        ],
        [
          "Synthetic defects can still teach useful behaviour",
          [
            "The small loader rejects duplicate IDs, duplicate times, invalid OHLC ranges, nonfinite values and missing rows. Its input bars are strictly ordered one-minute observations under an invented clock. These checks demonstrate selected parsing and identity behaviour. They do not establish that a real feed has no gaps, correct corporate actions or permissible redistribution. The prefix mutations change later invented observations to check causal processing; they are not historical revisions or independent validation periods. Retain the exact source bytes and contract so a reader can distinguish a completed software case from an absent market source."
          ]
        ],
        [
          "A completed negative research boundary",
          [
            "The frozen rule produces six simulated positions and negative 1.20 net cash under the declared fee policy. That result is complete as a software reference but cannot accept or reject a real market family. A verified no-model master requires the separate complete authorised research and independent checks, not a synthetic example with a negative total. Likewise, a positive variation would not be validated profit. The publication does not promote this fixture, replace canonical fill conventions or invent raw-data rights. The useful teaching conclusion states exactly which software questions are answered and which economic questions still need actual producing evidence."
          ]
        ]
      ],
      "case": "The fictional builder receives a CSV with 64 invented OHLC bars and a working replay launcher. The loader and prefix tests pass, but the source category stays synthetic. No point-in-time real universe, exchange-session clock or independent market sample exists. The recorded negative 1.20 belongs to the library fixture only. Renaming its arbitrary instrument field to a real ticker would not create historical data, suitable calibration, independent strategy evidence or a certified research result.",
      "rows": [
        [
          "Source",
          "Deliberately invented bars",
          "Software fixture"
        ],
        [
          "Clock",
          "Arbitrary one-minute UTC labels",
          "No exchange session"
        ],
        [
          "Input checks",
          "IDs / times / OHLC / finite / count",
          "Parsing and contract tests"
        ],
        [
          "Economic validation",
          "Actual market source absent",
          "Not performed"
        ]
      ],
      "sources": [
        [
          "QuantConnect research guide",
          "https://www.quantconnect.com/docs/v2/cloud-platform/backtesting/research-guide"
        ],
        [
          "QuantConnect warmup periods",
          "https://www.quantconnect.com/docs/v2/writing-algorithms/historical-data/warm-up-periods"
        ]
      ]
    },
    {
      "path": "guides/cost-basis-and-cash-reconciliation.html",
      "title": "Cash reconciliation and fee inclusion",
      "description": "Rebuild each simulated cash amount while keeping actual transactions and omitted costs separate.",
      "sections": [
        [
          "A price move and a cost record are different",
          [
            "The fixture's library fills use synthetic opens and one whole long unit. Gross cash change is exit price less entry price. Fixed commission is 0.10 at entry and 0.10 at exit, assessed separately, so each completed position deducts 0.20. The example does not include another spread, slippage, financing or tax amount. A real account could embed some costs inside transaction prices and assess others as separate charges. State inclusion before subtracting an all-in estimate, otherwise the same component may be charged twice. No current broker fee schedule is quoted by this teaching contract."
          ]
        ],
        [
          "Reconstruct the six-position ledger",
          [
            "The simulated positions have net cash of 2.50, negative 3.50, 3.00, negative 3.00, 2.90 and negative 3.10 after the fixed fees. Their sum is negative 1.20. The first row enters at 99.2 and exits at 101.9, giving 2.7 gross less 0.20. A later row enters at 99.2 and exits at 95.9, giving negative 3.3 gross less 0.20. Both remain in the same eligible packet. The total is not selected from only favourable rows, and there is no actual subscriber transaction or market source behind either amount."
          ]
        ],
        [
          "Preserve numerical output and reference tolerance",
          [
            "The standard engine returns floating-point cash, while an independent Decimal calculation reconstructs declared prices and fees. The exact teaching sum is negative 1.20 at the stated decimal representation; the engine's displayed raw total differs by a tiny numerical residue. The checker uses an explicit tolerance and preserves the actual output rather than rewriting it as a perfectly exact independent audit. A reader-facing two-decimal amount is formatting. It is not a rounding explanation for unrelated provider aggregates, evidence of actual account accuracy or permission to conceal a material reconciliation difference."
          ]
        ],
        [
          "Cash equality does not establish a strategy",
          [
            "A replay cash reconciliation checks the selected model and inputs. It does not certify queue realism, data availability, financial selection history, paper execution or production routing. Actual account return also needs marks, flows, currency, quantity and other holdings. The fixture has no deposits, shorts or nonlinear contracts, and its chosen initial cash does not recommend a personal allocation. Preserve the full transaction population and cost policy when moving to a real study. A favourable individual simulated position cannot replace the net total, and a matching checksum cannot supply an absent broker statement or independent economic evaluation."
          ]
        ]
      ],
      "case": "The fictional reconciler keeps all six completed rows and computes gross signed price changes less two 0.10 fees. Net contributions are 2.50, -3.50, 3.00, -3.00, 2.90 and -3.10, totalling -1.20. The engine's raw floating output is retained and matched within the declared tolerance. No excluded cost is silently estimated and no actual broker ledger is supplied. This completes the specimen's accounting check, not an audited return or financial strategy validation.",
      "rows": [
        [
          "Per-position cost",
          "0.10 entry + 0.10 exit",
          "0.20 additional fee"
        ],
        [
          "First net row",
          "101.9 - 99.2 - 0.20",
          "2.50"
        ],
        [
          "Second net row",
          "95.9 - 99.2 - 0.20",
          "-3.50"
        ],
        [
          "Complete sum",
          "Six net rows",
          "-1.20 synthetic cash"
        ]
      ],
      "sources": [
        [
          "Backtesting.py official API",
          "https://kernc.github.io/backtesting.py/doc/backtesting/backtesting.html"
        ],
        [
          "QuantConnect live/backtest reconciliation",
          "https://www.quantconnect.com/docs/v2/writing-algorithms/live-trading/reconciliation"
        ]
      ]
    },
    {
      "path": "guides/experiment-manifest-and-artifact-hashes.html",
      "title": "Experiment manifests and artifact hashes",
      "description": "Identify exact input and output bytes without claiming unseen history or independent financial proof.",
      "sections": [
        [
          "One manifest must name several producing objects",
          [
            "A reproducible run needs data, source, settings, engine environment, output identity and the policy linking them. A short model name cannot establish those objects. The public checksum map lists the synthetic bars, canonical settings, source launcher, full receipt and transaction CSV with digest and byte size. The receipt separately records data, source and settings hashes. These links make this fixture traceable but do not imply that an external auditor ran it. All inputs remain invented, and the replay carries explicit false fields for economic validation and production promotion."
          ]
        ],
        [
          "Byte equality is narrower than semantic similarity",
          [
            "SHA-256 identifies the selected bytes. A change in line endings, whitespace or column order can change the digest even when a parser later produces similar values. Conversely, a matching file can still contain an exposed holdout, wrong financial premise or invented observations. The browser inspector reads raw bytes and compares the selected public reference artifact, not a guessed filename or a reserialized object. The checksum result should name its scope: equality with a publication reference, not broker authenticity, causal market evidence or a new engine execution."
          ]
        ],
        [
          "A completed file comparison",
          [
            "An unchanged copy of the published CSV matches the declared bars digest. Adding one byte, altering a price or selecting the source-code reference for the same CSV produces a mismatch. The comparison is useful even when the file is not valid market data, because it answers an identity question. An unreadable, empty or overlarge local file has no valid comparison record and clears export. A mismatch can still be exported as a bounded observed digest result; it is not silently converted to a match or treated as a verified financial rejection."
          ]
        ],
        [
          "Research exposure needs another history",
          [
            "A hash cannot prove when a researcher viewed a period or selected an exit. Access records, candidate decisions and effective policy versions are separate evidence. A correction changes artifact identities and should retain the prior run, including failures, while acknowledging any already exposed evaluation. The teaching packet has no untouched economic holdout, so its complete file map does not invent one. Actual model certification and managed-cloud route evidence also remain separate. A publicly hosted checksum map and downloadable launcher support method reproduction without creating independent consensus, a profitable forecast or an authority to transact."
          ]
        ]
      ],
      "case": "A fictional reader compares the public bars file to the bars reference and obtains equal bytes. A second copy with an appended newline has a different digest even though a forgiving CSV reader might ignore it. The source-code reference selected for the original CSV also mismatches. The conclusion is raw-file identity only. No private file is uploaded, no engine runs in the browser, and no unseen holdout or actual financial result is inferred from either outcome.",
      "rows": [
        [
          "Input identity",
          "Synthetic CSV SHA-256 and size",
          "Raw bytes"
        ],
        [
          "Run links",
          "Source / data / settings IDs",
          "Declared linkage"
        ],
        [
          "Altered copy",
          "One added byte",
          "Mismatch"
        ],
        [
          "Financial validation",
          "Different evidence required",
          "Not established by hash"
        ]
      ],
      "sources": [
        [
          "Backtesting.py official API",
          "https://kernc.github.io/backtesting.py/doc/backtesting/backtesting.html"
        ],
        [
          "Backtesting.py package and licence metadata",
          "https://pypi.org/project/backtesting/0.6.6/"
        ]
      ]
    }
  ],
  "workbook": {
    "path": "synthetic-replay-workbook.html",
    "record": "data/synthetic-system-replay.json",
    "classification": "synthetic library fixture; no economic validation"
  }
}
