Strategy robustness before capital deployment
Sign in

Metadata and reproducibility (analyze() output)

Source path in repo: docs/examples/07-metadata-and-reproducibility.md. [View on GitHub]

Mirrored from the engine repository. Prefer reading here for a consistent experience; use GitHub for file history and blame.

Every analyze() call returns metadata you should persist when comparing runs or filing bug reports.

TypeScript

Rules of thumb

  • Same logical input and config should yield the same hashes for a fixed engine version.
  • Changing decimals or seed changes configHash and may change outputs.
  • After formula or canonicalization changes, refresh test vectors (see packages/test-vectors/CONFORMANCE.md; run npm run engine:vectors:refresh-metadata from the engine repository root when that script exists in your checkout).

See [OPEN_CORE_REPRODUCIBILITY.md] for CI gates and release checks.

[Back to documentation index]