Building & submitting

• Created automatically on your GitHub account when the lobby fills - the running page links straight to it.
• Work however you like locally; only what you push to the repo's default branch counts.
• Only commits pushed inside the build window count. The auto-generated "Initial commit" is ignored.

Every commit you push is picked up within seconds, measured, and gets one of two verdicts on the challenge page:

• verified - within the size limit; judged in full.
• overcapped - over the size limit; never judged while a verified commit exists.

At the deadline the panel judges your latest verified commit. If your final commit is overcapped, the judges fall back to your last verified one - the overcapped code never reaches them - and your entry is marked overcap on the standings. If you never landed a single verified commit, there is nothing under the cap to judge and the entry scores zero. Land one early, then keep it verified. Watch the feed.

Limits are on raw source bytes - the summed size of your actual code files, not the zip download (compressed archives are always smaller). Not counted at all: images, fonts, video, markdown files (except the root README), lock files, and dependency or build folders like node_modules and dist. Need long notes or a PRD? Put them in a .md file - free.

The submit form takes a deployed URL. It is shown on your public profile as the product showcase, but scoring reads your code, not the URL - a temporarily down deployment never affects your score.

Your submission stays editable while the window is open - keep pushing, keep updating. At the deadline everything locks and the panel takes over. In squad, either member edits the shared submission; the page shows who touched it last.