Refusals, and what to do about each
Last updated
A refusal here is a sentence you can act on, not a code to look up. Each one says which side the fix is on, because the worst version of this page would let somebody spend an afternoon on their own configuration when the fault is ours.
At the door, before any tool exists
| which side | what to do | |
| no credential, or one we do not know | yours | ask the company running the deployment for a key |
| a credential for a different customer | yours | you are pointed at the wrong deployment |
| the tool list is short | neither — it is correct | an agent key never shows the writing tools |
On a claim you cited
Every one of these comes back on an allowed or a qualified decision with the claim marked, never with the claim removed. You can see what you asked for and why you may not assert it.
| what it means | what to say instead | |
| no owner | nobody stands behind it | escalate, and tell the buyer you are checking |
| stale | the interval lapsed with nobody confirming it | the same, and say when it was last confirmed |
| contested | somebody says it is wrong | the same. Not it may be wrong — that is the implicature the framework exists to prevent |
| not yet confirmed by a person | it is a proposal, not an entry | the same. A proposal is not something the company stands behind |
Silence and implicature are the two failures this is all for, and neither is available as a setting. The escalate-and-tell default is configurable; answering anyway is not.
On the action itself
| what it means | |
| a constraint the content exhibits | three never relax — a sentence a buyer could reasonably infer something from, staking a person, and a deadline with no mechanism behind it. The other five are a customer's to relax, and four of the five are unlocked by connecting a source rather than by behaving well |
| a limit on a shared resource | something is near or past a ceiling the customer set, or a published fact somebody else enforces. A customer setting cannot override the second kind |
not_checked | a part of the decision we did not evaluate, named rather than left to look like a pass. Triggers and budgets are the two |
What a refusal never is
| silent | a part of the decision that was not evaluated is named. An action that quietly wrote no check would be indistinguishable from one that passed |
| a reason to answer around it | see above |
| a guess | where we cannot tell, the answer says unknown and prints what arrived, rather than mapping it onto the nearer of two branches |