Repository navigation
docs: align Phase 2 packing guidance with challenge rules - #44
Merged
Merged
Conversation
spMohanty
force-pushed
the
dev/phase2-packing-policy
branch
from
September 16, 2026 05:37
efb3514 to
46bd1d1
Compare
spMohanty
marked this pull request as ready for review
September 16, 2026 05:53
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
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.
The starter kit links to FlopScope pricing guidance without explaining that the Phase 2 fair-accounting rules also restrict metered packing. Participants can therefore read the shared int8/int16/int32 rate as permission to pack independent values into fewer billed elements.
This adds the Phase 2 packing policy to Allowed Code and makes it discoverable from the README, FlopScope primer, and FAQ. It uses the packed-boolean example already published in the Rules, distinguishes packing from choosing lower precision or quantizing values, and makes the official Challenge Rules authoritative for competition eligibility. It also corrects wording implying that visibility to the meter alone establishes eligibility.
Reference: official Challenge Rules.
Documentation only: no pricing, runtime, or dependency changes. The corresponding correction to FlopScope’s cost-model source is covered by AIcrowd/flopscope#261. The existing cost-model link points to the website page generated from that source.
Validation:
uv run pytest tests/ -q(47 passed; four dtype-promotion warnings),uv run ruff check .,git diff --check, and all four links to the new fair-accounting section resolved locally.Based on freshly fetched
origin/mainat3e1e3b5.