Skip to content

Fail closed: preserve exact f64 values across MCTS checkpoint readback #428

Description

@proerror77

Change contract: enable exact JSON f64 roundtrips for ploy-research checkpoint state so a freshly written content-addressed MCTS checkpoint validates after typed readback.

Acceptance evidence:

  • A focused counterexample roundtrips -1.9089014592447406_f64 through the configured serde_json graph without changing to_bits().
  • The authenticated selection checkpoint readback test covers that nontrivial reward and passes.
  • Existing focused prediction MCTS tests pass.

Dependency / merge order: predecessor to #325; merge this before promoting the three-event E2E fixture.

Out of scope: evaluator semantics, cohort partitioning, Polymarket projection, collector/runtime, hft-search-kernel behavior, or checkpoint schema changes.

Rollout / rollback: dependency-feature-only correctness change; rollback restores the known false corruption rejection for valid floating-point metrics.

Observed failure: -1.9089014592447406_f64 serializes and parses one ULP apart under the current feature graph, so authenticated_selection_evidence reports selection checkpoint does not match the current durable state even though the persisted state and referenced artifact are otherwise identical.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions