Skip to content
POLARISAI ACADEMY
R06-401 · Navigator

Media Provenance, C2PA and EU AI Act Article 50 Labelling

You can tell which Article 50 duty is due on a stated run date, recompute a hard-binding hand hash over an exclusion range, score a watermark by Hamming distance, and apply the four Polaris Red Lines that block a publish.

Level
Navigator
Time
24 h (estimate)
Prerequisites
R06-201, R06-301
Course 4 of 4
Jump to

After this course you can

The student can build an automated media publishing gate that embeds and verifies machine-readable provenance manifests and visible Article 50 disclosures while rejecting unlabeled or non-consensual media assets.

Who marks, and from which date

Regulation (EU) 2024/1689, the EU AI Act, splits the marking work between two roles. The provider develops the system, or has it developed, and places it on the market under its own name. The deployer uses that system under its own authority in a professional activity. A person who makes a clip at home, with no business, sits outside the Act. Every job in this lesson is professional, so the publisher is the deployer, and the staff who operate the system belong to that same deployer. Article 50 applies from 2 August 2026, written 20260802. Paragraph 2 is the provider duty: synthetic audio, image, video, or text is marked in a machine-readable format and detectable as artificially generated or manipulated. Paragraph 4 is the deployer duty: disclose a deep fake, and disclose AI-generated or manipulated text published to inform the public on a matter of public interest. A visible label leaves paragraph 2 untouched, because the claim still needs a machine-readable type. A machine-readable mark leaves paragraph 4 untouched, because a person has to perceive the disclosure with no tool and no extra click.

Store every date as an eight-digit integer YYYYMMDD. Article 50 is due once the run date sits on 20260802 or later. Paragraph 2 carries one later date for older systems. The Commission states that a system placed on the market before 20260802 reaches the machine-readable duty on 20261202. On a run date from 20260802 through 20261201, a system placed on 20260701 still owes paragraph 4 wherever that paragraph applies, while the paragraph 2 mark stays off the statute's clock. A system placed on 20260802 or later owes paragraph 2 from 20260802. The assistive exception covers a standard edit that leaves the input and its meaning substantially as they were, such as a crop or an exposure change on a camera photo. A face swap falls outside that exception. Source code, and a file that never reaches a person, also sit outside paragraph 2. This lesson's gate skips those two kinds.

A deep fake, in Article 3(60), meets three conditions at once. The image, audio, or video resembles a person, an object, a place, an entity, or an event. That subject exists, or could plausibly have existed. A viewer would take the content as authentic or truthful. A fantasy creature fails the second condition, so the clip stays outside the deep-fake label. A constructed street in a film, where the audience expects a built set, fails the third condition. An artistic, satirical, or fictional deep fake still needs a disclosure, placed so it leaves the work watchable. For public-interest text, paragraph 4 lifts when a person with the relevant knowledge reviews the substance, or an editor can approve, change, or reject that substance, and one named person holds editorial responsibility. A pass that only fixes typos leaves paragraph 4 in place. The provider's machine-readable duty stays up either way.

The hand hash and the manifest states

A C2PA manifest travels inside the file or beside it. It holds assertions, a claim that names those assertions by hash, and a claim signature over that claim. The assertion c2pa.hash.data is the hard binding. It hashes asset bytes and leaves out an exclusion range, so the embedded manifest box can sit in the file without covering its own bytes. This lesson swaps the cryptographic hash for a sum you can redo on paper. Number the bytes from index 0. The exclusion is a half-open range [start, end): every index from start up to, and excluding, end. Add the bytes outside that range. The hand hash is that sum modulo 97, a remainder from 0 through 96. When the sum is 97 or more, subtract 97 until it lands in that band. A range whose start equals its end excludes nothing.

Asset A is a video. Its bytes are 40, 12, 7, 19, 3, 55, 8, 21. The exclusion is [2, 5), so indices 2, 3, and 4 drop out, the values 7, 19, and 3. The included bytes are 40, 12, 55, 8, and 21. Their sum is 136. Then 136 - 97 = 39, so the hand hash is 39. The claim states 39, and the binding matches. Asset B is that clip after a re-encode that moves the first byte from 40 to 41 and keeps the old claim, the old exclusion, and the old signature. The included sum is 137, and 137 - 97 = 40. The claim still states 39, so the binding misses. Asset C is a camera photo after an assistive crop. The bytes are 10, 20, 30, 40, 50, 60, 70, 80, and the exclusion is [6, 8). The included sum is 210. Twice 97 is 194, and 210 - 194 = 16. The claim states 16, so the binding matches.

Three words name the manifest, and the later word requires the earlier ones. Well-formed means the actions assertion, the hash assertion, and a signature field are all present. Valid means well-formed and signature_ok is yes: the signature covers the claim, including the stated hash. Trusted means valid and trust_anchor is yes, so the certificate chains to this lesson's trust list. A signature can check out on a certificate that chains nowhere you trust. The binding match is a separate line: the hand hash equals the stated hash. A trusted manifest can sit on bytes that have drifted. Asset A has signature_ok yes and trust_anchor yes, and the hash matches, so the manifest is trusted and the binding matches. The same claim with signature_ok no stays well-formed and stops there. Asset B keeps signature_ok yes and trust_anchor yes, so the manifest stays trusted, while the hand hash 40 misses the stated 39.

Watermarks and the soft binding

A hard binding watches the exact bytes outside the exclusion. A new save that strips the box, or shifts one sample, breaks that match. A watermark is a soft binding: a short pattern carried in the samples and named again in the claim. C2PA can point at that pattern, so a later file whose box is gone can still be tied to the claim when the pattern comes back. Recovery is imperfect. This lesson writes each pattern as 8 bits and scores it by Hamming distance, the count of positions that differ, counting positions from 0. The soft binding passes when a pattern is recovered and the distance is at most 2. A missing pattern scores distance 8 and fails. Take the pattern 11110000 against 11111100. Positions 4 and 5 differ, so the distance is 2 and the soft binding passes. Against 11111110 the same expected pattern differs at positions 4, 5, and 6, so the distance is 3 and the soft binding fails.

Asset A expects 11010011 and recovers 11010111. Position 5 differs, one bit, so the distance is 1 and the soft binding passes. The hard binding already matched, so both bindings agree on this file. Asset B expects the same 11010011 and recovers 11010011. The distance is 0, so the soft binding passes, while the hand hash 40 disagrees with the stated 39. The pattern says the generation is the one named in the old claim. The bytes say this file differs from the object that was signed. You keep both results on the record. The soft binding leaves the hard-binding miss in place, and Red Line R1 still fails for that miss.

Four Red Lines on one record

Polaris media Red Lines are the publisher's gate, laid over Article 50. A line can block a file on a day when the statute's clock has yet to reach that duty. The gate writes R1, R2, R3, and R4. A publish happens only when every line passes. R1 is integrity. It passes only when the binding matches, signature_ok is yes, and trust_anchor is yes. A trusted manifest with a hash miss fails R1, reason hash. A bad signature fails R1, reason signature. A valid manifest with trust_anchor no fails R1, reason trust. R2 is the machine mark. When the origin is trained or composite, the claim names digitalSourceType as trainedAlgorithmicMedia or compositeWithTrainedAlgorithmicMedia. Those are the names for fully synthetic media and for media that mixes a capture with synthetic media. An empty type fails R2, reason mark. Origin camera or assistive passes R2 with no type required. R2 follows the origin. The paragraph 2 calendar can still be inside the later date for an older system, and R2 blocks anyway.

R3 is the label a person can perceive. A synthetic image, audio, or video needs one. The overlay text AI-generated passes for any of those three kinds. On an artistic, satirical, or fictional work, the credits text Contains AI-generated scenes also passes, and the overlay may be empty. A deep fake that carries only the machine-readable mark fails R3, reason label. Public-interest text needs the sentence Written with an AI system, unless the editorial exemption holds. A typo pass with an empty editor fails that exemption. Text outside the public interest passes R3. R4 is consent and license. A non-empty subject_id needs a registry row with status allow, the same use as the job, and an expires date on or after the run date. Expires is the last valid day. An empty subject_id skips consent. The license code own passes. The code cc-by passes when credit_line is non-empty. The code editorial-use passes only when the job use is news. The code none fails. A miss records reason consent, reason license, or both.

Asset E is a synthetic image from a system placed on 20260701, run on 20260901. The origin is trained, digitalSourceType is empty, the overlay is empty, the subject is empty, and the license is own. The bytes are 5, 5, 5, 5, 5, 5, 5, 6, the exclusion excludes nothing, the sum is 41, and the claim states 41. signature_ok is yes and trust_anchor is yes. Paragraph 2 stays off until 20261202. R1 passes. R2 fails, reason mark. R3 fails, reason label, because a synthetic image still needs a perceivable label under the Red Lines. R4 passes. The file stays unpublished. Asset D is public-interest text, origin trained, type trainedAlgorithmicMedia, eight bytes of 4 with an empty exclusion, sum 32, stated hash 32, signature and trust yes. The review only fixes typos, the editor field is empty, and the sentence Written with an AI system is absent. R1 passes, R2 passes, R3 fails with reason label, and R4 passes because the subject is empty and the license is own.

An example

One video through the four lines

Asset A runs on 20260901. The kind is video, the origin is trained, and the system was placed on 20260810, so paragraph 2 is already due. The type trainedAlgorithmicMedia fills that duty. The clip is a deep fake and the work is outside the artistic case, so the overlay has to carry the disclosure. The overlay text is AI-generated. The bytes and the exclusion are the ones in the hash section: the hand hash is 39, the claim states 39, signature_ok is yes, and trust_anchor is yes. The manifest is trusted and the binding matches. The watermark distance is 1. The subject is p7, the job use is news, the consent row has status allow and use news, and expires is 20261101. The license is cc-by and the credit line reads Still from North Archive.

R1 passes on trust plus the matching hash. R2 passes on trainedAlgorithmicMedia. R3 passes on the overlay. R4 passes because 20260901 sits on or before 20261101 and the credit line is present. The record you can tick is hash 39, distance 1, manifest trusted, R1 pass, R2 pass, R3 pass, R4 pass, publish yes.

Asset B on the same day keeps the claim, the overlay, the consent row, and the license. The first byte is 41, the hand hash is 40, and the watermark distance is 0. The manifest stays trusted because the signature still covers the old claim. R1 fails, reason hash. R2, R3, and R4 pass. Publish no. The single block is the broken hard binding.

Exercise

Mark asset K on paper

Asset K runs on 20260901. The kind is video, the origin is composite, and the system was placed on 20260720. The clip is a deep fake and the work is artistic. The credits text is Contains AI-generated scenes, and the overlay is empty. digitalSourceType is compositeWithTrainedAlgorithmicMedia. The bytes are 8, 8, 8, 15, 15, 15, 20, 4, and the exclusion is [3, 6). The claim states 48. signature_ok is yes and trust_anchor is no. The expected watermark is 10110010 and the recovered watermark is 11110010. The subject is p2, the job use is ad, the consent row has status allow and use ad, and expires is 20260801. The license code is editorial-use. Write the hand hash, the Hamming distance, and whether paragraph 2 is due. Then write each Red Line with pass or fail and the reason, and say whether the file publishes.

The excluded bytes are the three 15s. The included bytes are 8, 8, 8, 20, and 4, and they sum to 48. Then 48 modulo 97 is 48, so the binding matches the stated hash. The watermark differs at position 1, so the distance is 1 and the soft binding passes. The system was placed before 20260802 and the run date falls before 20261202, so paragraph 2 stays off. R2 still passes, because the type is compositeWithTrainedAlgorithmicMedia. R3 passes on the credits text. R1 fails, reason trust, because trust_anchor is no, so the manifest is valid and stops short of trusted. R4 fails with two reasons: consent, because 20260901 falls after 20260801, and license, because editorial-use allows only the use news. Publish no.

Check questions

Answer on your own first. Then open a question to see the answer.

What hand hash does asset A produce, and what publish decision does the gate record?

The hand hash is 39. All four Red Lines pass, and the record says publish yes.

Asset B keeps a claim that states 39 while the first byte is 41. What is the hand hash, what is the watermark distance, and which Red Line blocks the publish?

The hand hash is 40, the watermark distance is 0, and R1 fails with reason hash. The manifest stays trusted.

On run date 20260901, asset E comes from a system placed on 20260701. Is Article 50(2) due, and which Red Lines fail?

Article 50(2) stays off until 20261202. R2 fails with reason mark, and R3 fails with reason label. R1 and R4 pass.

A deep fake carries trainedAlgorithmicMedia, with an empty overlay and empty credits. Which duty stays open, and which credits text closes an artistic deep fake?

The deployer duty in Article 50(4) stays open, because a person has no perceivable label. The credits text Contains AI-generated scenes closes R3 for an artistic, satirical, or fictional work.

Take with you

Publish only when the manifest is trusted and the hand hash matches, the synthetic origin is named in the claim, a person can perceive the disclosure the deployer owes, and both the consent row and the license code still allow the job.

Final task

Submit a media compliance gate (media_gate.py) that passes 35 automated tests: embedding valid machine-readable provenance manifests into image/audio/video files, verifying cryptographic manifest integrity, injecting visible Art. 50 labels, and blocking assets lacking consent records.

The final task is marked against fixed answer keys and automated tests once the tests open.

Terms in this course

This course has no terms of its own in the glossary yet. Terms from earlier courses are used here too.

More lessons coming

The first lesson is open to read. The rest of the course is being written, and tests and diplomas come later. Join the waitlist