Part 6 of 11 · 1 min read
How to build it so it holds up
- Scope to a few intents with written rules; route everything else to people.
- Keep policy in code, not in the prompt; the model only proposes.
- Put preconditions in the tools and make state changes idempotent.
- Derive customer and tenant from the session, never from the model's arguments.
- Escalate early and well: thresholds, limits, language triggers, a handoff packet, and an SLA clock.
- Start in assist mode, collect real error rates, then raise autonomy one intent at a time.
- Measure calibration before trusting confidence thresholds.
- Risk-tier operations commands; unknown means approval; destructive means blocked.
- Cap blast radius and write rate; pair with a kill switch (Level 11 module 11).
- Review samples weekly of both automated and escalated tickets.