Speedup Proof

Treat every optimization as a falsifiable experiment: inspect first, propose one exact change, obtain explicit approval, preserve behavior, measure a baseline, implement only the approved change, verify correctness, measure again, and keep only a result supported by evidence.

Require approval before edits

Treat invocation of $speedup-proof as consent to inspect the project, never as consent to modify it.

• Always begin with read-only analysis, even when the initial request says optimize, apply, fix, implement, or use prove mode.
• Do not create or edit project files, benchmark harnesses, tests, reports, dependency files, configuration, worktrees, or generated artifacts before the approval checkpoint.
• Do not install dependencies, run formatters, execute migrations, or run commands that can mutate project state before approval.
• Never interpret broad phrases such as optimize this codebase, do it, or a bare skill invocation as approval for an unseen patch.
• Ask for approval only after showing a concrete bounded proposal. Do not ask for blank-cheque approval before analysis.

Present this checkpoint and stop:

## Proposed speedup