docs: align packing guidance with Phase 2 rules - #261
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 cost-model reference called packing “not banned and not judged” and sub-32-bit packing gains “in-bounds”, contradicting the Phase 2 fair-accounting rules.
This removes both statements and makes the official Challenge Rules authoritative for eligibility. It distinguishes accounting advantages from ordinary lower precision or quantization, explains that metering every operation does not grant permission, and qualifies related claims that pricing eliminates packing gains. The competition guide links to the corrected guidance. The website cost-model page is generated from the updated Markdown source.
The documentation audit covered Markdown and MDX guidance across the repository. New policy wording uses the publicly documented packed-boolean example. No runtime, dtype pricing, or dependency changes.
Validation: 11 tests passed (
tests/test_cost_model_page.pyandtests/test_cost_model_coverage.py); generated the website page and confirmed the stale permission statements are absent; checked the guide's target route and packing anchor;git diff --checkpassed.Based on freshly fetched
origin/mainat33cf0c05d3. Companion starter-kit clarification: AIcrowd/whest-starterkit#44.