Skip to content

Add info on created v gathered assertions#306

Open
crandmck wants to merge 2 commits intomainfrom
created-gathered
Open

Add info on created v gathered assertions#306
crandmck wants to merge 2 commits intomainfrom
created-gathered

Conversation

@crandmck
Copy link
Collaborator

@crandmck crandmck commented Feb 18, 2026

@netlify
Copy link

netlify bot commented Feb 18, 2026

Deploy Preview for cai-open-source ready!

Name Link
🔨 Latest commit 008d709
🔍 Latest deploy log https://app.netlify.com/projects/cai-open-source/deploys/69974d43436d94000813cb81
😎 Deploy Preview https://deploy-preview-306--cai-open-source.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@github-actions
Copy link

github-actions bot commented Feb 18, 2026

@github-actions github-actions bot temporarily deployed to pull request February 18, 2026 19:25 Inactive

### Configuration in SDK settings

Configure the settings file with the created assertions like this:
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To confirm: The below settings make the SDK create all assertions with those labels into created assertions?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes and also the assertion versions. So "c2pa.actions" will include c2pa.actions.v2 also. An assertion can also be set as created in the manifest definition with created: true

Copy link
Collaborator

@timmurphydev timmurphydev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good, Rand. I think you explained it really well.

My overall comment on the subject of created vs. gathered assertions is that they need to be configured intentionally and reflect the actual claim generating environment. Some assertions may be commonly be configured as created, but that doesn't mean it will be true for all claim generators.


### Configuration in SDK settings

Configure the settings file with the created assertions like this:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes and also the assertion versions. So "c2pa.actions" will include c2pa.actions.v2 also. An assertion can also be set as created in the manifest definition with created: true


* “This image was generated using Adobe Firefly”
* “This video was edited in Premiere Pro”
* Custom metadata like author name, title, or usage rights
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this referring to custom assertions?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments