By 27 May 2026, PrettyBaby had connected generation to cost control rather than treating them as separate features.
The generation pipeline plans a small static React project, generates one file at a time, validates the complete set, and can make bounded repair calls. Provider-reported usage from planning, file generation, and repair is normalized into owner-visible cost events. Those events feed actual-versus-estimated reporting and preserve the product's zero-markup position.
The same ledger data supports budget policy. A run is checked before it starts, and runtime guards evaluate the latest policy and calculated usage before later provider-call stages. The owner can choose warning, soft-limit, or hard-limit behavior and can pause generation directly.
A guard can stop the next call, but it cannot interrupt a provider call already underway. Soft limits also block until an override confirmation interface exists. The system offers meaningful control without claiming precision it does not have.
← Back to PrettyBaby