feat(research): persist trial outcomes and daily ledger - #636
Merged
Merged
Conversation
Co-Authored-By: Codex <noreply@openai.com>
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
1 participant
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.
Scope
Implements the next research foundation from the system review (§9.15.66–68, T09/U01–U03) and architecture (§5, B.2, B.4, B.8): independent trial outcome records and a daily cash/holdings/fees/NAV ledger. Failed, rejected, and aborted trials remain separate from ordinary performance results. A successful trial links to an existing
BacktestResultby exact run and version identity.The store uses create-only writes for trial start, terminal outcome, and ledger records. Cloud storage is authoritative when configured; local storage is used only without a cloud bucket. Existing performance result and promotion keys are unchanged.
Verification
git diff --checkand staged diff check: passed.Boundary
This PR establishes the shared storage contract only. It does not update the UES consumer or its pinned QPK dependency. The checks use synthetic and fake local/cloud adapters; they do not prove real cloud persistence, optimized live strategy identity, point-in-time plugin data, real trading costs, or portfolio performance. No promotion, paper/live activation, deployment, configuration change, or trading is included. Keep this PR in draft until the contract is reviewed.