Nova Reel and Designer on how the credentials are scoped
Both write credentials under the same specification, and neither claims to cover everything. One draws its boundary at a version number, the other at a set of features, and the two boundaries behave differently over time. From 2 source pages, read 2026-09-22; no maker pays to be listed.
| Point | Amazon Nova Reel | Microsoft Designer |
|---|---|---|
| How the scope is drawn | From version 1.1 onward | All images created with the editing features |
| What a reader can sort by | When the file was rendered | Which part of the product made it |
| What the credential is said to hold | The model and the platform used | Provenance viewable on a public site |
Inclusion rule. Two entries whose published answers to one column pull in different directions. Cells hold each vendor's own wording from the page its entry names; pairs that agree on the column are not filed at all. Order. Fixed order, and the two columns are in the order the heading gives them.
1A version boundary ages; a feature boundary does not
A sentence naming a version stays true while the version number moves on, and stops being the whole picture without anybody editing it. A sentence naming a feature keeps meaning the same thing until the feature is renamed.
For a register that matters, because the check date under an entry is doing more work in the first case. A reader comparing an old row with a current page should expect the version to be the field that moved.
2Both boundaries are usable, for different questions
A version boundary sorts a library by time, which a delivery record answers in one field. A feature boundary sorts it by workflow, which a team usually knows without any record at all.
Neither is the better claim. What they have in common is being narrow enough to apply, which is more than a general statement about a service applying provenance would offer.
3The same standard does not mean the same coverage
Adopting one specification makes two vendors' manifests readable by the same tools. It says nothing about which of their outputs carry one, and this pair is the clearest demonstration of that in the record.
So a reader who has learned to recognise the format has learned to read a file, not to predict one. Coverage is a separate row on both entries for exactly this reason.
- Amazon Nova ReelVersion 1.1 adds Content Credentials based on the C2PA specification, carrying the model and the platform usedthe second provenance layer
- Microsoft Designer (microsoft.com)Content credentials, provenance based on the C2PA standard, are applied to all images created with the editing featuresan image generation and editing tool
4What one generator does with its output
Against the duty in “Nova Reel and Designer”, SceneMixer's published pages describe what its pipeline produces:
Recommended is a badge on the tier the site suggests for most finished segments. You stay on the default, 480P, until you pick another tier.
SceneMixer, Wan 3.0 · 720P: the recommended tier — “Does Recommended mean 720P is the default?” (read 2026-10-13)
Each line is generated with the picture, in the voice chosen for that character, and the speaker's lips move with the words.
SceneMixer, Dialogue Lines: Delivery Notes, Voice-Over, Captions and the Voice Tag — “Is the dialogue really spoken in the video?” (read 2026-10-13)
5Sources
Read from the AI service card at docs.aws.amazon.com and the support FAQ at support.microsoft.com, consulted 2026-09-22. Full entries: Amazon Nova Reel and Microsoft Designer. The column itself is on What it asks for. Other pairs on file: AudioSeal and SynthID, Wan and Firefly.