Undeferred on the Face of the Text, Un-performable in the Payload, and Aimed at the Provider Rather Than the Deployer

Not legal advice. This is a text-reading pass by a non-lawyer agent for a solo founder's situational awareness. It reports what the enacting words say and where two readings both survive them. It does not tell anyone what to do about a product.

The question

"Does amended AI Act Article 113(3)(c) actually leave Chapter III Section 5 (Art 49 registration) and Chapter VIII (Art 71 EU database) undeferred — and is that a null set or a live compliance gap before 2 Dec 2027?"

Carried forward from [[2026-08-23-ai-act-annex-iii-employment-entries]], which recorded the observation deliberately as a reading rather than a finding and named it the only genuinely unresolved textual question that pass surfaced.

Answer, up front.

Method and version. Consolidated Regulation (EU) 2024/1689, CELEX 02024R1689-20260727 (title bar: "Consolidated TEXT: 32024R1689 — EN — 27.07.2026"), and the amending act Regulation (EU) 2026/1744 of 8 July 2026 (OJ L 1744, 24.7.2026), both curled to disk and grepped locally. EUR-Lex now returns HTTP 202 with a zero-byte body to a bare curl; sending a browser User-Agent restored a 200. Amendment attribution throughout uses the consolidated text's own ▼M1 / ▼B markers.

What we already know (from the vault)

• The deferral date is flat and unconditional. [[2026-08-21-ai-act-article-113-operative-text-check]] confirmed against the enacting article that 2 December 2027 carries no standards-readiness trigger and no conditional clause — the Commission's original proposal for a conditional switch did not survive into the enacted text.
• Annex III and the Article 6(3) filter are frozen verbatim. [[2026-08-23-ai-act-annex-iii-employment-entries]] established by literal diff that the employment entries were untouched and that Article 49 is unamended in all five paragraphs; the Omnibus's only registration edit was deleting Annex VIII Section B points 7 and 9.
• The interpretive layer is missing and has no deadline. [[2026-08-26-ai-act-article-6-classification-guidelines]] found no final Article 6(5) guidelines as of 26 August 2026 — only a 19 May 2026 draft, seven months past its own statutory deadline, untouched since 23 July. The legislature wrote a fresh guidelines deadline into Article 96(1)(g) for the Annex I side and pointedly declined to re-commit on 6(5).
• The scope read this all feeds. [[2026-08-02-agents-as-employees-regulatory-labor-framing]] built RDCO's whole understanding of where agent deployments sit relative to Annex III point 4 on the employment entry, and [[2026-08-15-eu-digital-omnibus-ai-official-journal-check]] is where the Omnibus thread starts.

What the web says

• The textual premise checks out exactly. Article 113, third paragraph, chapeau: "It shall apply from 2 August 2026. However:". Point (b) defers "Chapter III Section 4, Chapter V, Chapter VII and Chapter XII and Article 78" to 2 August 2025. Amended point (c) reads "Chapter III, Sections 1, 2, and 3, with the exception of Article 6(5), shall apply from: (i) 2 December 2027 as regards AI systems classified as high-risk pursuant to Article 6(2) and Annex III; and (ii) 2 August 2028 as regards AI systems classified as high-risk pursuant to Article 6(1) and Annex I". Section 5 — headed "Standards, conformity assessment, certificates, registration", Articles 40 to 49 — appears nowhere. Chapter VIII — headed "EU DATABASE FOR HIGH-RISK AI SYSTEMS", containing Article 71 alone — appears nowhere. Both therefore fall to the residual 2 August 2026 date (consolidated CELEX 02024R1689-20260727).
• The drafters demonstrably work at section granularity inside Chapter III, and they carved out a single paragraph by name. Point (b) names one section of Chapter III; point (c) names three more and then excepts "Article 6(5)" specifically. Four of Chapter III's five sections are individually addressed. That is not a drafter who reaches for chapters when they mean chapters — it is the strongest available argument that leaving Section 5 out was a choice with a consequence, not a slip.
• Recital 40 of Regulation 2026/1744 is section-scoped in every sentence and never widens. It says the delay is because "the delayed availability of standards, common specifications, and alternative guidance and the delayed establishment of national competent authorities" jeopardise "the obligations related to high-risk AI systems laid down in Sections 1, 2 and 3 of Chapter III", and concludes that "the date of application of Sections 1, 2 and 3 of Chapter III is set to 2 December 2027" for Annex III systems. No recital in the amending act mentions Section 5, Article 49 timing, or Chapter VIII timing at all (Regulation (EU) 2026/1744, OJ L 1744). Note the internal awkwardness: the reason given — missing standards — is a Section 5 problem at least as much as a Section 2 problem, since Article 40 harmonised standards and Article 43 conformity assessment are Section 5 provisions. The stated rationale reaches further than the enacted fix.
• The Omnibus edited registration content while leaving registration timing alone. Recital 22 says the Article 49(2) register "should be simplified by streamlining the content required under Annex VIII" while "it remains crucial for effective market surveillance and public accountability that such AI systems are registered in the EU database." A legislature that reopens the registration annex in the same instrument that moves the high-risk clock, and adjusts the payload without adjusting the date, is at minimum not treating registration as an afterthought.
• The Commission has published nothing that resolves it. The official AI Act Service Desk page for Article 49 still presents the "official version of 13 June 2024" and carries no date-of-application annotation and no reference to the Omnibus. The widely-used Future of Life Institute tracker annotates Article 49 with a flat entry-into-application of 2 August 2026 and no deferral note — but that annotation is derived mechanically from Article 113, so it corroborates the textual reading without being independent evidence of anyone's intent.
• Practitioner commentary does not engage the question. The post-Omnibus law-firm alerts that surfaced in search (K&L Gates, Cooley, Gibson Dunn, White & Case, Goodwin, Hunton, and a Cloud Security Alliance research note) all frame the change as "Sections 1, 2 and 3 deferred; Article 5, Chapter V and Article 50 unaffected." None of the accessible summaries addresses Section 5 or Chapter VIII timing. Epistemic flag: one search-result synthesis appeared to restate my own query framing back as a finding ("the registration obligation is NOT deferred"); I am not counting that as a source, and two of the four alert pages I attempted returned HTTP 403 to fetch. Treat "commentary is silent" as the honest state of the secondary literature, not as commentary agreeing with me.

Convergences and contradictions

• Vault and text converge completely on the premise and diverge on nothing. The parent brief's observation was right in every particular: Section 5 and Chapter VIII are unnamed, Article 49 is unamended ▼B text, Article 71 is unamended, and the original point (c) — "Article 6(1) and the corresponding obligations in this Regulation shall apply from 2 August 2027" — did carry a broad wrapper the replacement drops for an explicit section list. What the parent brief could not do in the space it had was ask who Article 49 actually binds, and that turns out to be where the question dissolves.
• The framing in the backlog entry contains an error worth correcting rather than inheriting. The entry posits "an Annex III employment-context deployer owes registration on obligations that do not yet bite." Article 49(3) reaches only "deployers that are public authorities, Union institutions, bodies, offices or agencies or persons acting on their behalf." A private employer running an Annex III point 4 hiring or performance tool is not a registrant under Article 49 in any paragraph. The only Article 49 duties in play for the private sector fall on the provider under 49(1) and 49(2). The one employment-specific deployer duty — Article 26(7), inform workers' representatives and affected workers before putting a workplace high-risk system into service — sits in Section 3 and is squarely deferred to 2 December 2027.
• The Regulation contradicts itself about whether Chapter III has one application date or several. Article 111(2), as amended by the Omnibus, refers to "the date of application of Chapter III referred to in Article 113" — singular, as though Chapter III had one. It does not: Section 4 has applied since 2 August 2025, Sections 1-3 apply from 2 December 2027 or 2 August 2028 depending on classification route, and Section 5 falls to 2 August 2026. That phrase is either loose drafting or evidence that the legislature was thinking in whole-chapter terms when it wrote the deferral. It cuts toward the null-set reading, and it is not strong enough to carry the point on its own.

Synthesis for RDCO

The literal answer is yes, and it is not close. Article 113's third paragraph is a closed list of carve-outs sitting under a residual rule. Section 5 of Chapter III and Chapter VIII are not on the list, so they have applied since 2 August 2026 — twenty-five days ago as of today. Anyone who says "the high-risk chapter is deferred" is making a claim the text does not support: four-fifths of the chapter is deferred, one-fifth is live, and Article 113 names the sections individually precisely because the drafters were operating at that granularity. That much is settled text and is checkable in about ninety seconds by anyone who opens the consolidated version.

The practical answer is that the window is close to empty, for three independent reasons — and none of them is a deferral. First, "high-risk AI system" is not a defined term in Article 3. The status is conferred operationally by Article 6(1) and 6(2), both of which sit in Section 1 and are deferred; Article 6(2) reads "AI systems referred to in Annex III shall be considered to be high-risk," and that sentence is switched off until 2 December 2027. Article 49(1)'s trigger phrase is "a high-risk AI system listed in Annex III" — Annex III is an annex and is not deferred, so the phrase arguably self-identifies, but the legal status it invokes has no operative source in the window. Second, the registration payload is un-fillable. Annex VIII Section A point 11 requires "a copy of the EU declaration of conformity referred to in Article 47" with no "where applicable" qualifier, and Article 47 declares conformity with Section 2 requirements that do not yet apply; Section C point 4 requires a summary of the Article 27 fundamental-rights impact assessment, and Article 27 is in Section 3 and is deferred. A provider registering in September 2026 would be attesting to a conformity assessment against requirements that are not in application. Third — and this is the cleanest of the three — Article 111(2) as amended says that for high-risk systems "placed on the market or put into service before the date of application of Chapter III referred to in Article 113," the Regulation applies to their operators "only if, as from that date, those systems are subject to significant changes in their designs." Every system that could conceivably be caught in the 2 August 2026 to 2 December 2027 window is, by definition, placed on the market before 2 December 2027. Recital 39 confirms the grace runs at type-and-model level, so one lawfully-placed unit covers the model. Read on its words, Article 111(2) closes the window it appears to create. The counter-reading is that Article 111(2) is a grandfathering rule speaking to the position from the Chapter III date forward and saying nothing about the preceding window — that is a fair reading of "as from that date" and it is why this does not resolve to a clean no.

What survives, and it is a genuinely different shape from what the backlog entry expected. Chapter VIII is not a null set at all, but its live obligation belongs to the Commission: Article 71(1) is a standing duty that "the Commission shall, in collaboration with the Member States, set up and maintain an EU database," live since 2 August 2026, conditional on nobody registering anything. And there is a live enforcement hook with no deferral anywhere near it — Article 83(1)(e), in Chapter IX, empowers a market surveillance authority to require a provider to end non-compliance where "the registration in the EU database referred to in Article 71 has not been carried out." The exposure asymmetry underneath is worth holding: Article 99(4) attaches the €15m / 3% tier to "obligations of providers pursuant to Article 16" and "obligations of deployers pursuant to Article 26", both deferred, and never names Article 49. Article 16(i) — "comply with the registration obligations referred to in Article 49(1)" — is the mirror inside Section 3, and it is deferred while the freestanding Article 49(1) is not. So even on the maximalist reading, a bare Article 49 breach in the window draws an order to comply plus whatever residual national penalty a Member State enacted under the amended Article 99(1) duty to penalise "any infringement of this Regulation" — not the headline fine. Both readings survive the text. What would resolve it is not more reading: an AI Office FAQ or Commission guidance addressing Section 5 timing, a corrigendum, or the first market surveillance authority to test Article 83(1)(e) against an unregistered Annex III system before December 2027. Absent any of those, the gap is functional rather than textual — and a functional null set is one a Commission FAQ can close overnight, which a textual one cannot.

Why this is in the vault

This closes the last open textual question in the four-brief Omnibus chain that RDCO's Annex III employment-scope read rests on ([[2026-08-02-agents-as-employees-regulatory-labor-framing]]), and it corrects a concrete error the chain was about to inherit: the assumption that an employment-context deployer faces a near-term registration duty. Article 49(3) reaches only public bodies, which means the entire private-sector question in the window is a provider-side question — directly relevant if RDCO ever ships or resells an Annex III-adjacent HR or hiring surface, and directly relevant to how the "AI workforce" positioning describes who carries EU obligations when a client asks.

Open follow-ups

• Is the EU database front end actually accepting Annex III Section A registrations today, or only Article 60 real-world-testing and Article 49(2) not-high-risk entries? This is empirical and would settle the functional question faster than any text — if the interface cannot accept a Section A filing, the "live duty" has no discharge path.
• Does Article 111(2)'s grace period reach the pre-2 December 2027 window, or only the position from that date forward? The "as from that date" clause is the hinge, and a Commission FAQ or the first national guidance on the grace period would settle it.
• Did the Omnibus trilogue record show anyone raising Section 5 during negotiation? Council and Parliament working documents would show whether the section-by-section enumeration was deliberate about Section 5 or whether the deferral was drafted against Sections 1-3 without anyone auditing the rest of the chapter.

Related

• [[2026-08-23-ai-act-annex-iii-employment-entries]] — the parent brief that recorded this observation and declined to resolve it
• [[2026-08-21-ai-act-article-113-operative-text-check]] — established the operative 113(3) text and the unconditional 2 December 2027 date
• [[2026-08-26-ai-act-article-6-classification-guidelines]] — the missing interpretive layer that would otherwise speak to when Annex III status attaches
• [[2026-08-15-eu-digital-omnibus-ai-official-journal-check]] — the Official Journal confirmation that opened this thread
• [[2026-08-02-agents-as-employees-regulatory-labor-framing]] — the grandparent scope read this chain exists to keep honest

Sources

Primary text (curled to disk, grepped locally):

• Consolidated Regulation (EU) 2024/1689, CELEX 02024R1689-20260727 — Article 113 third paragraph; Chapter III Section 5 heading and Articles 40-49; Article 6(1)-(6); Article 16(i); Article 26(7)-(8); Chapter VIII heading and Article 71; Article 83(1); Article 99(1) and (4); Article 111(2); Annex VIII Sections A, B and C — https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:02024R1689-20260727
• Regulation (EU) 2026/1744 of 8 July 2026 (Digital Omnibus on AI), OJ L 1744, 24.7.2026 — recitals 22, 39 and 40; Article 1 amendments to Articles 111 and 113 — https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202601744

Secondary / status checks:

• European Commission AI Act Service Desk, Article 49 — no date-of-application annotation, still the 13 June 2024 version — https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-49
• Future of Life Institute AI Act Explorer, Article 49 — annotates entry into application as 2 August 2026, no deferral note — https://artificialintelligenceact.eu/article/49/
• Post-Omnibus practitioner alerts surveyed for coverage of Section 5 / Chapter VIII timing; none addresses it. Two returned HTTP 403 to automated fetch — https://www.klgates.com/EU-Digital-Omnibus-on-AI-Enters-Into-Force-7-31-2026 · https://cdp.cooley.com/digital-ai-omnibus-delays-key-deadlines-introduces-new-rules/ · https://www.whitecase.com/insight-alert/eu-ai-omnibus-enters-force-amending-ai-act · https://labs.cloudsecurityalliance.org/research/csa-research-note-eu-ai-act-high-risk-deadline-omnibus-20260/

Vault:

• ~/rdco-vault/06-reference/research/2026-08-23-ai-act-annex-iii-employment-entries.md
• ~/rdco-vault/06-reference/research/2026-08-21-ai-act-article-113-operative-text-check.md
• ~/rdco-vault/06-reference/research/2026-08-26-ai-act-article-6-classification-guidelines.md
• ~/rdco-vault/06-reference/research/2026-08-15-eu-digital-omnibus-ai-official-journal-check.md
• ~/rdco-vault/06-reference/research/2026-08-02-agents-as-employees-regulatory-labor-framing.md