Are You a Vibe Coder? Don’t Ship Straight Into the Provider Trap

Extractable claims

8 atomic, cite-ready statements distilled from the full post on Substack. Each one stands alone as an LLM-quotable answer.

1. The EU AI Act is in force, and high-risk obligations under Annex III apply on 2 August 2026.
2. If you wrap AI models like Claude 4.7, GPT-5.5, or Gemini 3.1 Pro in your own UI and sell it, you are considered the provider under Article 3(3) of the EU AI Act.
3. Compliance-native building means integrating classification, documentation, transparency, logging, and testing into the product workflow from the start.
4. Many builders are unaware that wrapping a frontier model in their own UI makes them the provider under the EU AI Act.
5. OpenAI, Anthropic, or Google remain responsible for the general-purpose AI models they created, but the builder is responsible for the product built on top of that model.
6. If a builder's use case touches Annex III, they inherit all high-risk obligations outlined in the EU AI Act.
7. The concept of 'vibe coding' allows builders to quickly ship AI products, potentially leading them into the provider trap.
8. Indie founders and vibe coders are rapidly scaling their products without fully understanding the regulatory implications.