EU AI Act compliance, built into the platform

Article 12 of the EU AI Act takes effect on the second of August, 2026. Every provider of a high-risk AI system has to keep automatic event logs throughout the system's lifetime. Two minutes below: the articles we cover, and how.

Why this video, and why now

The 2 August 2026 deadline is becoming the regulator's anchor in every EU enterprise procurement conversation about AI agents. CISOs are asking the same question across banking, insurance, defence, and the public sector: which articles do you actually deliver evidence for, and how?

So we filmed the answer. Article by article, what the HookBus Enterprise Suite produces. No "compliance theatre". No claim that buying our product makes your organisation compliant. Compliance is your programme. Our job is to produce the evidence the act requires, in the format your assessor expects.

Articles we stake

What we don't claim

We do not stake compliance to articles where we do not deliver direct evidence. Specifically:

• Article 10 (data and data governance). The training-data provenance and quality story sits with the model provider, not the bus.
• Article 11 (technical documentation). We can hand you our spec and architecture, but the high-risk system documentation set is the provider's responsibility.
• Articles 16+ (provider quality management, conformity assessment, post-market monitoring). Programme work, not infrastructure.

Coverage of the articles we do stake depends on what your AI runtime exposes through its lifecycle hooks. We are leading the work with AI providers to ensure those hooks deliver what the act requires. Our reading of the four-role split (provider, deployer, importer, distributor) is on the EU AI Act page.