Add deterministic Polymarket recording and replay - #16
Merged
Conversation
howdymary
force-pushed
the
codex/packet-4-forecast-provider
branch
from
July 15, 2026 00:06
11c7cd8 to
d49bc39
Compare
howdymary
force-pushed
the
codex/packet-5-recorder-replay
branch
from
July 15, 2026 00:06
081ff9e to
7880ebf
Compare
howdymary
marked this pull request as ready for review
July 15, 2026 00:15
12 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
autopredict.recordingv1 capture contract for Gamma metadata, CLOB books, public trades, explicit gaps, and later resolutionWhy / root cause
AutoPredict had no first-party point-in-time recorder, so realistic evaluation and shadow replay could not distinguish complete evidence from polling gaps. Venue identifiers and public transport state also needed an explicit fail-closed boundary before captured data could be treated as reproducible evidence.
User and developer impact
Developers can capture public Polymarket observations, append resolution later, verify immutable hashes and completeness warnings, and replay the result deterministically. Partial or malformed captures remain ineligible for performance claims; no market data or missing sequence is fabricated.
Schema and migration
Introduces versioned recording/capture contracts and a documented replay projection into
autopredict.dataset.v1. Existing evaluation datasets are unchanged. Recorder artifacts with unsupported completeness values, identity mismatches, discontinuities, or conflicting immutable targets are rejected with actionable errors.Verification
git diff --check: passedResidual risks
Tracks #2
Closes #9
Depends on #15.