Redline

Always read the usage meter fresh before starting heavy work; a reading over 90 minutes old means no-go.

Never go over any usage cap; when unsure, start nothing and say why.

Run one heavy paid job at a time, and prove each change actually ran, not just that tests passed.

Risky work (money data, secrets, health data, backups) is held for the owner and never auto-run.

Never use pay-as-you-go credits or extra paid models to get past a cap unless the owner said so.

Rewrites of the pacer's own rules wait for the owner's approval, and roll back automatically if the next week does worse.

Use before starting any build or other heavy task on a weekly usage meter, to decide go/no-go and the biggest slice that fits, at each weekly reset to write a retro whose adjustments tune next week, and monthly to propose a tested rewrite of its own rules.

Use after the pacer verdict, before starting a task, to pick the cheapest route, pool and model that can do it well, log the result, and learn which routes pay off.

Use as the first conversation of a newly installed Redline bot, to learn the owner's usage meter, limits, tools, backlog and rules, then set up pacing state and the build loop.