Public Framework Specification · v1.0 Public Draft · May 2026

Universal Creation Evidence (UCE)

A public-draft framework for verifiable evidence linked to creative works, including cryptographic integrity, chronology references, and recorded assertions.

Universal Creation Evidence (UCE) is a public-draft, implementation-independent framework for preserving and verifying technical evidence associated with creative works. Copyright by UCE (CbyUCE) is the separate live operational implementation and current reference architecture.

UCE is an evidence framework — not a copyright registration system.

No institutional affiliation or endorsement. UCE is independent and is not affiliated with or endorsed by WIPO or any national copyright office. UCE evidence is not government copyright registration and does not replace national registration, legal advice, or adjudication. Find an official IP office.

Document
UCE Evidentiary Standards & Verification Framework
Version
1.0 Public Draft
Released
May 2026
Last Updated
May 2026
Status
Public Draft — Open for Review
Maintainer
Copyright by UCE (CbyUCE)
Documentation License
CC BY 4.0; UCE mark and trademark rights reserved separately

What UCE Provides — and What It Does Not

Clear scope. Defined limits.

UCE Provides

  • Verifiable chronology evidence
  • Cryptographic integrity verification
  • Tamper-evident evidence manifests
  • Published verification procedures
  • Machine-readable rights declarations
  • A record of claimant-supplied authorship, ownership, creation-date, and rights assertions

UCE Does Not Provide

  • Government copyright registration
  • Judicial ownership determination
  • Guaranteed legal outcomes
  • DRM or copy protection
  • Automatic enforcement of rights declarations
  • Proof that no earlier creator exists

Designed for Independent Verification

UCE evidence records are designed to be independently auditable using publicly documented verification procedures.

  1. 1Obtain the original file.
  2. 2Compute the file hash using the declared content hash algorithm.
  3. 3Retrieve the evidence manifest from its storage anchor.
  4. 4Canonicalize the manifest using the declared canonicalization method.
  5. 5Compute the manifest hash and compare to the recorded value.
  6. 6Validate the digital signature against the signed payload.
  7. 7Validate the public key reference and confirm it was valid at signing time.
  8. 8Confirm storage references, including content addresses and any ledger inclusion timestamps.
  9. 9Review creator, identity, and rights assertions, treating them as assertions unless separately attested.

Verification of a UCE evidence package does not independently determine legal ownership, validate the truth of claimant assertions, or adjudicate competing claims. A result establishes only the technical relationships it reports as checked; unavailable inputs and unperformed checks must remain explicit.

About this example. This is a live hosted convenience interface from the CbyUCE reference implementation. It currently displays the platform-recorded upload date, manifest Arweave block date, exact UTC technical details, manifest hash, platform public-key reference, raw-manifest access, block-explorer access, and JSON verification data. For the representative record observed August 24, 2026, the hosted result reported a matching manifest hash and valid platform signature; it did not report a successful public file-byte comparison, File Arweave Block Date, or Complete UCE Record Date. It is not proof of legal ownership, a WIPO-reviewed or WIPO-endorsed record, an independent technical audit, or the future provider-independent reference verifier.

Chronology in the Current CbyUCE Implementation

Distinct labels prevent a platform event from being mistaken for a network-confirmed time.

Platform-Recorded Upload Date

The date CbyUCE recorded receiving the upload. That platform-recorded value is contained in the signed evidence manifest subsequently submitted to Arweave. It is not described as Arweave-confirmed.

Arweave Block Dates

The uploaded file and evidence manifest are separate transactions. Their network-reported block dates are distinct from the platform-recorded value. If both block dates are available, the later date may be displayed as the Complete UCE Record Date.

The primary plain-language utility claim is proof of upload date. Calendar-date chronology is often the most practical public-facing claim; exact UTC values remain available for technical examination. Neither UCE nor CbyUCE is an RFC 3161 timestamp authority, qualified electronic timestamp provider, eIDAS trust service, governmental authority, or authoritative time source.

Framework Documents

Public specifications, technical references, and verification guidance associated with the UCE framework.

Download PDF (Framework v1.0 Public Draft) Verification & Conformance Status

Reference Architecture

The current UCE v1 reference architecture.

  • File hashingSHA-256
  • CanonicalizationRFC 8785 JSON Canonicalization (JCS)
  • Manifest hashingSHA-256
  • Digital signaturesES256 (ECDSA / P-256 / SHA-256)
  • Public verification keysPublished with key identifier and algorithm
  • Durable storage anchoringArweave Layer 1 or Arweave-compatible
  • RetrievalMulti-gateway retrieval
  • VerificationPublic verification URLs
  • CertificatesHuman-readable evidence certificates
  • RightsMachine-readable rights declarations

UCE is the public-draft framework. CbyUCE is the separate live platform used as the current reference implementation.

Research & Standards Direction

Areas of active interest for future revisions and interoperability work.

Post-quantum signature migration

Pathways to ML-DSA and hybrid classical/post-quantum signature schemes for long-horizon evidence.

Decentralized identity integration

Verifiable credentials and decentralized identifiers for stronger creator attestation.

AI provenance interoperability

Alignment with emerging content authenticity and provenance standards.

Rights-management interoperability

Machine-readable licensing and rights-routing across platforms and ecosystems.

Educational institution workflows

Reference workflows for institutional creator-evidence programs and archives.

Legal-tech integration

Workflow integration with copyright counsel, Copyright Claims Board, and related processes.

Public conformance test suites

Open test vectors and conformance suites for independent verifier implementations.

Reference verifier publication

A publicly documented reference verifier to support implementation and audit.

Use the UCE Framework Today

Copyright by UCE (CbyUCE) is the separate live operational implementation and current reference architecture. Use of CbyUCE is governed by its own Terms and Privacy Policy.

CbyUCE is a private evidence service, not a government or national copyright-registration service. Neither UCE nor CbyUCE is affiliated with or endorsed by WIPO or any national copyright office.