What is UCE? Evidence for Creative Works

What does UCE stand for?

On this site and in the creative-evidence framework, UCE means Universal Creative Evidence. The name describes the framework and its associated evidence mark. The framework is designed to support technical review across implementations and borders; the legal treatment of a record depends on the applicable jurisdiction and circumstances.

Short name

UCE

Full name

Universal Creative Evidence

Purpose

Verifiable technical evidence linked to creative works

Creative work examples

Photographs, illustrations, music, video, writing, and software

Publication status

Version 1.0 public draft

Maintainer

CbyUCE, an alternate name of 5 Race Street LLC

Reference service

CbyUCE

Public inspection tool

UCE Evidence Lens

Read the framework overview, UCE v1.0 specification, or governance and feedback process for more detail.

Examples of creative works and UCE evidence

A UCE record links evidence to a particular file. These examples illustrate the kinds of creative works and technical comparisons the framework describes; supported file types and size limits depend on the record-creation service.

• Photographs and illustrations: compare an image file with the cryptographic digest in its evidence record.
• Music and video: distinguish a particular recording or export from a later edited file by comparing their digests.
• Writing: associate a manuscript, script, or document file with its recorded evidence and chronology references.
• Software: compare a source-code file or packaged version with the file identified in an evidence record.

These checks concern file integrity and recorded evidence. They do not independently establish authorship, originality, ownership, or when the work was first created. See the public verification example for the inputs and checks currently available.

What is a UCE record?

A UCE evidence record associates a creative work with technical data and recorded statements. Depending on the record profile and available inputs, an inspection may examine:

• File integrity: whether the bytes of a supplied file produce the recorded cryptographic digest.
• Manifest integrity: whether the covered manifest fields reproduce the recorded manifest hash.
• Signature: whether a supported digital signature validates against the identified public key and signed payload.
• Chronology: the reported platform timestamp and available storage or ledger references, with their different meanings and limits.
• Assertions: the creator, claimant, rights, and other statements placed on record, distinguished from independently checked facts.

For example, a photographer can compare a local image's digest with the digest recorded in a supported public UCE manifest. A match supports the reported relationship between that file and the recorded digest. It does not by itself prove who took the photograph or who owns the copyright.

Not every tool checks every field or profile. Read the current verification coverage and limitations alongside any result.

What does the UCE mark mean?

The UCE mark signals that a corresponding verifiable evidence record exists for a work. The mark can accompany an image, audio release, document, portfolio, or other presentation of the recorded work.

During the public-draft period, eligibility requires a corresponding CbyUCE evidence record. The mark does not certify legal ownership, government registration, or institutional endorsement. See the UCE mark-usage rules and mark downloads before applying it.

How do UCE, CbyUCE, and UCE Evidence Lens relate?

• UCE is the framework. This site publishes its specification, mark guidance, governance, and verification status.
• CbyUCE is the record-creation service. CbyUCE is the separate live operational implementation and current reference architecture. Its own terms govern use of the service.
• UCE Evidence Lens is an inspection tool. Lens reports supported technical checks and limitations for public records. Browser and connector capabilities may differ; a dated inspection report is not a UCE Certificate or an independent audit.

To inspect a record, follow its public verification reference, review the checks actually performed, and distinguish confirmed technical relationships from recorded assertions. The public verification example provides a starting point.

Common questions about UCE

Does UCE prove authorship or copyright ownership?

UCE preserves technical evidence and recorded assertions. A valid hash or platform signature does not independently establish authorship, identity, legal ownership, originality, or non-infringement. Those questions require other evidence and may require legal determination.

Does a UCE timestamp prove when a work was created?

A platform-recorded upload timestamp, a ledger timestamp, and a claimant's stated creation date describe different things. None should be relabeled as independently proven creation time. A chronology result must state which relationship was checked and which inputs were available.

Is UCE an approved international standard?

UCE v1.0 is a public draft. It has not been approved as an international or consensus standard. UCE is independent and is not affiliated with or endorsed by WIPO or any national copyright office.

Does a recorded AI-training preference stop AI use?

A machine-readable declaration records the claimant's stated preference. It does not technically block scraping, create rights that do not otherwise exist, or guarantee compliance by an AI system.

How can I report an error or disputed claim?

Use the case-handling procedure for disputed assertions, corrections, suspected misuse, or security concerns. Framework feedback follows the published governance process.