Repository navigation
Separate future research gates from retrospective point estimates - #27
Merged
Merged
Conversation
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.
Freeze the evaluation sessions, objective boundary, planning alternative, calibration and paired block-bootstrap uncertainty in the immutable trial registry. Future eligibility depends on the original registration timestamp, complete validated pairs, review date, declared detectability and objective budgets. Point estimates and retrospective runs never grant engineering or promotion credit. Preserve gate and typed failure evidence in native research results/findings.
Validation: full suite 246 passed, 1 skipped with 84.76% branch coverage; the updated planning-margin tests pass. Full CI is required before merge.