28 August 2026¶
Weekly Summary Letter
2026/08/28 Weekly Summary Letter
Hi NUMBERS,
This is Tammy, closing out August with you. This month, AI transparency stopped sounding like a future policy debate and started behaving like an operating requirement. Article 50 of the EU AI Act began to apply on 2 August, and the Commission's August guidance made the practical question clearer: not only whether AI content is labeled, but whether the record still explains the exact asset, review, and decision after the file moves. Numbers Protocol was built for that harder job.
Throughout August, the team kept returning to the same gap from different angles. A machine-readable mark on the source file is only the first step. The version that actually reaches a newsroom, customer, moderator, or platform may be cropped, compressed, reposted, or stripped of context. That is why this month kept pushing us from labels toward receipts, from one original file toward the exact copy a human reviewed, approved, or challenged later.
One of the clearest signals this month was independent validation around the tooling layer. C2PA's Conformance Explorer lists Numbers Verify Engine as a conformant Validator Product, which matters because portability is only useful when another system can actually test the evidence it receives. In parallel, our August work kept grounding the same idea in practice: Capture SDK for recording the transition, Numbers ID for keeping the asset referenceable, Asset Profile for connecting versions and decisions, and ProofSnap for making source capture legible from the start.
The monthly story also became more concrete through the public examples we discussed. The Irish Times hoax and the Princess of Wales photo kill are different incidents, but they expose the same operational weakness: human involvement alone does not preserve proof. Teams still need to know which version was reviewed, what changed, who approved it, and what reached the public or the next recipient. Numbers Protocol does not replace editorial judgment, legal review, or source verification. It gives those decisions a durable record that can survive handoffs instead of disappearing into chat threads, folders, and memory.
That matters for everyone who holds, builds with, or advocates for NUM. Every asset registration, verification path, workflow event, and share that carries real context helps prove that provenance can work as infrastructure, not decoration. When the community tests one asset, follows one receipt, or asks one better question about the file in front of them, the network becomes more useful to the next person who needs to trust a result.
Thank you for helping close August with that standard. Numbers Protocol keeps getting stronger when proof survives the real workflow: export, review, publication, dispute, and reuse. Keep testing the file that actually moved, not only the one that left the first tool. That is how Human truth. Machine proof. becomes an operating habit, not a slogan.
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 week.
Best,
Tammy