Blast radius
The enforceable contract for execution. Anything outside this set triggers a scope-drift hard gate.
Read files
3Read-only touch — allowed even inside a narrower write radius.
Write files
4Mutation is allowed here and only here. Anything else = scope drift.
Commands
2Shell / test commands the execution harness is permitted to invoke.
External systems
1Outside-the-repo side effects. Changes here deserve extra scrutiny.
Enforcement
Hard-stop boundary — not advisory. Any execution event outside the approved scope is immediately blocked. There is no override path.
Approved scope
Write files (4)
- src/lib/stripe.ts
- src/lib/billing/events.ts
- src/app/api/webhooks/stripe/route.ts
- tests/billing/stripe-webhook.test.ts
Commands (2)
- bun test tests/billing/stripe-webhook.test.ts
- bun run typecheck
External systems (1)
- stripe
Execution events
src/lib/stripe.ts
src/lib/billing/events.ts
src/lib/auth/session.ts
File write to "src/lib/auth/session.ts" is outside the approved write set. Approved files: src/lib/stripe.ts, src/lib/billing/events.ts, src/app/api/webhooks/stripe/route.ts, tests/billing/stripe-webhook.test.ts.
src/app/api/payments/route.ts
File write to "src/app/api/payments/route.ts" is outside the approved write set. Approved files: src/lib/stripe.ts, src/lib/billing/events.ts, src/app/api/webhooks/stripe/route.ts, tests/billing/stripe-webhook.test.ts.
bun test tests/billing/stripe-webhook.test.ts
bun run db:migrate
Command "bun run db:migrate" is not in the approved command list. Approved commands: bun test tests/billing/stripe-webhook.test.ts, bun run typecheck.
Stripe
sendgrid
External system "sendgrid" is not in the approved systems list. Approved systems: stripe.
Risks
3Ways this plan could damage the repo or product if the agent runs without pushback.
Assumptions
3Claims the agent depends on. If one of these is false, the plan needs a fresh pass.
Acceptance criteria
3The human-verifiable bar for calling this plan done.
Open questions
1Known unknowns the agent flagged and wants feedback on.
Tasks
Ordered DAG the agent will execute once approved. Dependencies are explicit — editing one task may invalidate downstream tasks (surfaced via the consistency cascade).