Skip to content

Make result artifacts validated and failure-explicit #45

Description

@stefan-jansen

Findings: BR-033.

Define the required result-artifact manifest and schema behavior. Missing, incomplete, malformed,
or unsupported artifacts must fail precisely by default. Any legacy recovery path must be explicit
and report every omission.

Primary surfaces: BacktestResult.to_parquet, BacktestResult.from_parquet, config and spec
serialization, artifact tests and compatibility fixtures.

Acceptance:

  • Requested config and spec writes cannot disappear silently.
  • Empty directories, corrupt YAML or JSON, missing required files, and unsupported schema versions
    raise specific errors before a partial result is returned.
  • Explicit recovery mode remains deterministic and returns structured recovery diagnostics.
  • Valid current and retained beta artifacts round trip with complete content.

Dependencies: Issue 3.


Plan reference: /home/stefan/ml4t/libraries/ml4t-backtest-dev/.workspace/work/backtest-stable-release/milestone-1/plan.md - Issue 5 in milestone 0.1.0-m1 - Financial correctness and auditability.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions