Screen 6 of 6
Case closed
TOS-2025-7741 · no further actions available
Outcome explained: never
Which policy clause matched which action, on which evidence, decided by whom — none of this exists in the record. Only the adjective.
Scene 06 · Oct 9, 09:15 UTC — 23 h 34 m after your appeal, inside the 24 h target
A decision, signed.
Case TOS-2025-7741 · decided Oct 9, 09:15 UTC
Reinstated, effective immediately.
You filed at 09:40 yesterday. I read your statement twice, the architecture note, and the request sample line by line. Three hundred IPs, one key, one identical user-agent: that is not a resold key — that is your server doing its job on launch week. That is not §3.1. That is a good week.
What I changed besides your account: I’ve referred the many-IPs-one-key pattern to the classifier team for human-first review — a proxied consumer app should never trip an auto-action on IP count alone. Your case was the third like it this month; it should be the last.
You can reply to this decision. It comes to me — not to a queue.
Restoration — everything screen 01 listed, closing
- API keys re-enabledElonovo is serving customers again.
- History intactNothing was deleted. Nothing will be.
- Billing resumedReview-period charges voided, as promised on screen 01.
- Case file export unlockedThis entire record is yours, permanently.
The scoreboard
| Wrong UX | Human UX | |
|---|---|---|
| Time until a human read your appeal | never | 5 h 45 m |
| Appeals read by a person | 0 of 3 | 1 of 1, guaranteed in writing |
| Evidence shown to the user | none | signal · confidence · policy · brief |
| Where the case lives | nowhere you can reach | your export, forever |
| The ending | “final” | signed, reasoned, replied to |
None of this was expensive. One specialist, one case, one honest hour. The costly thing is the alternative — measured in people who stop believing a platform can be fair.