Skip to content
Aristeia
Performance & OptimizationHeraclesrecipe

Frame Budget Receipt

Publish the millisecond budget next to the work — a receipt that makes optimisation a claim you can audit.

Built here · no external address

Heracles: Foundational labour. Difficult, necessary technique.

Why it matters

"It runs at 60" is not a receipt. Atalanta demands the budget in writing: target ms, measured ms, and what drops when you miss.

Key techniques

  • Target frame time as a constant beside the study.
  • One-second probe after mount for adaptive quality.
  • Degradation table in the prose, not a footnote.

What to steal

The transferable part.

Print the budget on the page. Agents and reviewers should not guess.

What not to copy

Context-specific or costly.

Do not keep a perpetual fps counter in production chrome.

Inclusion rationale

First Atalanta seed — performance as a chamber, not a vibe.

Technical register

Performance

Probe cost is bounded and self-removing.

Mobile

Budgets differ by tier; publish both.

Accessibility

Numbers are text; colour is secondary to the label fresh/ageing for verification elsewhere.

Study next

Related entries

HephaestusDraw-Call DisciplineTreat draw calls as a published budget — one population, one call — so a forge stays honest when the count climbs.HephaestusHonest LODLevel-of-detail that drops populations and post, not meaning — a degradation path you can defend on a phone.HephaestusThe Instanced ForgeFour thousand ingots drawn in a single call, with the draw-call figure published next to the frame time so the cost of the scene is stated rather than implied.ZeusThe Parametric SingularityA lightning bolt with no model file — a high-segment cylinder displaced along its own normals by 3D noise every frame, orbited by fourteen shards on an underdamped spring.