Synthetic content not machine-readable-marked

Mark every generated image, audio, video, or text output with machine-readable provenance, such as a signed C2PA manifest or watermark, before it is saved, served, or published.

In the generation service, a marking step sits between the generator call and every sink (image.save, s3.put_object, blob.upload, FileResponse, res.send, publish). Images, video, and audio get a signed C2PA manifest whose actions record digitalSourceType trainedAlgorithmicMedia, and where robustness matters an invisible watermark as well (imwatermark WatermarkEncoder, AudioSeal, SynthID) so the mark survives metadata stripping. Generated text carries provenance metadata in the API response or document, or a text watermark where the model provider offers one. Sinks accept only the marked artifact, and a test confirms the mark is present and detectable.

Where it goes: 9 AI output handling, 1 application source code, 12 repository artifacts.

What reviewers look for: c2pa signing (c2pa.Builder / builder.sign, c2patool, @contentauth/c2pa, c2pa-node) or a watermark encoder on every path from images.generate, audio.speech.create, or a diffusion pipeline to a save or serve call; a test that reads the mark back from a generated sample.

image = pipe(prompt).images[0]   # StableDiffusionPipeline
image.save(out_path)

image = pipe(prompt).images[0]
content_id = uuid.uuid4()
bgr = cv2.cvtColor(np.array(image), cv2.COLOR_RGB2BGR)
enc = WatermarkEncoder()
enc.set_watermark('bytes', content_id.bytes[:4])   # 32-bit id, detectable later
cv2.imwrite(tmp_path, enc.encode(bgr, 'dwtDct'))
sign_c2pa(tmp_path, out_path, content_id=content_id)   # our helper around c2pa.Builder.sign

Engineering guidance, not legal advice. Each provision below may add its own details (a cadence, a deadline, a required notice element): open it for those.