bound-request-scopelisted

# Bound Request Scope Keep **this request** right-sized: objective, in/out, non-goals, cut lines, and ceremony matched to risk. ## When to use - Scope is expanding, ambiguous, or thrashing - Need an explicit in/out contract before or during implementation - Choosing between direct path vs deeper analysis ## Method (short) 1. **Bind** objective, owning boundary, terminal condition, risk floor, non-goals. 2. **Ground** facts vs inference; acquire only decision-critical evidence. 3. **Choose the smallest complete path** (avoid → reuse → stdlib/platform → existing dep → new only if required). 4. **Scale ceremony to risk** — trivial reversible edits stay direct; irreversible material changes earn deeper analysis. 5. **Do not** turn this into a mandatory report for ordinary work. ## Depth Full procedure, ladders, and examples: [full-method.md](references/full-method.md). Also: [right-sized-agent-engineering.md](references/right-sized-agent-engineering.md), [closure-brief.md](references/closure-brief.md). ## Output Stable scope contract · path chosen · residuals