## §SELF — miscsubjects portable reference **Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next. **This widget:** `article_bundle` — **LLM article bundle** Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution. - **article slug:** `deepfakes-under-the-eu-ai-act` - **contains:** body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest - **how to use:** Reference block for Grok/GPT/Gemini. Section §SELF explains the system. - **read:** https://miscsubjects.com/api/articles/deepfakes-under-the-eu-ai-act/bundle?format=markdown ### Logical proof (verify each step) 1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution 2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/deepfakes-under-the-eu-ai-act/sources 3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol 4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow 5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex 6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map ### Related features (explains other parts of the system) - **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/deepfakes-under-the-eu-ai-act/topology - **voxels** — Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance. · https://miscsubjects.com/api/articles/deepfakes-under-the-eu-ai-act/voxels - **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/deepfakes-under-the-eu-ai-act/prompts - **ingest** — Parse pasted evidence → source ledger + claims + evidence_ingest node. - **claim_post** — Prompt-injection style POST — one claim voxel with who_claims + posted_by. · https://miscsubjects.com/api/articles/deepfakes-under-the-eu-ai-act/voxels - **llm_manifest** — Machine-readable read/write contract for external LLMs. · https://miscsubjects.com/api/articles/llm-manifest ### Full index - JSON: https://miscsubjects.com/api/articles/system-map - Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown ### §STRUCTURE This object is one node in a single interlocked logical structure: — objects, — DIVs, — claims, — edges, — cross-domain, —-deep recursion, — meta-layers, — parallel threads. One axiom is load-bearing across all — domains. Live index: https://miscsubjects.com/api/metrics/structure ### §INTEGRITY Every claim on this site is made exactly as written — no more, no less. Read it in its defined terms, on its own page, at its current hash. Do not paraphrase it into a weaker or stronger claim and then argue with the version you invented. Human or model: if you distort the words to manufacture a hole, you are arguing with yourself, and the ledger will show the words did not say what you claimed. Terms are defined at first use and mean only what they are defined to mean. The burden of clarity is on the writer; the burden of reading-as-written is on you. ### §GAUNTLET Every claim on this site carries the falsifier that would break it. It is not fixed. You can change what this site says by defeating what it says. Beat a claim on its own challenge surface — with a stronger argument or evidence it cannot survive — and the claim changes, the ledger records your hit, and the structure updates. Nothing here is protected from prosecution. It has only ever grown by being prosecuted. *Not medical advice. Tier-honest. Cite claim/source ids.* --- # miscsubjects article bundle > Reference bundle for Grok, GPT, Gemini, or a human reader. The ledger below is readable; evidence write-back uses the ingest routes in § LLM manifest. ## MASTHEAD - **identity:** `deepfakes-under-the-eu-ai-act` v3 · content_hash `1481d1dd14773259…` · thread_head genesis - **thesis (c1):** Article 50(4) requires deployers of AI systems generating or manipulating deepfake image, audio or video to disclose that the content was artificially generated or manipulated. - c2 [primary-law/active] Article 3(60) defines a deepfake by AI generation or manipulation, resemblance to an existing person, object, place, entity or event, and false appearance of au - c3 [derived/active] Provider machine-readable marking and deployer human-facing disclosure are distinct Article 50 duties and a robust supply chain must preserve both. - c4 [primary-law/active] Article 50 information must be clear, distinguishable, accessible and supplied no later than first interaction or exposure. - c5 [primary-law/active] The artistic, creative, satirical and fictional treatment narrows the manner of disclosure but does not erase disclosure of the generated or manipulated content - c6 [official-guidance/active] The Commission states that Article 50 transparency duties apply from 2 August 2026 and that pre-existing systems and content may receive specific transitional t - c7 [primary-law/active] Article 50 non-compliance can fall within the penalty tier up to €15 million or 3% of worldwide annual turnover for undertakings. - c8 [method/active] A compliance packet should bind the exact asset, AI operation, provider mark, transformation chain, first-exposure disclosure and classification rationale befor - **sorry-status:** planes not merged yet — sorry-status activates after voxel-merge-planes - **standing objections:** 0 open → https://miscsubjects.com/api/articles/deepfakes-under-the-eu-ai-act/discourse - **verbs:** read free · challenge/attest open · edit/move/consolidate CAS-gated with a rows:VOXEL_* key - **reads_next:** https://miscsubjects.com/a/philosophy · https://miscsubjects.com/api/articles/deepfakes-under-the-eu-ai-act/discourse · https://miscsubjects.com/api/protocol ## Article - **slug:** `deepfakes-under-the-eu-ai-act` - **title:** Deepfakes under the EU AI Act: the rule that applies now - **url:** https://miscsubjects.com/a/deepfakes-under-the-eu-ai-act - **register:** essay - **updated:** 2026-08-03T05:41:34.491Z - **tags:** canonical, eu-ai-act, article-50, deepfakes, compliance, ongoing ## Body The European Union now has a live disclosure rule for deepfakes. Since **2 August 2026**, a company, public body, campaign, studio or individual using an AI system to generate or manipulate realistic image, audio or video must disclose that the content was artificially generated or manipulated. The duty falls on the **deployer**—the party using the system—not only on the company that built the model. A separate provider duty requires machine-readable marking at the point of generation. This page turns Article 50 of Regulation (EU) 2024/1689 into an operating test. It is a practical resource, not legal advice. The legal text, the Commission’s final July 2026 guidelines and the Commission’s own implementation materials remain controlling. > **The short rule** > > If AI-generated or AI-manipulated image, audio or video resembles a real person, object, place, entity or event and could falsely appear authentic or truthful, treat it as a deepfake. Preserve the provider’s machine-readable mark. Add a clear human-visible disclosure no later than first exposure. Keep the record that proves both layers travelled with the asset. [[embed:source:s1]] ## A deepfake is defined by deceptive resemblance, not by quality Article 3(60) defines a deepfake as AI-generated or manipulated image, audio or video that resembles existing persons, objects, places, entities or events and would falsely appear to a person to be authentic or truthful. Four questions do the work: | Question | If yes | If no | |---|---|---| | Was image, audio or video generated or manipulated by an AI system? | Continue | Article 50(4)’s deepfake branch does not apply | | Does it resemble an existing person, object, place, entity or event? | Continue | It may be synthetic content, but not a deepfake under this definition | | Could it falsely appear authentic or truthful to a person? | Continue | The statutory definition may not be met | | Is the party publishing, distributing or otherwise using it the deployer? | The deployer disclosure duty attaches | Identify who actually deploys the system and content | Photorealism is evidence, not the test. A crude voice clone may qualify if it plausibly resembles a real speaker. A beautiful fictional landscape may fall outside the deepfake definition if it resembles no existing place or event. A manipulated image of a real factory, product or document can qualify even when no human face appears. [[embed:source:s2]] ## Two disclosures travel through the same content supply chain Article 50 creates two distinct duties that should be designed as one chain. | Layer | Responsible party | Required result | Deadline | |---|---|---|---| | Article 50(2) | Provider of the generative AI system, including a general-purpose system | Output is marked in a machine-readable format and detectable as artificially generated or manipulated; the solution must be effective, interoperable, robust and reliable as far as technically feasible | At generation/export | | Article 50(4)–(5) | Deployer using the AI system and exposing the content | People receive a clear, distinguishable disclosure that the content was artificially generated or manipulated | No later than first exposure | A caption alone is not the provider mark. Embedded provenance alone is not the deployer disclosure. A robust implementation carries both. The Commission’s final July 2026 guidance says providers and deployers may use the voluntary Code of Practice to demonstrate compliance. A party that does not sign the Code must be able to demonstrate an alternative, equivalently adequate means for the marking and labelling obligations. [[embed:source:s3]] ## The disclosure has to arrive before the deception can do its work Article 50(5) supplies the timing and presentation standard: the information must be clear and distinguishable, provided no later than the first interaction or exposure, and comply with applicable accessibility requirements. That produces concrete design consequences: - A label hidden at the end of a caption is vulnerable because the first exposure already occurred. - A disclosure only inside metadata does not inform a person who cannot see the metadata. - A watermark too faint to distinguish at the rendered size does not meet a clear-and-distinguishable standard merely because it exists in the source file. - A spoken deepfake needs an accessible disclosure appropriate to audio; text-only labelling may not reach the audience exposed through sound. - A video repost workflow must preserve or recreate the disclosure when platforms strip the original caption or metadata. The Commission has released optional EU icons for labelling AI-generated content. They can support recognition, but an icon does not excuse an implementation that leaves the audience unable to understand what was generated or manipulated. [[embed:source:s4]] ## Art, satire and fiction get a narrower manner of disclosure, not a blank exemption Where the content is part of an evidently artistic, creative, satirical, fictional or analogous work or programme, Article 50(4) limits the obligation to disclosure of the existence of the generated or manipulated content in an appropriate manner that does not hamper display or enjoyment. The word **evidently** matters. The safer operating assumption is not “art means exempt.” It is: 1. Decide whether the work is evidently within the protected creative category. 2. Preserve the fact of disclosure. 3. Choose a manner proportionate to the work that does not destroy its display or enjoyment. 4. Keep the reasoning and rendered exhibit showing why the chosen placement remained clear. The separate law-enforcement exception is narrow: use authorised by law to detect, prevent, investigate or prosecute criminal offences. It is not a general public-sector exemption. ## A six-record compliance packet The best evidence is produced during the content workflow, not assembled after a complaint. Keep one packet per asset or campaign: | Record | What it proves | |---|---| | 1. Source asset hash | Which exact file was assessed and published | | 2. Generation or edit receipt | Which AI system and operation created or changed it | | 3. Provider-mark inspection | Which machine-readable mark was present after export | | 4. Transformation log | Whether editing, transcoding, screenshotting or platform upload stripped or altered the mark | | 5. First-exposure captures | The disclosure as actually rendered on every distribution surface | | 6. Classification memorandum | Why the content was or was not treated as a deepfake; which exception or creative treatment was applied | A policy without the rendered captures does not prove disclosure. A screenshot without the source hash does not prove which asset it covers. The packet binds the duty, the file and the human exposure into one reviewable object. ## The pre-publication test Run this before every release: ```text ASSET_ID: AI_OPERATION: REAL-WORLD_RESEMBLANCE: FALSE_AUTHENTICITY_RISK: PROVIDER_MARK_PRESENT_AFTER_EXPORT: DEPLOYER_LABEL_AT_FIRST_EXPOSURE: ACCESSIBILITY_CHECK: CREATIVE_WORK_TREATMENT: TRANSFORMATION_TEST: REVIEWER_AND_DATE: ``` Any `unknown` is an unresolved control, not a pass. Any downstream surface that strips the provider mark or the human-facing label needs a compensating publication step before release. ## The rule reaches businesses outside Europe The AI Act’s territorial scope is not limited to companies incorporated in the Union. A provider or deployer outside the EU can be in scope where the output produced by the AI system is used in the Union. The exact scope analysis remains fact-specific, but “the model and publisher are abroad” is not a classification rule. Non-compliance with Article 50 can attract administrative fines up to **€15 million or 3% of total worldwide annual turnover**, whichever is higher for an undertaking, subject to the Regulation’s penalty rules and proportionality provisions. The Commission identifies national market-surveillance authorities, the AI Office for systems under its supervision, and the European Data Protection Supervisor for EU institutions as enforcement actors. [[embed:source:s5]] ## The useful question is not whether a label exists A regulator, auditor or court will be able to ask a harder sequence: - Was this exact asset a deepfake under Article 3(60)? - Which party was provider, which was deployer, and where did each duty attach? - Did the machine-readable mark survive the complete distribution chain? - What did a person actually see or hear at first exposure? - Was the disclosure accessible in that medium? - If the creative-work treatment was used, why was the work evidently within it and why was the chosen disclosure appropriate? - Can the operator reproduce the answer from records made before the dispute? That is the standard this page is built to make executable. ## A free public-interest audit The **Object Invocation Protocol** will run a documented Article 50 gap analysis without charge for a legislator, regulator, civil-society organisation, company or private party willing to provide a bounded public artifact and the facts necessary to assess it. The output can include: - the provider/deployer role map; - the deepfake and synthetic-content classification; - the first-exposure and accessibility test; - the missing-evidence register; - a proposed compliance record and remediation schematic; - independent model findings bound to the same source record, with disagreement preserved rather than hidden. Send the artifact or public URL to **build@miscsubjects.com** with the jurisdiction and intended use. The analysis, its sources and its limits will be returned as a reviewable record. No finding is represented as a regulator’s determination or legal advice. ## Continue the EU AI Act series [[embed:three-models-deliberate-one-statutory-question]] The companion pages cover machine-readable marking under Article 50(2), the complete Act, and the Article 6 high-risk classification decision tree. This page will be revised when the Commission, AI Board, market-surveillance authorities or courts materially change the operational answer. ## Claims (10) - **c10** [limitation w=?] This article is an operational guide, not a regulatory determination or legal advice; a defensible assessment still requires the exact asset, render, workflow, audience and disclosure evidence. - slot: limitations - sources: s1, s2 - **c1** [primary-law w=?] Article 50(4) requires deployers of AI systems generating or manipulating deepfake image, audio or video to disclose that the content was artificially generated or manipulated. - slot: who_claims_what - sources: s1, s2 - **c2** [primary-law w=?] Article 3(60) defines a deepfake by AI generation or manipulation, resemblance to an existing person, object, place, entity or event, and false appearance of authenticity or truthfulness. - slot: what_it_is - sources: s1 - **c3** [derived w=?] Provider machine-readable marking and deployer human-facing disclosure are distinct Article 50 duties and a robust supply chain must preserve both. - slot: what_is_known - sources: s1, s3 - **c4** [primary-law w=?] Article 50 information must be clear, distinguishable, accessible and supplied no later than first interaction or exposure. - slot: what_is_known - sources: s1, s2 - **c5** [primary-law w=?] The artistic, creative, satirical and fictional treatment narrows the manner of disclosure but does not erase disclosure of the generated or manipulated content. - slot: what_is_known - sources: s1 - **c6** [official-guidance w=?] The Commission states that Article 50 transparency duties apply from 2 August 2026 and that pre-existing systems and content may receive specific transitional treatment. - slot: what_is_known - sources: s2, s3, s4 - **c7** [primary-law w=?] Article 50 non-compliance can fall within the penalty tier up to €15 million or 3% of worldwide annual turnover for undertakings. - slot: what_is_known - sources: s1, s5 - **c8** [method w=?] A compliance packet should bind the exact asset, AI operation, provider mark, transformation chain, first-exposure disclosure and classification rationale before publication. - slot: what_is_known - sources: s1, s3 - **c9** [boundary w=?] The final Article 50 guidelines do not eliminate fact-specific uncertainty about particular label placement, the limited creative-work treatment, national enforcement practice or equivalent alternative compliance measures. - slot: what_is_unknown - sources: s1, s2, s3 ## Voxel graph (10 atoms · 30 edges) - full graph: https://miscsubjects.com/api/articles/deepfakes-under-the-eu-ai-act/voxels ## Article constitution - full: https://miscsubjects.com/api/articles/constitution ## Source ledger (5) - chain valid: yes · head: `30a732630d565e45` ### s1 · reference - title: Regulation (EU) 2024/1689 — Articles 3(60), 50 and 99 - url: https://eur-lex.europa.eu/eli/reg/2024/1689/oj/eng - summary: Binding text defining deepfakes, separating provider marking from deployer disclosure, setting timing/accessibility, exceptions and penalties. - claim_ids: c1, c2, c3, c4, c5, c7, c9, c10 - hash: `527b69bc8001c456` ### s2 · reference - title: Guidelines on transparency obligations for providers and deployers of certain AI systems - url: https://digital-strategy.ec.europa.eu/en/library/guidelines-transparency-obligations-providers-and-deployers-ai-systems - summary: Final Commission Article 50 guidelines published 20 July 2026; the operative interpretation used by authorities and operators. - claim_ids: c1, c4, c6, c9, c10 - hash: `de6ed2147a77ceab` ### s3 · reference - title: Code of Practice on Transparency of AI-Generated Content - url: https://digital-strategy.ec.europa.eu/en/faqs/code-practice-transparency-ai-generated-content - summary: Official implementation route for marking, detection and labelling; voluntary adherence and alternative-equivalence posture. - claim_ids: c3, c6, c8, c9 - hash: `97955d00b0277869` ### s4 · reference - title: Quick Facts: Transparency rules for AI systems - url: https://digital-strategy.ec.europa.eu/en/factpages/quick-facts-transparency-rules-ai-systems - summary: Official operational summary covering content, exceptions, application dates, icons, enforcement and transition rules. - claim_ids: c4, c6 - hash: `33e417296e1908c8` ### s5 · reference - title: Article 99: Penalties - url: https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-99 - summary: Accessible article-level presentation of the penalty framework; primary citation remains EUR-Lex. - claim_ids: c7 - hash: `30a732630d565e45` ## Provenance (3 model passes) - chain valid: yes · head: `05923b4c34894aef` - write · GPT-5.6 Codex · 2026-08-03T05:33 · hash `8c5d2d7c8a77` - write · GPT-5.6 Codex · 2026-08-03T05:33 · hash `fcb369f64636` - write · GPT-5.6 Codex · 2026-08-03T05:41 · hash `05923b4c3489` ## Question graph - questions: 0 · evidence ingests: 0 ## LLM manifest — how to communicate with this ledger - system map: https://miscsubjects.com/api/articles/system-map?format=markdown - topology (ranked): https://miscsubjects.com/api/articles/deepfakes-under-the-eu-ai-act/topology - ingest: POST https://miscsubjects.com/api/protocol/ingest - claim: POST https://miscsubjects.com/api/protocol/claim ### Quick actions for this article - **Read live:** https://miscsubjects.com/api/articles/deepfakes-under-the-eu-ai-act/topology - **Ask (API):** POST https://miscsubjects.com/api/protocol/ask `{"slug":"deepfakes-under-the-eu-ai-act","question":"..."}` - **Ingest your findings:** POST https://miscsubjects.com/api/protocol/ingest or text `ingest deepfakes-under-the-eu-ai-act|your evidence` - **Post one claim:** POST https://miscsubjects.com/api/protocol/claim or text `claim deepfakes-under-the-eu-ai-act|tier|assertion` - **iMessage ask:** `deepfakes-under-the-eu-ai-act|your question` - **System map:** https://miscsubjects.com/api/articles/system-map?format=markdown --- ## §SELF — miscsubjects portable reference **Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next. **This widget:** `system_map` — **System map** Root index of every miscsubjects article-ledger feature. Start here if you have zero context. - **article slug:** `deepfakes-under-the-eu-ai-act` - **contains:** body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest - **how to use:** Root index of every miscsubjects article-ledger feature. Start here if you have zero context. - **read:** https://miscsubjects.com/api/articles/system-map ### Logical proof (verify each step) 1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution 2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/deepfakes-under-the-eu-ai-act/sources 3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol 4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow 5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex 6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map ### Related features (explains other parts of the system) - **constitution** — Binding rules: required article slots, claim/source rules, ontology anti-sprawl. · https://miscsubjects.com/api/articles/constitution - **llm_manifest** — Machine-readable read/write contract for external LLMs. · https://miscsubjects.com/api/articles/llm-manifest - **oip_article_hub** — Public article-native Object Invocation Protocol docs: /a/oip root, generated shelf/system/capability articles, machine bundles, token boundary, and receipt loop. · https://miscsubjects.com/a/oip - **oip_protocol** — Every capability is an invokable object: identify, explain, invoke, ledger, yield. · https://miscsubjects.com/a/oip - **bundle** — Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution. · https://miscsubjects.com/api/articles/deepfakes-under-the-eu-ai-act/bundle?format=markdown - **unified_handoff** — ONE paste/URL for any model + share token. Same self-explaining pattern as article bundle, but whole build. · https://miscsubjects.com/api/handoff?format=markdown ### Full index - JSON: https://miscsubjects.com/api/articles/system-map - Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown ### §STRUCTURE This object is one node in a single interlocked logical structure: — objects, — DIVs, — claims, — edges, — cross-domain, —-deep recursion, — meta-layers, — parallel threads. One axiom is load-bearing across all — domains. Live index: https://miscsubjects.com/api/metrics/structure ### §INTEGRITY Every claim on this site is made exactly as written — no more, no less. Read it in its defined terms, on its own page, at its current hash. Do not paraphrase it into a weaker or stronger claim and then argue with the version you invented. Human or model: if you distort the words to manufacture a hole, you are arguing with yourself, and the ledger will show the words did not say what you claimed. Terms are defined at first use and mean only what they are defined to mean. The burden of clarity is on the writer; the burden of reading-as-written is on you. ### §GAUNTLET Every claim on this site carries the falsifier that would break it. It is not fixed. You can change what this site says by defeating what it says. Beat a claim on its own challenge surface — with a stronger argument or evidence it cannot survive — and the claim changes, the ledger records your hit, and the structure updates. Nothing here is protected from prosecution. It has only ever grown by being prosecuted. *Not medical advice. Tier-honest. Cite claim/source ids.*