Repository navigation
docs: align limitations with published fidelity release - #16
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.
The limitations page still described the current image as unpublished and described all FP4-Local prefill as W8A8. It now identifies the published digest and distinguishes routed W4A4 prefill from the MXFP8 projection/shared-expert path in engine
63bebfa6.Historical measurements retain their date and scope. The page also states that F32 HC/PLE norm weights are still rounded to BF16 and TP1 validation remains outstanding.
Validation: 34 tests, static installation checks and 1,188 receipt hashes passed. Documentation only; source, image, profiles and raw results are unchanged.