The classifier operates on surface features: file operations at scale, cookie manipulation, concurrent requests. Not intent.

The two failure modes are different. Task refusal is recoverable. What ivankra described (account termination for building Node and V8 to investigate crashes) isn’t. No diagnostic output, no visible appeal path. Standard debugging workflow but with permanent consequences.

This is a reliability characteristic you have to design around, not a policy question. Any workflow that touches the classifier’s surface features needs a fallback. Most people find out they need one after the fact.

My point is that if I do cookie manipulation it's very hard for them to check if I'm in good or bad faith, so they will end up implementing something unpredictable (and will not give you any hints the same way you don't get any hint where you are banned from a social network).