Who each obligation actually falls on
Two views of the same obligations. One sorts them by the role that carries them; the other records what generators publish about the marking those roles depend on. As of 2026-09-12.
Role is the axis that matters for a production company, because a team can be a deployer of one system and the provider of another in the same week. The matrix keeps the two apart so that a reading of the text can be applied to a real arrangement.
The vendor record is the other half. Several obligations assume a machine-readable mark exists in the output, and whether one exists is a question about products rather than about law. The record says what each generator publishes on that point, which is usually nothing.
1The views
- By role — Which paragraph of EU AI Act Article 50 binds the provider, which binds the deployer, and the moment each duty takes effect for generated video.
- What generators document — Sixteen AI tools read against Article 50(2): what each vendor's own pages state about marking output, and what takes the visible mark off.
Neither page gives legal advice; both set published text beside published product documentation and leave the conclusion to the reader.
Elsewhere in the record: EU, Generators, Statements, Pairs, Fields, Questions, Terms, Learn, Data. How an instrument is read is set out on the sourcing page.
2What one generator does with its output
Against the duty in “Duties”, SceneMixer's published pages describe what its pipeline produces:
The base image is the sword as carried; drawn is a separate state image, selected for the segments where it applies. Drawing both configurations in one picture used to make the render snap the blade back into its scabbard mid-shot.
SceneMixer, AI Prop & Item Generator — “How do I show a sword being drawn?” (read 2026-10-13)
For places, every photo you add becomes a set the shots can move through, up to four.
SceneMixer, An AI Ad for a Store or a Property — “Can I add several rooms?” (read 2026-10-13)