No. All three miss us, and two of the three impose no AI-content labelling duty on anybody. The parent verdict stands unchanged.
Not legal advice. This is an operational read of primary text by a non-lawyer. A real EU media lawyer should see this before it becomes commercial policy, and the place that matters most is the European Media Freedom Act "press publication" question in follow-up 2.
Emphasis added in every quoted passage below is mine, not the source's.
The question
Verbatim: "Do the DSA, the Political Advertising Regulation, or the European Media Freedom Act impose AI-content labelling duties that the AI Act Article 50(4) editorial carve-out does not reach?"
Context: [[2026-09-03-ai-act-article-50-transparency-guidelines]] produced the only concrete change to a shipping RDCO surface in the whole AI Act thread. Sanity Check needs a publicly findable editorial-responsibility statement, naming a person or function with contact details, to hold the Article 50(4) carve-out. That verdict rests on the carve-out being the only labelling duty in play. This brief tests the three instruments that could break that assumption: the Digital Services Act (Regulation (EU) 2022/2065, "DSA"), the Political Advertising Regulation (Regulation (EU) 2024/900), and the European Media Freedom Act (Regulation (EU) 2024/1083, "EMFA"). It also reads the Commission Article 50 guidelines sections on interplay with other Union acts that the parent pass skipped.
Answer, up front
| Instrument | AI-content labelling duty? | Duty-bearer | Editorial exemption? | Does it reach RDCO? |
|---|---|---|---|---|
| DSA (Reg. (EU) 2022/2065) | No. Art. 35(1)(k) is a listed example of a risk-mitigation measure, not a standalone labelling rule, and on its own wording it covers image, audio and video but not text | Providers of very large online platforms (VLOPs) and very large online search engines (VLOSEs), per Art. 35(1) | None, and none needed: Art. 2(2) excludes any service that is not an intermediary service | No. Own-content publishing is not an intermediary service at all; separately, VLOP designation needs 45 million monthly EU recipients |
| Political Advertising Reg. (Reg. (EU) 2024/900) | No. The only two artificial-intelligence references in the whole Regulation are in Art. 19, and they are about AI used to target or deliver an ad, not AI used to create content | Political advertising publishers, sponsors, providers of political advertising services | Yes, Art. 1(2), and broader than Art. 50(4) in one respect: no publication-of-identity condition is attached | Not applicable. RDCO runs no political advertising. One forward trip-wire, below |
| EMFA (Reg. (EU) 2024/1083) | No. Zero content-labelling provisions. Art. 18(1)(e) is the inverse: a declaration that you do not publish AI content without human review | Art. 18 duty falls on VLOP providers; Art. 6(1) falls on media service providers but is service-level transparency, not content labelling | The concept runs the other way: EMFA Art. 2(8) is one of the sources the Commission tells us to read Art. 50(4) against | No labelling duty. Whether RDCO is a "media service provider" owing Art. 6(1) is genuinely open, and that duty is about ownership and contact details, not AI |
Verdict on the parent brief: STANDS, unchanged. No instrument examined here adds an obligation. The parent's single shipping-surface action item, the ¶138 editorial-responsibility statement, is still the right one and still the only one on a surface. The EMFA does not add a second duty; what it offers is a possible reuse of the same document, conditional on two things RDCO probably cannot satisfy (below). I am not manufacturing a new action item to make this brief feel productive.
What we already know (from the vault)
- [[2026-09-03-ai-act-article-50-transparency-guidelines]] established the live position: Art. 50(2) marking is a provider duty and misses RDCO; Art. 50(4) second subparagraph is a deployer duty and lands on Sanity Check; the editorial carve-out is available in substance but the guidelines ¶138 publication requirement is unmet. That brief's own third follow-up is this question. It also carried two policy items alongside the surface change: no substantive agent rewrites after founder sign-off (guidelines ¶136 voids the exception), and watch the provider/deployer role line.
- The same brief established that territorial scope does not save a Florida company. Guidelines ¶13 treats posting on the globally accessible internet as foreseeing use in the Union. That finding is load-bearing here too, and it is why the DSA and EMFA answers below turn on role rather than on geography.
- [[2026-08-27-ai-act-113-3c-registration-deferral-gap]] and [[2026-08-21-ai-act-article-113-operative-text-check]] both established the thread's recurring pattern: in this body of law, "who are you" resolves more questions than "what did you publish."
- [[revival-strategy]] sets the Sanity Check monetization path at third-party sponsorship, with sponsor outreach beginning at 1,000 subscribers. That plan supplies the one forward-looking trip-wire in this brief.
- Gate-check re-run via qmd on 2026-11-01: the vault still has five AI Act research briefs and no document touching the DSA, Regulation (EU) 2024/900 or the EMFA. This is first coverage for all three.
- No vault record shows the ¶138 editorial-responsibility statement has been published since 2026-09-03. The action item appears still open; that is a statement about vault records, not a check of the live surface.
What the web says
- Sekwenz, When Is Content "AI-Generated Enough"? Labelling Synthetic Media under the Digital Services Act and the AI Act (arXiv 2609.07727, Sept 2026) reads Art. 35(1)(k) exactly as the text reads it: it "identifies, among the measures available to mitigate systemic risks under Article 34 DSA," measures ensuring prominent markings. And directly on the over-reading question: "Neither Article 50 AI Act nor Article 35(1)(k) DSA makes every use of AI subject to the same visible disclosure requirements."
- Secondary framing is split. Several law-firm and vendor pieces surfaced in search describe Art. 35(1)(k) as an obligation on large platforms to label deep fakes; others call it a mitigation option. None of them was fetched and read, so they are not relied on here. The operative words "Such measures may include" settle it against the stronger framing anyway: the duty is to mitigate identified systemic risks, and labelling is one listed way to do that.
- The Commission adopted guidelines on the Article 18(1) EMFA declaration functionality on 6 February 2026, published as Communication C/2026/901 (OJ C, 11.2.2026). The European Board for Media Services welcomed them on 22 April 2026 and called on VLOP providers to implement the functionality.
- The two European publisher associations, the European Magazine Media Association (EMMA) and the European Newspaper Publishers' Association (ENPA), argued in the Article 18 consultation that AI-supported functionality such as weather updates or market tickers inside a newspaper should not disqualify the rest of the editorial content from the Art. 18(1)(e) declaration. Position, not law, but it signals where the sector reads the line.
- One secondary source that would have been directly on point, Taylor Wessing's The DSA, the EMFA and the AI content conundrum, returned HTTP 403 and the retry was blocked by the auto-mode classifier as bot-check circumvention. Flagged, not worked around. Its absence does not change the primary-text answer.
Convergences and contradictions
- Convergence across all four instruments, and it is the whole finding: among the instruments examined, AI Act Art. 50(4) second subparagraph is the only human-visible AI-origin labelling duty that attaches to text and lands on a publisher. Art. 35(1)(k) DSA covers image, audio and video on its own wording and is a platform measure. Regulation (EU) 2024/900 labels the advertisement, not the AI. The EMFA labels nothing. (Art. 50(2) AI Act does cover text, but it is machine-readable marking and it binds the system provider, which the parent brief already settled.)
- Convergence the parent brief could not have seen: guidelines ¶140 says Art. 50(4) editorial responsibility "should therefore be interpreted in line with the existing media acquis," pointing at EMFA Art. 2(8). Read alone that would be unhelpful, because Art. 2(8) defines editorial responsibility "for the purposes of the provision of a media service," which is the status follow-up 2 leaves open. The stabilising clause is the rest of ¶140, which the parent brief never had: the concept "remains a distinct concept that may also apply in broader contexts and to other deployers, so long as they assume editorial responsibility for the text publication." That sentence is what keeps the carve-out available to a publisher who is not a media service provider.
- Contradiction inside the guidelines themselves, and it is operationally useful. ¶138 says the editorial-responsibility identity and contact details may be published through "a website's terms and conditions or other user-facing legal information." ¶142, on the Art. 50(5) horizontal requirement, says information is not clear and distinguishable where it is "part of terms of use that are often not read by users." These are not in conflict once separated: ¶138 governs where you publish who is responsible, ¶142 governs where you put the AI-origin label itself. The legal page is fine for the first and disqualified for the second.
- Negative finding worth recording: the 51-page Article 50 guidelines mention Regulation (EU) 2024/900 zero times. The guidelines carry five sections titled "Interplay with other Union legal acts" (3.3, 4.4, 5.3, 6.1.5 and 6.2.5; 5.3 concerns emotion recognition and biometric categorisation and is irrelevant here). Across them the Commission discusses the Unfair Commercial Practices Directive, the Consumer Rights Directive, data protection law, criminal-procedure directives, the DSA at length, and the EMFA. The Political Advertising Regulation never appears. The Commission does not see an interaction there, and neither do I.
Instrument by instrument, on the operative text
DSA: wrong architecture, not just wrong threshold
Two independent walls, and the first matters more than the headline threshold.
Wall one, Article 2(2): "This Regulation shall not apply to any service that is not an intermediary service or to any requirements imposed in respect of such a service, irrespective of whether the service is provided through the use of an intermediary service." Intermediary service is closed-listed in Art. 3(g) as mere conduit, caching, or hosting, where hosting is "the storage of information provided by, and at the request of, a recipient of the service." Sanity Check and the rdco.dev sites publish RDCO's own content at RDCO's own request. Recital 18 confirms the direction: the liability exemptions are unavailable for "information provided not by the recipient of the service but by the provider of the intermediary service itself, including where the information has been developed under the editorial responsibility of that provider." Own editorial content sits outside the framework rather than being exempted within it. That is why the DSA has no Art. 50(4)-style editorial carve-out; it never needed one.
Wall two, the scale thresholds, which only matter if wall one somehow fell: Art. 35(1) binds "providers of very large online platforms and of very large online search engines," and Art. 33(1) sets that at 45 million average monthly active recipients in the Union plus a Commission designation decision under Art. 33(4). Art. 19 separately excludes micro and small enterprises from the whole online-platform section. A one-person newsletter is not within several orders of magnitude.
And the duty itself is weaker than its reputation. Art. 35(1): providers "shall put in place reasonable, proportionate and effective mitigation measures, tailored to the specific systemic risks identified pursuant to Article 34 ... Such measures may include." Point (k) is item eleven on a menu. Its material scope differs from Art. 50(4) in two directions. Guidelines ¶126 names the two distinctions it sees: a broader material scope, because point (k) catches content manipulated "regardless of the technologies used," and a different personal scope, VLOP and VLOSE providers rather than deployers. A third difference comes from the wording of point (k) itself rather than from ¶126: it reaches only "a generated or manipulated image, audio or video," so AI-generated text is outside it. So the reading that Art. 35(1)(k) is a general labelling duty is not supported by the text, for three separate reasons: it is illustrative, it is platform-bound, and on its face it does not cover text.
One genuinely useful thing in ¶126 points the other way. Where a VLOP provides labelling tools, "those deployers can rely on such tools to fulfil their transparency obligation under that provision within the context of the VLOP or VLOSE used." If RDCO ever posts content that does clear the deep-fake bar to LinkedIn or X, the platform's own AI-content label can discharge the Art. 50(4) first-subparagraph duty for that post.
Political Advertising Regulation: inapplicable, with one sponsorship trip-wire
Crisply: no AI-content labelling duty exists in this Regulation, and the Regulation does not apply to RDCO because RDCO runs no political advertising.
The labelling duty that does exist, Art. 11(1), requires each political advertisement to carry a statement that it is a political advertisement, the sponsor's identity, the linked election or process, a statement if targeting was used, and a transparency notice under Art. 12. None of it concerns AI origin. The only two artificial-intelligence references in the instrument are in Art. 19, which requires transparency about "whether an artificial intelligence system has been used to target or deliver the political advertisement." That is a duty about the targeting pipeline, not about who or what wrote the words.
The editorial carve-out, Art. 1(2), is worth noting because it is broader than Art. 50(4) in the one way that matters to us: "Political opinions and other editorial content, regardless of the medium through which they are expressed, that are subject to editorial responsibility shall not be considered to be political advertising unless specific payment or other remuneration is provided for, or in connection with, their preparation, placement, promotion, publication, delivery or dissemination by third parties." No publication-of-identity condition, no fact-checking minimum, no post-sign-off voiding rule. Art. 1(3) adds that political opinions expressed in a personal capacity are out.
The one forward trip-wire. The Sanity Check monetization plan in [[revival-strategy]] is third-party sponsorship, with outreach opening at 1,000 subscribers. Art. 1(2)'s carve-out falls away where a third party provides specific payment for or in connection with the editorial content. Combine that with Art. 3(2)(b), which defines political advertising to include a message "liable and designed to influence ... a legislative or regulatory process, at Union, national, regional or local level," and a paid-sponsored Sanity Check issue advocating a position on AI regulation could land inside Art. 11, if the sponsor's payment is tied to that content rather than being a generic per-issue slot. The distinction between a generic sponsor slot and payment for a position is exactly where Art. 1(2) turns, and it is not resolved by the text alone. Worth a lawyer's eye before the first sponsored issue, not before the first subscriber.
EMFA: not a duty, and a reuse that is probably out of reach
The EMFA contains no content-labelling provision of any kind. Its only artificial-intelligence provision is Art. 18(1)(e), and reading it carefully inverts the worry:
"Providers of very large online platforms shall provide a functionality allowing recipients of their services to: ... (e) declare that they do not provide content generated by artificial intelligence systems without subjecting it to human review or editorial control."
The obligation is on the platform to offer the box. The publisher's side is a self-declaration whose payoff is the Art. 18(4) procedural protections: a statement of reasons and a 24-hour window to reply before a VLOP suspends or restricts visibility of your content. It is a declaration that you do keep a human in the loop, which is the opposite of a label, and the consequence of not making it is losing a protection rather than incurring a duty.
Art. 6(1) is the one real duty the EMFA places on publishers, and it is service-level, not content-level: legal name and contact details, influential owners, beneficial owners, and the annual totals of public funds received for state advertising and of advertising revenue from third-country public authorities or entities, all "easily and directly accessible to the recipients of their services." Art. 6(3) adds, for providers of news and current-affairs content, measures to guarantee editorial independence and to disclose conflicts of interest. None of this touches AI origin, and none of it asks for a named function holding editorial responsibility. Keeping the service-level and content-level duties apart is the whole reason this instrument reads as alarming and resolves as harmless.
Does RDCO fall inside the duty-bearer class? Honestly uncertain. EMFA Art. 2(1) defines a media service as one whose principal purpose is "providing programmes or press publications, under the editorial responsibility of a media service provider, to the general public." Art. 2(5) imports "press publication" from Art. 2(4) of the Digital Single Market copyright directive, Directive (EU) 2019/790: a collection mainly of literary works of a journalistic nature, constituting an individual item in a periodical or regularly updated publication under a single title, informing the general public, "published in any media under the initiative, editorial responsibility and control of a service provider." Recital 56 of that directive expressly includes news websites and "subscription-based magazines," and excludes blogs only where the activity is not carried out under a service provider's initiative, editorial responsibility and control. Ray Data Co LLC supplies exactly that initiative and control over Sanity Check, so the blog exclusion does not obviously rescue us.
The weak link is Art. 2(2)'s "whose professional activity is to provide a media service." The Article 18 guidelines stress that recital 9 of the EMFA "highlights the professional character of the activity as a determining factor," while confirming the definition covers "a wide spectrum of professional media actors, including freelancers." Sanity Check is free, RDCO is dormant, a media service is a service within the meaning of Articles 56 and 57 of the Treaty on the Functioning of the European Union (normally provided for remuneration), the EMFA has no territorial-scope article, and enforcement runs through national regulatory authorities over providers within Member State jurisdiction. So: arguable in principle, no practical duty, and in any case not a labelling duty. Filed as follow-up 2 rather than resolved here.
The Article 18 reuse, and why it is probably out of reach. Section 4.4 of the Article 18 guidelines describes the optional information a media service provider may share alongside the point (e) declaration as relating to "specific functions or roles within a media service provider's organisation that are entrusted with editorially reviewing content generated by artificial intelligence systems, or with taking editorial responsibility for such content" (¶40). That is close to the artefact AI Act guidelines ¶138 asks for, described in similar words by the same institution five months earlier. The temptation is to call that a second reason to write the statement. Two features of the text block it:
- The declaration is cumulative, not a menu. Guidelines ¶1: "To benefit from these safeguards, media service providers need to declare that they fulfil a number of elements, as listed in Article 18(1), first subparagraph, points (a) to (g)." Point (a) is a declaration that you are a media service provider, which is the open question above. Point (d) requires declaring that you are "subject to regulatory requirements for the exercise of editorial responsibility in one or more Member States and to oversight by a competent national regulatory authority or body," or that you adhere to a co-regulatory or self-regulatory mechanism "widely recognised by and accepted in the relevant media sector in one or more Member States." A US-established one-person newsletter has no evident route to point (d).
- The ¶40 information is expressly optional. Guidelines ¶17 makes the whole supporting-information feature "strictly subject to media service providers' sole discretion," and says its absence "should not render the declaration incomplete."
So the honest statement is narrower than it first looked: the EMFA asks RDCO for nothing, and the convergence of wording is a drafting convenience available if RDCO ever becomes a media service provider with a point (d) route. It is not a second duty, and it is not a second reason the statement must exist.
Synthesis for RDCO
The answer to the question as asked is no, three times, and the reasons are different enough to keep separate. The DSA misses us on architecture: Art. 2(2) says the Regulation does not apply to services that are not intermediary services, and a newsletter publishing its own content is not one. The Political Advertising Regulation misses us on subject matter: it contains no AI-content labelling duty for anyone, and we run no political advertising. The EMFA misses us because it has no labelling duty to miss anyone with. The parent brief's verdict therefore stands without modification. The single shipping-surface action item is unchanged, it is still open as far as vault records go, and its two companion policy items from the parent brief are untouched by anything here.
What this pass did buy is a tested negative, which is worth more than it reads. The parent verdict was a single-instrument conclusion: we owe a label unless we hold a carve-out, and the carve-out has a form requirement. A single-instrument conclusion in EU digital law is exactly the kind of thing that breaks when the second and third instruments arrive, because the usual pattern is overlapping obligations with mismatched exemptions. That pattern does not appear here. All three candidate instruments route their AI-adjacent provisions to platforms, and the only one that places a real duty on publishers, EMFA Art. 6(1), places a service-level ownership-and-contact duty that has nothing to do with AI origin. The content-versus-service distinction is the thing to keep: these are different obligations, they live in different instruments, and collapsing them is how a small publisher talks itself into compliance work it does not owe.
The thread's recurring lesson repeats. "Who are you" resolved the question twice more here: Art. 35(1)(k) DSA misses us because we are a publisher rather than a platform, and EMFA Art. 18 misses us because the duty-bearer is the VLOP provider. In both cases the intuition reasoning from subject matter, "this is about AI content and we publish AI-assisted content," pointed the wrong way, and the intuition reasoning from role pointed the right way first. Worth encoding as a reading rule for the next instrument: find the duty-bearer noun before reading the duty. The Political Advertising Regulation is the one miss here that is not role-based; it simply contains no such duty.
For positioning, this tightens the claim the parent brief identified rather than extending it. The sellable observation was "your AI-assisted content is fine, and here is the two-line thing you need on your site to keep it fine." Three instruments later, that claim survives a deliberate attempt to break it, which is the kind of thing worth saying in a market where most coverage is still aimed at the machine-readable marking duty that belongs to model providers rather than to publishers. The re-frame holds: the regulation everybody read as a technology requirement is an editorial-accountability requirement, and the two instruments you would reach for next to find a technology requirement do not contain one. The thing to drop from the pitch is any suggestion that the DSA adds exposure for ordinary publishers. It does not, and saying otherwise would be the fear-selling the vault's own editorial standard rules out.
Why this is in the vault
This closes the third open follow-up from [[2026-09-03-ai-act-article-50-transparency-guidelines]] and confirms, against three primary texts plus the five guideline interplay sections, that the single live action on a shipping RDCO surface, Sanity Check's publicly findable editorial-responsibility statement, survives a deliberate attempt to find a competing labelling duty with no editorial exemption. It records first vault coverage of the DSA, the Political Advertising Regulation and the EMFA, supplies the ¶140 clause that makes the Art. 50(4) carve-out available to a publisher who is not a media service provider, and gives the [[revival-strategy]] sponsorship plan a specific regulatory question to put to a lawyer before the first paid issue.
Open follow-ups
- Does the Code of Practice on Transparency of AI-Generated Content impose anything on signatory deployers that Art. 50(4) does not? The parent brief noted that deployers may sign, that the Commission has assessed the code adequate, and that guidelines ¶137 specifically commends it to "deployers that are not media service providers subject to existing editorial professional or deontological standards." The commitments themselves were never read. If any deployer-side commitment lacks an editorial carve-out, signing would create an obligation we do not currently have. Answerable from the published code.
- Is Sanity Check a "press publication" under Art. 2(4) of Directive (EU) 2019/790 as imported by EMFA Art. 2(5), and what follows if it is? The structural elements mostly fit; the live questions are EMFA Art. 2(2)'s "professional activity" read against recital 9 and the remuneration element in Articles 56 and 57 of the Treaty, and the "economic activity" condition in recital 56 of Directive (EU) 2019/790, both of which bear directly on the fact that Sanity Check is free. Two distinct consequences to separate: EMFA Art. 6(1) service-level transparency, and eligibility for the Art. 18 safeguards, which is separately gated by Art. 18(1)(a) and (d). Mostly answerable from the EMFA recitals, C/2026/901 and the directive; the Member State enforcement-practice part is not document-fixed.
Related
- [[2026-09-03-ai-act-article-50-transparency-guidelines]] — the parent brief, whose verdict this one tests and upholds
- [[revival-strategy]] — the Sanity Check sponsorship plan that the Regulation (EU) 2024/900 trip-wire attaches to
- [[2026-08-21-ai-act-article-113-operative-text-check]]
- [[2026-08-27-ai-act-113-3c-registration-deferral-gap]]
- [[2026-08-26-ai-act-article-6-classification-guidelines]]
- [[2026-08-15-eu-digital-omnibus-ai-official-journal-check]]
- [[2026-08-02-agents-as-employees-regulatory-labor-framing]]
- [[2026-04-15-data-engineering-weekly-editorial-scope-context-engineering]] — the vendor-neutrality editorial standard that keeps Sanity Check outside the guidelines' advertisement carve-out and therefore inside Art. 50(4)
Sources
Primary, fetched and read
All EU texts retrieved via the Cellar content-negotiation route documented in the parent brief: curl -H 'Accept: application/xhtml+xml' -H 'Accept-Language: eng' http://publications.europa.eu/resource/celex/<CELEX>, then stripped to plain text locally and read by article. No WebFetch summarisation was used on any legal text.
- Regulation (EU) 2022/2065 (Digital Services Act). CELEX 32022R2065, HTTP 200, 838,166 bytes. Articles read: 1, 2(1)-(4), 3(g) including points (i)-(iii), 3(i), 3(j), 3(k), 19, 26, 33(1)-(4), 35(1) opening and point (k). Recitals 13 and 18 (online-newspaper comments as ancillary to publication under the publisher's editorial responsibility; liability exemptions unavailable for the provider's own editorially-responsible content).
- Regulation (EU) 2024/900 (transparency and targeting of political advertising). CELEX 32024R0900, HTTP 200, 370,804 bytes. Read: 1(1)-(4), 2(1)-(3), 3(2) definition of political advertising with exclusions (i)-(iii), 11(1)-(5), 12(1). Full-text search for "artificial intelligence" across the instrument returned exactly two hits, both in Art. 19.
- Regulation (EU) 2024/1083 (European Media Freedom Act). CELEX 32024R1083, HTTP 200, 344,753 bytes. Read: 1(1)-(3), 2(1)-(13), 6(1)-(3), 18(1)-(4). Recital 32 on Art. 6(1) ownership transparency. Full-text search for labelling, deep fake and generated-or-manipulated returned one substantive hit, Art. 18(1)(e).
- Directive (EU) 2019/790 (Digital Single Market copyright). CELEX 32019L0790, HTTP 200, 273,811 bytes. Read: Art. 2(4) press-publication definition and recital 56 (subscription-based magazines in, blogs out only where not under a service provider's initiative, editorial responsibility and control).
- European Commission, C(2026) 5054 final, ANNEX, Guidelines on the implementation of the transparency obligations for certain AI systems under Article 50 of Regulation (EU) 2024/1689, 20.7.2026, 51pp. https://ec.europa.eu/newsroom/dae/redirection/document/131215 — 837,633 bytes, converted locally. Sections read in full this pass: 3.3 (¶¶50-53), 4.4 (¶¶94-98), 6.1.5 (¶¶126-129), 6.2.5 (¶140), plus §7 ¶¶141-143 on the Art. 50(5) horizontal requirements and §5.3 ¶110 (checked and set aside as irrelevant: emotion recognition and biometric categorisation). Non-binding.
- European Commission, Communication C/2026/901, Commission guidelines on the implementation of the declaration functionality for media service providers pursuant to Article 18(1) of Regulation (EU) 2024/1083, OJ C, 11.2.2026 (adopted 6 February 2026). CELEX 52026XC00901, HTTP 200, 70,637 bytes. Read: ¶1 (cumulative points (a) to (g)), the scope paragraphs on the media-service and media-service-provider definitions, ¶17 (optional supporting-information feature, sole discretion), ¶¶39-40 (section 4.4 on Art. 18(1), first subparagraph, point (e)). Non-binding. Note: the ELI route https://eur-lex.europa.eu/eli/C/2026/901/oj/eng returned HTTP 202 with a zero-byte body; the CELEX route worked.
Secondary
- Marie-Therese Sekwenz, When Is Content "AI-Generated Enough"? Labelling Synthetic Media under the Digital Services Act and the AI Act, arXiv:2609.07727v1, cs.CY, CC BY-SA 4.0. https://arxiv.org/pdf/2609.07727 — read locally after PDF extraction; the WebFetch summariser could not read the byte stream.
- Taylor Wessing, The DSA, the EMFA and the AI content conundrum. https://www.taylorwessing.com/en/interface/2025/media-hot-topics-2025/the-dsa-the-emfa-and-the-ai-content-conundrum — unreachable. HTTP 403 to WebFetch; the browser-user-agent retry was denied by the auto-mode classifier as bot-check circumvention and was not attempted again. Directly on topic; its contents are not reflected in this brief.
- European Commission, Guidelines under Article 18 European Media Freedom Act (EMFA) library listing. https://digital-strategy.ec.europa.eu/en/library/guidelines-under-article-18-european-media-freedom-act-emfa
- European Board for Media Services, statement welcoming the Article 18 guidelines, 22 April 2026. https://media-board.europa.eu/news-0/media-board-welcomes-eu-commissions-guidelines-under-article-18-emfa-2026-04-22_lt
- EMMA and ENPA, joint feedback on the Article 18(1) EMFA guidelines consultation. https://www.enpa.eu/press-releases/emma-enpa-feedback-art-181-emfa-guidelines-consultation
Research notes trail
- Research caps observed: 2 qmd calls, 3 WebSearch, 3 WebFetch. Everything else was direct
curlof free primary sources, which the parent brief established as the reliable route for long EU texts after WebFetch truncated a 350 KB regulation. - Vault gate-check re-run 2026-11-01: still zero vault documents on the DSA, Regulation (EU) 2024/900 or the EMFA. Also searched for evidence the ¶138 editorial-responsibility statement has been published since 2026-09-03; no vault record found, so the action is treated as open.
- Deliberately not re-litigated: what Art. 50(4) says, who the provider and deployer are, and whether territorial scope reaches a Florida company. All three are settled in [[2026-09-03-ai-act-article-50-transparency-guidelines]].
- Independent review, and what it changed. A zero-context fresh-eyes critic re-fetched all the primary texts and spot-checked the quotes. Quotations came back verbatim; the first draft's reasoning did not survive intact. Five corrections were applied: the headline was recalibrated from "STRENGTHENED, a second independent reason" to "STANDS, unchanged" after C/2026/901 ¶1 showed the Art. 18(1) declaration is cumulative across points (a) to (g), including a point (d) national-oversight condition RDCO has no route to; a claim that Art. 50(4) is the only text-labelling duty "in Union law" was wrong, since Art. 50(2) also covers text; the no-text point about Art. 35(1)(k) was misattributed to guidelines ¶126, which does not make it; the gap between the two guideline documents is about five months, not eight; and the guidelines carry five interplay sections, not four. The ¶140 "distinct concept ... broader contexts and to other deployers" clause was added at the critic's prompting and is now the load-bearing cite for the carve-out being available to a non-media-service publisher.
- No paywalls were encountered on any primary source. EUR-Lex and the Commission document store are both free.