Provenpost
A per-piece provenance workspace separating exact content bytes, tool-use assertions, editorial actions, approval, signed manifests, publication readback, correction and revocation.
Agencies face buyers who want to understand whether and how automated tools contributed to published work. The supplied research confirms an active content-provenance standard, maintained browser tooling and two managed signing services. It found no reviewed multi-client agency workspace built around public verification pages. The standard makes a receipt technically feasible, but it does not make human-versus-model percentages measurable or a badge trustworthy by itself.
Provenpost would preserve agency, client, content identifier, exact content hash, asset version, source file, tool-use assertion, model identifier assertion, prompt-retention choice, contributor identity assertion, editorial action, reviewer, approval scope, rights assertion, manifest version, signer, signature result, timestamp observation, publication URL, published-byte readback, badge render, correction, revocation and replacement as distinct records. Claims about human contribution remain declared and reviewable rather than computed as objective percentages.
A hash can show that bytes match. A signature can support signer attribution and manifest integrity. A provenance manifest can record declared actions. None proves authorship, originality, factual truth, copyright ownership, lawful training data, human supervision or commercial clearance. A badge must expose its scope and evidence rather than saying content is verified. If the published bytes change, the old receipt no longer covers the new version.
The supplied December 2026 European transparency date is future as of authoring and described as a provider-side obligation; current primary authority and qualified counsel must decide whether an agency or client has duties. The pilot should cover one client and one piece with synthetic or rights-cleared assets. Buyer role is an agency operations, editorial or client-trust lead, but client demand, accepted evidence, signing custody, budget and differentiation from direct signing services remain open.
An agency operations, editorial or client-trust owner responsible for bounded, correctable disclosure of the production process behind published content.
Agency operations and editorial owners are actionable, while client demand, budget and accepted evidence need validation.
Manifest generation and verification pages scale through software across clients and content types.
Current standards and services make implementation easier, but the product is a workflow layer over existing signing capability.
The input identifies an agency buyer, confirmed provenance standards and managed signing interfaces, plus a concrete multi-client verification workflow.
Human contribution is not objectively measurable, direct signing products exist, legal scope is unsettled for the buyer and trust badges can become misleading claims.
Discussion
No comments yet — be the first to weigh in.
