standards.sgit.ai / eu-ai-act / provisions / art-026-para-05

Article 26(5) — suspension and notification Law

The provision that makes the case against checklists. A checklist renders this as one box, and the box can be ticked with half the obligation unmet.

The operative text is not reproduced on this page. The reading below is derived from secondary sources, which the project flagged against itself before this site existed. A page whose thesis is point at the provision does not get to quote a provision it has not re-derived — so this page publishes the citation, the address, the hashes and the reading, marked as a reading, and points at the authority for the text. The re-derivation status →
Regulation (EU) 2024/1689 · Article 26 · paragraph 5

Article 26(5) — suspension and notification

Operative text not reproduced here — see the note above. Read it in the vault, where it was parsed from Formex XML and hash-verified, or at the authority.

pos d8fc6df65f292bf3 sha not computed — text not re-derived alias art-026-para-05 retrieval: EUR-Lex ELI, via CELLAR Formex XML into the vault

The reading

It is a dual obligation. Suspension without notification is not compliance, and notification without suspension is not either.

Two acts are required of a deployer who identifies a relevant condition, and they are required together. That is not an unusual drafting pattern in EU law, and it is precisely the pattern that a compliance checklist destroys: one row, one tick, and no way to record that an organisation did the operationally obvious half and skipped the one that involves telling somebody outside.

Modelled as a graph rather than a row, the two obligations are separate nodes with separate evidence requirements, and an assessment can be partially grounded — which is the honest state most organisations are actually in.

LimbWhat evidence would ground itTypical state
Suspend useAn operational record showing the system was actually stopped, with a timestampUsually evidenced — it is a visible operational event
NotifyA record of the notification, to whom, when, and what it containedFrequently unanswered. This is the half a checklist loses

Where this is used

This provision is one of five in the worked example, and it is the one that produces a finding of a different kind from the arithmetic one — a finding about a capability that has never been exercised rather than a number that is too small.

Deconfliction. This example is the strongest asset for both this site and risks.sgit.ai. The proposed split: risks owns the register and the acceptance decision; standards owns the provision and the arithmetic. One canonical copy, the other links in. Q1, open →

Crosswalk edges

None

No bridge attaches to this provision, in either direction. Why there are none, and what has to be true before there are →

Citing this provision

https://standards.sgit.ai/eu-ai-act/provisions/art-026-para-05.html
positional hash: d8fc6df65f292bf3   (sha256 of "eu-ai-act/art-026-para-05", first 16 hex)

The positional hash is the canonical identity; the alias is a projection of it. If the Act renumbers, the alias moves and the hash does not — which is what lets a crosswalk drawn today survive a consolidation. The scheme →