{ "schemaVersion": "1.0", "language": "en", "canonicalUrl": "https://catalysphere.co.jp/en/articles/ai-transparency-disclosure-design/", "machineReadableUrl": "https://catalysphere.co.jp/en/articles/ai-transparency-disclosure-design/index.json", "publisher": { "name": "Catalysphere", "url": "https://catalysphere.co.jp/", "description": "A research and consulting studio connecting AI and big-data research with practice." }, "article": { "slug": "ai-transparency-disclosure-design", "title": "AI transparency does not end with a single disclosure", "summary": "A role-and-output reading of EU AI Act Article 50, translating human-facing disclosure, machine-readable marking, exceptions, and version evidence into one placement record.", "takeaways": [ "Article 50 creates different transparency duties for different roles and system or output categories; one generic badge cannot substitute for them.[1]", "Clarity, timing and accessibility for human-facing disclosure serve a different purpose and implementation surface from machine-readable marking and detectability.[1] [3]", "Catalysphere recommends using a placement record covering the provision, surface, exception basis, test result, version, and owner as a release gate." ], "publishedAt": "2026-08-27", "updatedAt": "2026-09-26", "readingMinutes": 11, "topics": [ "AI governance", "Generative AI", "Content provenance", "Risk management" ], "domains": [ "governance-risk", "generative-ai" ], "evidenceKind": "research-review", "status": "published", "lead": "An EU-facing release review can go wrong when a footer saying “AI-generated” is treated as the whole transparency design. Article 50(1)–(5) does not collapse interaction, synthetic content, emotion recognition and biometric categorisation, deepfakes, and public-interest text into one disclosure.[1] This research review integrates the current law, the 2026 amendment, and Commission materials to provide a release decision structure rather than case-specific legal advice.[1] [2] [3]", "sections": [ { "heading": "The decisions erased by a single badge", "paragraphs": [ "A generic footer creates one visible location, but it does not determine whether the actor is a provider or deployer, whether the object is an interaction or generated output, or who controls first exposure. Article 50 separates transparency by actor, system or output, audience, timing, and medium rather than treating it as one UI component.[1]", "The non-obvious point is that human-facing disclosure and machine-readable marking are not stronger and weaker versions of the same device. Provider-side marking under Article 50(2) enables software to read and detect generation or manipulation. Deployer-side disclosure under Article 50(4) makes certain deepfakes and other content intelligible to people. Evidence of one implementation does not replace the decision for the other.[1] [3]", "This article treats the release question not as whether a label exists, but whether every applicable role-and-object combination has the correct surface and evidence. Duties can apply cumulatively to the same system or group of actors, so the branching decision must precede the choice of badge.[3]" ] }, { "heading": "Return paragraphs (1)–(5) to their roles and outputs", "paragraphs": [ "Article 50(1) requires the provider of an AI system intended to interact directly with natural persons to inform them that they are interacting with AI. The law includes bounded qualifications, including when that fact is obvious in the circumstances, but when the duty applies Article 50(5) makes delivery no later than the first interaction or exposure part of the design.[1] [3]", "Article 50(2) requires providers of systems that generate synthetic audio, image, video, or text to mark outputs in a machine-readable format and make them detectable as artificially generated or manipulated. Article 50(3), by contrast, requires deployers of emotion-recognition and biometric-categorisation systems to inform exposed natural persons.[1]", "Article 50(4) separates two further deployer duties: disclosure of deepfakes and disclosure of certain AI-generated or manipulated text published to inform the public on matters of public interest. Article 50(5) makes clear and distinguishable information, timing, and accessibility horizontal requirements. Paragraphs (1)–(4) are not mutually exclusive menu choices.[1] [3]" ], "visual": { "kind": "comparison", "eyebrow": "ROLE × OUTPUT × DISCLOSURE SURFACE", "title": "The same “AI label” splits into different actors, outputs, and placements", "caption": "This is a statutory index separating the decision surfaces in Article 50(1), (2), (4), and (5). Machine-readable marking does not replace human-facing disclosure. Article 50(3) emotion-recognition and biometric-categorisation notices, case-specific exceptions, and the limited 2026 transition are handled separately in the article.", "items": [ { "label": "Interactive AI", "value": "Provider | Human notice | By first interaction", "detail": "Tell natural persons that they are interacting with AI. Whether the interaction is obvious in context or a statutory exception applies is a separate decision.", "referenceIds": [ 1 ] }, { "label": "Synthetic audio, image, video, or text", "value": "Provider | Machine-readable marking | Generated output", "detail": "Mark outputs in a machine-readable format so they are detectable as artificially generated or manipulated; the technical solutions must be effective, interoperable, robust and reliable as far as technically feasible. This is not the same as a human-visible badge on every output.", "referenceIds": [ 1 ] }, { "label": "Deepfake", "value": "Deployer | Human-perceivable disclosure | By first exposure", "detail": "Do not rely only on provider metadata. Evidently artistic, creative, satirical, fictional, or analogous works require a separate decision about appropriate disclosure that does not hamper enjoyment.", "referenceIds": [ 1 ] }, { "label": "Public-interest text", "value": "Deployer | Human disclosure | Publication or exposure", "detail": "This branch covers generated or manipulated text published to inform the public on matters of public interest. Record the human-review, editorial-control, and editorial-responsibility exception separately.", "referenceIds": [ 1 ] } ] } }, { "heading": "Visible disclosure and readable marking work on different surfaces", "paragraphs": [ "Machine-readable marking is not synonymous with a badge people see on every output. The non-binding Commission guidelines describe software-extractable information and perceptible disclosure as complementary and do not derive a universal visible-label duty for every synthetic output from Article 50(2). Marking also involves effectiveness, interoperability, robustness, and reliability so far as technically feasible.[1] [3]", "Conversely, a deployer publishing a deepfake cannot treat provider metadata alone as the human-facing disclosure. The wording, first exposure, and placement in the screen, player, or text must be designed so the actual audience can distinguish it. Burying the information in terms, a manual, or a footer is not the same as disclosure at first exposure.[1] [3]", "This article uses a two-layer handoff: receive the marking method, detection method, supported format, and version from the provider, then have the deployer check whether the mark survives distribution and place its human-facing disclosure. The final Code gives signatories concrete marking, detectability, visible or audible disclosure, and internal-process measures without merging the two responsibilities.[3] [4]" ] }, { "heading": "Separate an exception from an attenuated disclosure", "paragraphs": [ "Article 50(1) includes bounded qualifications for interactions that are obvious in the circumstances and certain legally authorised criminal-law uses. This article's release check does not treat a product owner's assumption that users will surely understand as sufficient. It checks the intended audience, contact surface, and opening of the interaction in the release candidate and retains the factual basis for obviousness.[1] [3]", "Article 50(2) expressly addresses standard-editing assistance, outputs that do not substantially alter input data or its semantics, and certain legally authorised law-enforcement uses. The guidelines' treatment of closed products and ephemeral real-time generation is non-binding interpretation of proportionality and technical feasibility, not a set of new blanket statutory exceptions.[1] [3]", "For deepfakes in evidently artistic, creative, satirical, fictional, or analogous works, Article 50(4) attenuates the manner of disclosure but still contemplates an appropriate disclosure that does not hamper display or enjoyment. Public-interest text has an exception involving human review or editorial control plus editorial responsibility for publication. A superficial review should not be treated as automatic proof of the exception.[1] [3]" ], "bullets": [ "Applicability: Fix the actor, system or output category, audience, and publication or exposure facts first", "Express exception: Retain the paragraph wording, relevant facts, scope, and decision owner in one record", "Attenuated disclosure: Do not confuse it with no duty; test whether the audience is informed without hampering enjoyment of the work", "Guideline interpretation: Keep it separate from statutory exceptions and retain the version and non-binding rationale" ] }, { "heading": "2 August and 2 December are not the same postponement", "paragraphs": [ "Under Article 113 of the AI Act, Article 50 has applied since 2 August 2026, and the 2026 amendment left that date and the core structure of the duties in place. As of 26 September 2026, 2 December (the Article 111(4) transition) is the only remaining Article 50 date; reading it as a general grace period would delay interaction notices and deployer disclosures that already apply.[1] [2]", "The transition added to Article 111(4) by Regulation (EU) 2026/1744 is narrow. Providers of synthetic-content-generating systems placed on the market before 2 August 2026 have until 2 December 2026 to comply with Article 50(2). It is neither a general postponement of Article 50 nor a blanket grace period for new systems.[2]", "Where one product both interacts and generates content, separate the Article 50(2) marking that may qualify for the transition until 2 December from the Article 50(1) interaction notice that has applied since 2 August. The Commission guidelines' treatment of outputs generated before 2 August as not requiring retroactive action is interpretation, not operative language carrying the same legal weight as Article 111(4).[2] [3]" ] }, { "heading": "Do not turn guidance and the Code into a certificate", "paragraphs": [ "The Commission guidelines published on 20 July 2026 are influential implementation material on roles, cumulative application, placement, and technical feasibility, but they are non-binding. The library page says they were adopted, while C(2026) 5054 says the content was approved and formal adoption would follow once all language versions were available. Because no separate later adoption instrument had been identified as of 26 September 2026, this article uses the narrower description: non-binding guidelines whose content the Commission approved.[3]", "The final Code dated 10 June 2026 is voluntary and provides a signatory route for Article 50(2), (4), and (5). It does not cover the interaction notice in paragraph (1) or the emotion and biometric notice in paragraph (3), and it mixes signatory commitments with encouraged or optional measures. Following it cannot be expanded automatically to every Article 50 duty or treated as the only implementation method.[4]", "The Commission Opinion and AI Board assessment found the Code adequate, but adherence is not conclusive evidence of compliance. The Board retained concerns about interoperability, short text, and downstream label retention and noted the need for reassessment where measures prove insufficient, impractical, or disproportionate. Amended Article 50(7) likewise preserves Board-informed assessment and the possibility of common rules if the Code is inadequate.[2] [5]" ] }, { "heading": "Turn the placement record into a release gate", "paragraphs": [ "Catalysphere recommends deriving a disclosure placement record from the role-output matrix rather than copying the statutory text into a form. This is neither a prescribed legal document nor a certificate of conformity. It is an internal control that makes it possible to recheck which version was used, who assessed each duty, and where the disclosure or marking was implemented.[1] [3] [4] [5]", "The core of the record is the decision field, not the disclosure wording. Link the system and release ID, provider or deployer role, Article 50 paragraph, system or output category, audience, first interaction or exposure, human-facing medium, machine-readable method, exception or attenuated-treatment rationale, accessibility, technical limit, evidence, owner, and review date. Do not release with applicable, not applicable, exception, or attenuated treatment left blank.", "At the release gate, inspect the human-facing disclosure in the rendered candidate, extract and detect the mark from actual outputs when applicable, and test the assumption that it survives downstream transformation. Re-review when the legal source, Code, format, model, or distribution surface changes, and name the stop or rollback owner for missing disclosure or failed marking. The gate does not automate legal judgment; it stops unresolved branches from disappearing into release." ], "bullets": [ "Current source: Fix the versions and check dates for the consolidated law, amendment, guidelines, Code, Opinion, and Board assessment", "Role and duty: Decide the provider or deployer role, Article 50 paragraph, and system or output category separately", "Human-facing surface: Render and inspect the audience, wording, channel, placement, first interaction or exposure, and accessibility", "Machine-readable surface: When applicable, inspect the format, embedding point, extraction, detectability, and interoperability target", "Exception path: Distinguish an express exception, attenuated disclosure, and technical-feasibility interpretation; retain facts, authority, and approver", "Evidence owner: Link screenshots, sample outputs, inspection results, downstream tests, and the review date to the release ID", "Change and rollback: Name triggers for model, format, UI, distribution, and legal-source changes, plus owners for stop, repair, and republication" ] } ], "note": "This is a research review of release design centred on Article 50, not case-specific legal advice. The consolidated text is documentary and the authentic Official Journal acts control.[1] [2] The Commission guidelines are non-binding, and their formal-adoption status reflects a check made on 26 September 2026.[3] The Code is voluntary, and neither the Commission Opinion nor the AI Board assessment treats adherence as conclusive proof of legal compliance.[4] [5] The classification of provider and deployer roles, deepfakes, public-interest matters, substantial alteration, and human review depends on the facts. The Catalysphere placement record and release gate are unvalidated internal-control proposals; consult qualified EU counsel and the competent authority for a specific case.", "sources": [ { "id": 1, "authors": "European Parliament and Council of the European Union", "year": 2026, "title": "Consolidated text of Regulation (EU) 2024/1689 laying down harmonised rules on artificial intelligence, 27 July 2026", "venue": "EUR-Lex consolidated text", "url": "https://eur-lex.europa.eu/eli/reg/2024/1689/2026-07-27/eng", "finding": "Article 50(1)–(5) assigns provider- and deployer-specific notice, marking, disclosure, timing, clarity, and accessibility duties across interactive AI, synthetic content, emotion and biometric systems, deepfakes, and public-interest text.", "limitation": "The consolidation is documentary and authentic Official Journal acts control. Deepfake, public-interest matter, substantial alteration, and human-review classifications are fact-dependent; this article does not decide a specific application." }, { "id": 2, "authors": "European Parliament and Council of the European Union", "year": 2026, "title": "Regulation (EU) 2026/1744", "venue": "Official Journal of the European Union", "url": "https://eur-lex.europa.eu/eli/reg/2026/1744/oj/eng", "finding": "The amendment changed the Article 50(7) Code-assessment procedure and added a transition until 2 December only for Article 50(2) and certain synthetic-content systems placed on the market before 2 August 2026.", "limitation": "It is not a general postponement of Article 50 or a blanket grace period for all systems. Historical procedural language in the Opinion should be read against the final act and current consolidation." }, { "id": 3, "authors": "European Commission", "year": 2026, "title": "Guidelines on transparency obligations for providers and deployers of certain AI systems", "venue": "European Commission, C(2026) 5054 final and Annex", "url": "https://digital-strategy.ec.europa.eu/en/library/guidelines-transparency-obligations-providers-and-deployers-ai-systems", "finding": "The guidelines operationally distinguish roles and four duties, cumulative application, machine-readable marking, human-facing placement, first exposure, accessibility, exceptions, and transition treatment.", "limitation": "The guidance is non-binding and only the Court of Justice can authoritatively interpret EU law. The library page's adopted wording and C(2026) 5054's formal-adoption statement leave a status caveat." }, { "id": 4, "authors": "European AI Office and Code drafting participants", "year": 2026, "title": "Code of Practice on the transparency of AI-generated content", "venue": "European Commission final voluntary Code, 10 June 2026", "url": "https://digital-strategy.ec.europa.eu/en/policies/code-practice-ai-generated-content", "finding": "For Article 50(2), (4), and (5), the Code gives signatories concrete measures for marking, detectability, interoperability, visible or audible disclosure, placement, testing, and internal documentation.", "limitation": "The Code is voluntary, excludes Article 50(1) and (3), and includes optional or encouraged measures. Signature or adherence does not conclusively establish case-specific legal compliance." }, { "id": 5, "authors": "European Commission and European Artificial Intelligence Board", "year": 2026, "title": "Commission Opinion and AI Board assessment of the Code of Practice on transparency of AI-generated content", "venue": "European Commission, C(2026) 4839 final, and AI Board assessment", "url": "https://digital-strategy.ec.europa.eu/en/library/commission-opinion-assessment-code-practice-transparency-ai-generated-content", "finding": "The Commission and AI Board found the Code adequate for Article 50(2), (4), and (5) while requiring continued attention to implementation and technical effectiveness.", "limitation": "These are institutional assessments, not legislation or a judicial determination. The Board retained concerns about short text, interoperability, fragmented detection, and downstream label retention." } ], "image": { "prompt": "Edit the referenced article artwork. Change only the four paper-like objects on the left: replace them with fully abstract, blank translucent material forms such as smooth vellum ribbons, glass flakes, or woven fibers. Remove every pseudo-letter, handwriting-like mark, document line, illustration, landscape, symbol, and printed texture from those left-side objects. They must contain absolutely no text-like or image-like markings. Preserve the central folded ivory membrane, the antique-gold and cool-blue inspection planes, the flowing strands, the right-side abstract outputs, deep navy background, exact wide composition, lighting, color palette, and all other geometry unchanged. Constraints: absolutely no text, letters, numbers, logos, watermarks, handwriting, document pages, paintings, badges, QR codes, or barcodes anywhere.", "alt": "Several gold signal sheets pass through layered translucent membranes and emerge as distinct blue forms: stacked planes, cubes, contours, and a node network", "aspectRatio": "16:9", "assetPath": "article-art/ai-transparency-disclosure-design.png", "status": "approved" }, "readingLayout": { "lead": { "sourceLength": 484, "sourceChecksum": "8a0c9997", "breaks": [ 300 ], "emphasis": [] } }, "url": "https://catalysphere.co.jp/en/articles/ai-transparency-disclosure-design/", "machineReadableUrl": "https://catalysphere.co.jp/en/articles/ai-transparency-disclosure-design/index.json", "topicFacets": [ { "id": "governance-risk", "name": "AI Governance", "url": "https://catalysphere.co.jp/en/topics/governance-risk/" }, { "id": "generative-ai", "name": "Generative AI", "url": "https://catalysphere.co.jp/en/topics/generative-ai/" }, { "id": "privacy-rights", "name": "Privacy & Rights", "url": "https://catalysphere.co.jp/en/topics/privacy-rights/" } ] } }