Flows workflow logoFlows
Rate and Blast-Radius Limits for Destructive Tools
0/4 steps0%

Step 1 of 4

Set the budgets from real usage

Caps must fit normal work and catch abnormal work.

First time here? Paste the Context Pack first so the AI understands your project - open it from the header above.

Prompt Capsule
Define the budget scheme with data. Measure from recent normal sessions: files modified per task (distribution), deletions per task, lines changed, commands per hour. Set budgets at generous multiples of normal (e.g. p95 x 3) so legitimate work never trips them: per-task and per-15-minute-window caps for files-modified, files-deleted (much stricter - deletions are rarer and riskier), total lines changed, and shell commands. Define the escalation ladder per budget: at 60% - log; at 85% - inline warning shown to user; at 100% - pause requiring review-and-continue. Write the scheme into harness config with the measurement basis documented.
Paste into EmergentFull Build: complete implementation prompt with explicit requirements

Quick is short. Full Build is recommended for most steps. Strict forces real logic when the AI keeps faking output.

Actual change check

Expected after this step

Data-derived budgets with an escalation ladder in config.

Should NOT happen

  • An existing feature broke
  • A button only logs to console
  • Data disappears after refresh
  • Errors fail silently with no visible state

This is what should exist before you continue. If reality does not match, do not move on.

Track what changed, failed, or needs follow-up. Notes export with the flow.

Made with Emergent