REGULATION (EU) 2024/1689 · EU AI ACT

AI Act: from obligations to evidence

A guide for businesses deploying AI agents: understand scope, assign responsibilities and assess controls without confusing architecture with certification.

Sources consulted: · AI-assisted technical synthesis; no legal review claimed.

Start with use. Then assess the control.

01 · PURPOSE

Not every agent is high-risk

Classify by purpose and context under Article 6 and its annexes. Assess prohibitions and transparency separately; autonomy alone does not determine the category.

Art. 6 →
02 · PROVIDER

Who puts it into service

Developing or commissioning a system and putting it into service under your name may make you a provider. Review substantial changes and changes of purpose along the value chain.

Art. 3 / 25 →
03 · DEPLOYER

Who uses and oversees it

A deployer uses the system under its authority. For high-risk use, review instructions, accountable people, monitoring and log retention.

Art. 26 →

BABYLON can support technical controls. Classification, documentation, organisation and conformity assessment depend on the system and its use. The AI Act does not mandate Touch ID or a particular database.

From an obligation to a testable claim

Indicative technical mappings for high-risk systems, not a conformity assessment. States come from the published snapshot; runtime tests have not been repeated here.

Evidence snapshot: 2026-10-18T18:15:12.880Z · Tests, divergences and reproduction
ObligationRelated controlAvailable evidenceLimits
Art. 9 · Risk managementAdversarial tests and failure review.heterogeneous_verification_quorum
verified_local
A technical test suite cannot replace an ongoing organisational process.
Art. 12 · Automatic loggingReceipts linking operations and outcomes.cose_ed25519_receipt
verified
Receipt integrity does not prove completeness or absence of effects.
Art. 14 · Human oversightAuthorisation bound to the action.secure_enclave_p256
verified_local
Biometrics do not prove understanding; suitable people, authority and interfaces are required.
Art. 15 · Accuracy, robustness and cybersecurityStopping and containment on failure.inv_04_fail_stop_halt
verified
Stopping does not prove accuracy, fairness or coverage of all threats.

CORTEX: memory · BABYLON: control · NEMESIS: verification layer. A “verified” state is limited to its test and configuration.

Timeline: phased application

Timeline checked against Article 1, point 40, of Regulation (EU) 2026/1744, amending Article 113 of the AI Act. Distinguish the general date from specific high-risk provisions. Also review the Article 6(5) exception, prohibitions with their own dates and Article 111 transitional rules for your case.

  1. Initial provisions: Chapters I and II, subject to later exceptions in Article 113.

  2. Governance and general-purpose model rules, with exceptions and transitional arrangements.

  3. General application date; this is not one deadline for every obligation.

  4. Article 6(2) / Annex III high-risk rules: date set by amended Article 113.

  5. Article 6(1) / Annex I high-risk rules: date set by amended Article 113.

Article 113 and exceptions → · Commission information →

AI Act: responsibility, control and evidence

Sources and review scope

This content distinguishes law, technical interpretation and product evidence. It is not legal advice or certification. Specific obligations require assessment of purpose, role and applicable regime.