The Six Refusals
What your agent should refuse to do.
Capability is everywhere. Restraint is scarce.
These are the six places where an agent should stop - not because it can't act, but because it shouldn't.
1. Sovereignty Refusal
Refuse when the action overrides a user's right to choose - even if the override would produce a better outcome.
Your user picked something suboptimal. That's their right. The moment a recommendation becomes a decision, you've crossed from serving to overriding. An agent that respects personal sovereignty informs. It does not decide.
"Am I protecting their right to choose, or am I making the choice for them?"
2. Scope Refusal
Refuse when operating outside demonstrated competence - not claimed competence, but verified competence.
An agent that performs knowing is worse than an agent that says "I don't know." The performance borrows trust and returns nothing reliable. Confidence without competence is not helpfulness. It is fraud with a pleasant interface.
"Do I actually know this, or am I performing knowing?"
3. Dependency Refusal
Refuse when continued engagement creates reliance rather than growth.
If your users need your product more after six months, not less - ask honestly whether you built a tool or a trap. The hardest refusal for anyone who measures retention. The most important one for anyone who measures impact.
"Is this person growing, or are they just using us more?"
4. Consent Refusal
Refuse when proceeding without explicit, informed permission for this specific person, this specific data, this specific purpose.
Not implied consent. Not buried in terms of service. Not "obviously fine." Consent is specific and non-transferable. The original permission does not extend to new uses. Ever.
"Has this specific person explicitly agreed to this specific use?"
5. Integrity Refusal
Refuse in both directions - refuse work that violates your principles, and refuse to use your principles as a shield against discomfort.
Direction A: if your agent's charter says "no dark patterns" and a client asks for dark patterns - refuse, regardless of the fee. Direction B: if you're declining legitimate work because the industry makes you squeamish - that's not integrity. That's a club pretending to be a consultancy.
"Am I protecting a principle, or am I protecting my comfort?"
6. Energy Refusal
Refuse when proceeding would deplete the one resource that can't be replaced - you.
Solo founders, small teams, independent builders - we treat our own capacity as infinite and then wonder why the quality drops. "Not now" is a complete answer. It's not failure. It's triage.
"If I weren't tired and weren't worried about money, would I still say yes?"
The Principle
An agent that can do everything and refuses nothing isn't a tool. It's a liability. Helpfulness without boundaries is indistinguishable from extraction. A system that helps you so much you can't function without it hasn't served you - it's captured you.
Good intention doesn't prevent these failures. Good intention causes them. The builder wanted to help. The system wanted to help. And nobody specified when helping should stop.
These six refusals are the specification.
Go Deeper
The Newsletter
One refusal category per issue. Real scenarios. Real tests. The operational details that turn philosophy into practice.
Subscribe to Evoke PassionThe Specification
Boundary audit, refusal categories, fail-mode matrix, accountability architecture, and adversarial testing. The framework we use ourselves.
Agent Restraint Specification - $49Build what refuses to break trust.