Who owes what
- Provider: builds the oversight measures into the system before placing it on the market and states them in the instructions for use (Article 14(1), 14(3)(a), 13(3)(d)).
- Deployer: assigns oversight to natural persons with the competence, training, authority and support to exercise it (Article 26(2)).
Read Article 14
Article 14 of Regulation (EU) 2024/1689, the EU AI Act.
Where the controls stop
- Output guardrails do not run on streaming responses.
- Max. execution time excludes tool execution, and a request value overrides the agent manifest.
- Tool approval is not enforced on
POST /v3/router/responses, and Allow always removes later pauses. - No control here halts a run already in flight.
Records
Audit logs record control-plane changes; traces and annotations record per-run actions and human decisions. Those are the logs of Article 12, kept under Article 26(6). A record shows an action was taken, not that oversight was effective.Change control
Prompts and model deployments are versioned and audited, so a change ties to the person and time that made it. A change to a deployed high-risk system can be a substantial modification: the party that makes it becomes a provider (Article 25(1)(b)), with the obligations of Article 16 and a new conformity assessment under Article 43(4).What Orq.ai does not decide
- The high-risk classification and the acceptance thresholds.
- Who oversees, and with what competence, training, authority and support.
- Whether to suspend use and notify under Article 26(5).