payload-budgetslisted

# Payload budgets ## The constraint Bytes cost money that the user paid in advance, arrive over a link that drops, and land on a device that is already full. A download that fails at 80% is retried on a prepaid bundle, which means the second attempt costs real money for nothing. Storage is the other half: on a 16GB device sitting permanently near full, your app is competing for space with photographs of the user's family, and it will lose. The number that matters is the **cold, uncached, first-attempt download on a congested cell**. Every other number flatters you. ## Hard rules | ID | Rule | Severity | |---|---|---| | SIZE-001 | Declare a byte budget per platform before writing the feature. | critical | | SIZE-002 | Keep the Android initial download at or below 15MB. | critical | | SIZE-003 | Budgets are enforced by CI and fail the build when exceeded. | critical | | SIZE-004 | Measure the cold-cache first visit on a tier C device, not a warm reload. | warning | | SIZE-005 | Serve images sized to the rendered box, in a modern format, responsively. | warning | | SIZE-006 | Cap first-load JavaScript on the critical path at 200KB compressed. | warning | | SIZE-007 | Every third-party script has a named owner and counts against the budget. | warning | | SIZE-008 | Load secondary features on demand rather than at install or first paint. | warning | | SIZE-009 | Never block first paint on a web font. | warning | | SIZE-010 | Budget the installed storage footprint, not only th