AI Cost And Risk Gate
Estimate task size and risk so agents can choose the right amount of context,
Purpose
Estimate task size and risk so agents can choose the right amount of context, validation, and caution.
This document is not permission to enter Slicing Mode by default. Large task size alone is not enough to trigger Slicing Mode. RFC, ADR, phase planning, and proceed gates are manual opt-in only unless a high-risk task truly cannot be implemented safely without user confirmation.
Default Outcome
For normal Prox OS work, use Direct Implementation Mode:
- read only the minimum relevant context;
- implement in the same run;
- run relevant checks;
- summarize after implementation.
For broad UI mock/product-surface work, use UI Incubation Mode:
- visible UI/code progress first;
- no RFC by default;
- no proceed gate by default.
Size Labels
Size labels are planning hints, not automatic gates.
| Level | Typical traits | Default action |
|---|---|---|
| S | One file or a few lines in one module. | Implement directly. |
| M | 2-8 files in one app/package, local UI or docs behavior. | Short internal plan, then implement directly. |
| L | Multiple modules/packages or lifecycle/routing/state impact. | Implement directly if safe; recommend Opt-in Slicing Mode only when risk warrants it. |
| XL | Broad architecture/platform migration or unbounded request. | Recommend Opt-in Slicing Mode, but do not enter it unless the user confirms. |
High-risk Triggers
Recommend Opt-in Slicing Mode when work involves:
- auth, login, or sessions;
- permissions or security boundaries;
- payment, Stripe, live billing, entitlements, or refunds;
- database schema, migrations, production data, or destructive data changes;
- API contracts or generated clients used across packages;
- Cloudflare deployment pipeline or production infrastructure;
- app runtime protocol, app contract redesign, or microfrontend isolation;
- destructive refactors, deleting large code areas, or irreversible migrations;
- multi-user collaboration contracts;
- legal/compliance flows with irreversible assumptions.
Recommendation means:
This looks high-risk. I recommend Opt-in Slicing Mode, but I will not enter it unless you explicitly confirm.Explicit Opt-in Phrases
Only enter Opt-in Slicing Mode when the user explicitly says things like:
- "start slicing mode" or the same request in the user's language;
- "start RFC-style development" or the same request in the user's language;
- "write an RFC first";
- "write an ADR first";
- "RFC first";
- "ADR first";
- "phase plan only";
- "planning only, do not change code";
- "do not change code";
- "proceed-gated";
- "wait for my confirmation between phases";
When activated, announce it at the start of the response.
Do Not Slice By Default
Do not start RFC/slicing/proceed-gated work by default for:
- UI incubation;
- 30+ app placeholder, app card, or route surface work;
- Join Us, Hola, Pricing, Founder Suite, or App Store mock UI;
- docs index cleanup;
- lightweight roadmap sync;
- Storybook stories;
- copywriting;
- local mock UI;
- app registry display updates;
- design token documentation;
- non-destructive refactors.
Document Length Budget
- Preflight plan: max 30 lines.
- Slice plan: max 250 lines.
- RFC / ADR: target 300-500 lines.
- If an RFC exceeds 500 lines, split it into a main decision doc plus appendix.
- Phase 1 should be the first visible implementation slice unless the user asked for planning-only.