EU AI Act Article 50: a Decision Framework for Providers and Deployers


On this page
Definition: An Article 50 decision framework is a structured way to determine your obligations: whether you are a provider or deployer, which deadline applies, and which marking layers to implement first.
TL;DR: Answer four questions: are you a provider or deployer; is your system already on the EU market; what share of output is in scope; and which layers do you have. New systems have had to comply since 2 August 2026; legacy systems may have until 2 December 2026 under the provisional Digital Omnibus, which was not yet adopted when we last checked.
Question 1: provider or deployer?
If you place a generative system on the EU market, you are a provider under Article 50(2) and must mark output machine-readably. If you use such a system to publish deepfakes, you are a deployer under Article 50(4) and must disclose. Many platforms are both. Decide this first, because it sets which obligation drives your build.
Question 2: what is your deadline?
A system not on the EU market before 2 August 2026 has no grace and has had to comply since that date. A legacy system already on the market may have until 2 December 2026 under the 7 May 2026 provisional Digital Omnibus agreement. That agreement was not yet formally adopted when we last checked, so treat August as the date that applies and December as a contingency that could revert.
Question 3: what is in scope?
Identify the share of your output that is synthetic and reaches the EU. For most generation platforms that is all of it. For mixed pipelines, scope the AI-generated portion and mark at the boundary where it is produced.
Question 4: what do you build?
The Code of Practice second draft points to three layers: signed metadata, an imperceptible watermark, and fingerprint recovery. If you have none, the fastest path is one signing call that attaches all three. If you have some, fill the gaps. Document the posture, because authorities will ask what you did and when.
FAQ
Is the December grace period safe to rely on?
No. It depends on formal adoption of the Digital Omnibus, which had not happened when we last checked. Without adoption, the original 2 August 2026 date applies.
Does the Code of Practice bind me?
It is voluntary, but signatory status is likely to function as a presumption of compliance, shifting the burden to non-signatories.
Where Original Pictures stands today
Original Pictures offers a Sign API, a Verify API, hosted verify pages and the <op-verify> embed, the AI disclosure SDK with a tamper-evident evidence log, workflow templates, and the SDKs that wrap the APIs (the embed, the disclosure SDK and the SDKs are not yet published to npm or PyPI). One POST /v1/sign with "watermark": true, "fingerprint": true attaches a C2PA-format manifest and an invisible watermark and keeps a content fingerprint for lookup. RFC 3161 timestamping is built and will be switched on with our production signing certificate; files signed before then carry no trusted timestamp. Any C2PA-aware validator can read the manifest without calling us.
Original Pictures is C2PA conformant: it is listed on the C2PA Conforming Products List as a generator product under the C2PA Conformance Program 0.2 (C2PA Technical Specification 2.4), and any C2PA-aware validator can read its manifests. Signed with our production certificate from SSL.com, on the C2PA Trust List; validators that use the C2PA Trust List show the signer as recognized. One thing is on the near roadmap, and we name it as roadmap, not as shipped: a consumer capture app (not yet available). We do not sell a capture SDK.
Bottom line: Decide provider versus deployer, treat 2 August 2026 as your real deadline, which has already passed, scope your in-scope output, and implement the three marking layers now. Treat the December grace as conditional, not granted.
Try it on your own files
Create an API key and sign a test file. Talk to us if you need a walkthrough.