Agent Bounds and Stop Rules
Recall the bounds that keep an agentic coding run narrow, attributable, and reviewable.
What is a surface bound? The specific files, modules, call path, or product area the agent may inspect or edit for this run. Without a surface bound, “related” work expands silently. Surface What is a proof bound? The evidence the run must gather or satisfy before editing can be trusted: failing test, log trace, benchmark, or explicit acceptance check. Proof prevents the run from optimizing against vibes alone. Proof “While you are there, feel free to clean up anything adjacent.” A prompt writer is about to widen the run with a casual sentence. That line removes the stop condition. If…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in