docs: add recipe verification levels - #178
Merged
Merged
Conversation
Expose the evidence behind each shipped recipe and distinguish canonical E2E gates from scaled proxies and curve-only validation. Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Rockdu
force-pushed
the
docs/recipe-verification-levels
branch
from
August 17, 2026 05:37
1976cbb to
b00a15c
Compare
Rockdu
marked this pull request as ready for review
August 17, 2026 06:04
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.
What
FG,PG,V, andNVevidence levels and classify all nine documented recipes.V: its 2-GPU recipe has a complete curve and no E2E gate; the implementation remains on PR feat: add MiniMax H3 t2va Flow-GRPO support #154.Why
A completed learning curve, a bit-exact canonical E2E gate, and a scaled proxy gate provide different evidence. The labels make that distinction explicit per recipe instead of implying one status for an entire model family.
Validation
git diff --checkmainplus the MiniMax H3 script on PR feat: add MiniMax H3 t2va Flow-GRPO support #154.Files
docs/user-guide/recipe-verification.md— defines the four levels and current inventory.docs/index.md— links the policy and disambiguates feature support from recipe verification.docs/models/sd3/sd3.md— labels both SD3 recipes.docs/models/ltx/ltx2.md— labels the LTX canonical gate.docs/models/wan/wan2-2.md— labels the 5-GPU, 17-GPU proxy, and SFT recipes.docs/models/qwen-image/qwen-image.md— labels the Qwen-Image recipe.docs/models/cosmos/cosmos3.md— labels and corrects the Cosmos3 recipe documentation.docs/models/h3/h3.md— labels the MiniMax H3 2-GPU recipe.Checklist
pre-commit run --all-filespasses — not run; documentation-only changepytest -xis green — not run; documentation-only changepython3 train.py --helpstill parses — no launch flags changedMade with Cursor