docs: record refactor step D5b (PR #99) and the confirmed jump_amount_corr look-ahead - #100
Merged
Merged
Conversation
…_corr look-ahead
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.
Progress-doc-only PR. Records: the confirmed look-ahead in jump_amount_corr_20 (independently reproduced by two parties on different symbols and windows; the sharper cut — perturbing only bars at/after 14:51 — moves 1,363/1,363 cells, i.e. the signal sees the minute it trades in and the nine after), why no existing test caught it, and the ruling that truncating applies a standing research-side authorization while still requiring its own correctness-fix PR; the delivered evaluation contract v1.0; the two MEDIUM findings (a guard that could not guard itself, and a false view=decision claim one level up) with the general rule the second one produced — a mismatch that destroys meaning must be blocked, one that only introduces a disclosed sign-known bias must be recorded; the three premise problems now ruled on and queued, including the store's universe dependence (amendment A2, queued as D4c before C4) whose date-only gap detection is the very red line amendment A1 invoked to reject caller-side batching; and two methodology notes. Merged-PR list gains #98/#99. AGENTS.md byte-identical via cp. No code changes.