Run a local report
Run promotion gates
Each live script requires an explicit authorization flag, Modal credentials, a clean source revision, fixed placement and resources, retries set to zero, and a fresh output directory.
Read the canonical benchmark procedure before a live run. It defines the exact flags, timer boundaries, cost ceiling, cleanup, sanitization, and promotion rules.
Keep measurements comparable
- Use one exact source commit and a clean worktree.
- Record requested and observed placement.
- Hold resources, Image, ingress, HTTP version, input backend, screenshot options, and warm capacity constant.
- Interleave matched arms according to the preregistered schedule.
- Keep failures. Use no replacement samples.
- Report cleanup failures and survivors.
- Separate cold allocation, startup, Function dispatch, borrow, and warm operations.
Store evidence safely
Write raw output under ignoredbenchmark-results/. Remove endpoint URLs, resource IDs, tokens, screenshots, typed text, clipboard text, and raw failure content before promotion.
Publish only a sanitized artifact accepted by its repository validator. Keep dated reports and artifacts immutable.
