Is your AI wrapper a "High-Risk" system? (A dev's guide to the EU AI Act)

If you're building AI features right now, you and your team are probably arguing about the tech stack: Should we use LangChain or LlamaIndex? Should we hit the OpenAI API or run Llama 3 locally? Here is the harsh truth about the upcoming EU AI Act: Regulators do not care about your tech stack. They don’t care if it’s a 100B parameter model or a simple Python script using scikit-learn. The law only cares about one thing: Your use case. Why This Matters Your use case determines your risk category . If your product falls into the High-Risk category, you are legally required to implement: human oversight risk management systems detailed technical documentation (Annex IV) Getting this wrong doesn’t just mean “non-compliance”. It means: failed procurement audits blocked enterprise deals serious regulatory exposure 🔍 5 Real-World AI Scenarios Here are practical examples to help you understand where your system might fall. 1. AI Chatbot for Customer Support Use case: routing tickets answering