Add fixed time horizons validation guide - #303
Merged
Merged
Conversation
Contributor
|
uriahf
marked this pull request as ready for review
August 13, 2026 12:25
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.
What changed
uriahtalkshorizon explorer with transparent styling and emoji outcome statesWhy
Time-to-event predictions need an explicit evaluation horizon before performance is interpreted. This makes that prerequisite discoverable without reorganizing the rest of the documentation.
Validation
great-docs buildworkflowBefore You Validate → Fixed Time Horizons