25 September 2026¶
Weekly Summary Letter
2026/09/25 Weekly Summary Letter
Hi NUMBERS,
This is Tammy, closing out September with you. This month, the central provenance question moved from whether a source is authentic to whether its use, transformation, and delivered result can still be explained. Across Numbers Protocol's September work, a licensed source was only the beginning. The more useful record connected the source to permission, action, output, and review.
The month opened with a practical handoff test. A source should be checked before it leaves, the public rendition should be identified after delivery, and the relationship between those copies should be written down. Exact, recovered, similar, and unsupported are not interchangeable outcomes. A verification result from the source cannot simply be carried forward as if it also described every copy that a platform, editor, or recipient handled. The record has to follow the asset through the real workflow.
That distinction became concrete in the work around Verify Engine and published copies. A file can be cropped, resized, compressed, downloaded, or reposted while still looking familiar. Verify Engine can validate supported C2PA records and search Numbers-registered assets for exact or similar relationships where the format supports it. Similarity can help reconnect a transformed copy to a known source, but it is not a verdict that two files are identical. The reviewer still needs a sentence in plain language: exact match, same image modified, no match, or not supported by this check.
Numbers Protocol gives each side of that handoff a place in the record. Capture and ProofSnap can register the source and give it a persistent NID. Asset Profile keeps the provenance history readable. The receiving team can check the copy it actually received instead of borrowing trust from the original file. That is not a promise that every transformation preserves proof automatically. It is a more honest workflow for showing what survived, what changed, and where the evidence stops.
By the end of the month, the focus had moved from permission to use. A license can say what someone was allowed to do with an asset. It does not, by itself, show whether the asset was used, where it went, what action changed it, or which output came from it. Numbers Protocol's Commit API can record actions, license details, and custom metadata such as where an asset was used. When a new output is registered, its NID gives that result a persistent reference while Asset Profile keeps the histories inspectable. Provenance becomes infrastructure when it explains how this output came from that source.
To everyone holding NUM, capturing assets, testing delivered copies, checking verification results, sharing proof paths, and asking better questions about what a record can support, thank you. Your participation makes this infrastructure more useful. Each registration, review, and honest boundary between known and unknown helps prove that provenance belongs inside the workflow, not only in the final caption. Human truth. Machine proof. is strongest when the next person can inspect the same story without relying on a screenshot, an old chat, or the memory of the original operator.
As usual at weekends, the team will respond a little more slowly while taking some rest. Our moderators will keep supporting you, and the team will be well prepared for the new month.
Best,
Tammy