Simulated: the items, steps, and apps are made up. This page does not check real Content Credentials.
See it in a feed and in an article
Common badge
Honest label
What the label says
Follow one photo from camera to screen
The credential is lost at one step. Turn on the check box to see the platform keep it.
What the label says now
Six items, one label style at a time
How it works
Try this
- Pick the Stripped item. Compare the feed post and the article in both views.
- Select Play. Watch the credential chip. Find the step that removes it.
- Turn on "The platform keeps the manifest". Play again. Then try Quiz mode on the six items.
Pain point
People cannot tell where content came from, because the proof is often missing.
Problem statement
A common badge says verified or not. Some platforms strip the manifest on upload, so a real photo can look fake.
What sparked it
C2PA Content Credentials have uneven coverage, and some platforms strip them on upload.
Why this approach
Use three states, not two: signed, unsigned, and stripped. Each state says why, and unknown never reads as fake.
Hypothesis tested
We believed that three honest states build more trust than a common badge. If it holds, readers will not trust an Unsigned item less than a badged one.
How to try it
- Open the Prototype tab. Compare the common badge with the honest label.
- Select Play in the photo journey.
- Select "Why this label?" on one card in the list of six.
- Turn on Quiz mode and answer for each card.
What this does not do
- It does not read or check real Content Credentials.
- The items and names are made up.
- A Signed label does not show that the scene is true.
Notes
- Buyer: a newsroom, platform, or brand that shows media origin.
- First customer: a news publisher that signs its own photos.
- Model: a monthly fee per publisher. This is an assumption.
- Weak spot: users may ignore labels.
- Feedback: which words in the three labels are still unclear?
Traces
| Step | Prompt | Model | Tool | Date |
|---|
Cost
| Step | Model | Input tokens | Output tokens | Cost (USD) |
|---|---|---|---|---|
| Total | ||||
Measured: the author runs used 188,801 tokens in total. Estimated: the split into input and output tokens (90 percent input, 10 percent output) and the dollar cost, at $2 input and $10 output per million tokens for Sonnet 5.5 (about $0.53). The run reported one total only. The lead session's planning, research, and publishing are not included. The prompts in the Traces section are listed in the order they were given.