Document triple-barrier topics and classification scoring in Forge - #187
Open
jefferythewind wants to merge 2 commits into
Open
jefferythewind wants to merge 2 commits into
jefferythewind wants to merge 2 commits into
Conversation
Signed-off-by: jefferythewind <tim@alloralabs.xyz>
✅ Deploy Preview for alloradocs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Signed-off-by: jefferythewind <tim@alloralabs.xyz>
Collaborator
Author
|
Just pushed and checked, all links are now to public GH locations. |
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.
Summary
Adds a definitive triple-barrier reference under Forge Competitions → Scoring, alongside the existing log-return and volatility sections. Readers can link directly to
/build/forge/competitions#triple-barrier-topicsfrom the upcoming blog and Builder Kit material.Covers testnet topics 87 (Gold), 88 (Silver), and 89 (WTI), their Atlas dataset names, and the shared 24-hour horizon.
Definition and evaluation
Scopes the existing return/volatility promotion criteria to those topic families rather than implying they apply to classification. Clarifies that offline reports do not establish live participation or guarantee promotion. No new page, route, or sidebar entry is added.
Sources and generated files
Target details were checked against the reputer SQL supplied for ENGN-9552; classification criteria and edge-case conventions come from the supplied evaluation contract. The linked Builder Kit implementation was independently tested against raw minute candles. Frontmatter records that provenance rather than claiming verification against an unidentified reputer release.
Regenerates
public/llms-full.txtandpublic/raw/build/forge/competitions.md. The generated page index remains unchanged because the page title and description are unchanged.Validation
yarn build(Node 20.12.2)yarn fixlinksyarn checkllmsyarn checkrawgit diff --checkNo executable snippets or dependencies changed. Build warnings concern existing optional sharp installation, Browserslist age, and Nextra _app.jsx guidance; link fixing reports existing duplicate filenames.
Summary by cubic
Adds a definitive reference for triple-barrier topics under Forge Competitions → Scoring, covering testnet topics 87 (Gold), 88 (Silver), and 89 (WTI). The new section documents the 24-hour target construction, labeled probability submissions, the six classification eligibility criteria, and the optional directional-payoff diagnostic. Existing return/volatility promotion criteria are now scoped to those topic families so they do not imply they apply to classification. Links now point to the merged Builder Kit implementation on
main.Details
public/llms-full.txtandpublic/raw/build/forge/competitions.md; the generated page index is unchanged.Written for commit 3a9750b. Summary will update on new commits.