PTC

Protocol and specifications

The Canal Transparency Protocol (PTC) is published as an open corpus of six documents with distinct functions. Validator.es is a reference implementation; it is not the protocol.

Corpus map

The shared core combines with specialised profiles and formats. ARCH spans the whole set as the architectural framework. FRS-01 can be used directly or within Package Format 2.0; DCL-03 is an optional extension of the exact-file path.

PTC specification map
FRS-01 does not require PKG-02: a standalone FRS record can be conformant and useful. PKG-02 applies when a complete Package Format 2.0 is generated or verified. DCL-03 is optional and does not replace PTC.

Current corpus

Core

The three common pieces that define the protected object, the declaration and the protocol architecture.

R-01 v1.1Core

Canonical Text

Text normalisation, canonical object, preimages and reproducible hash rules.

Published

DOI 10.5281/zenodo.21406620

Zenodo ↗
PTC-F v1.2Core

Functional PTC specification

PTC fields, order, allowed values and the semantics of each declaration.

Published

DOI 10.5281/zenodo.21406680

Zenodo ↗
ARCH v0.3Architecture

Normative architecture

Corpus governance, relationships among specifications, adapters and operating modes.

Published

DOI 10.5281/zenodo.21406665

Zenodo ↗

Profiles and formats

Specialised profiles that extend the core without redefining it.

FRS-01 v0.3Exact-file profile

file-reference-sha256-v1

Binds a PTC declaration to the exact bytes of any file using SHA-256.

Published

DOI 10.5281/zenodo.21830122

Zenodo ↗
PKG-02 v0.4Package format

Validator Package Format 2.0

Defines the interoperable ZIP used to transport, preserve and reconstruct verifiable pieces.

Published

DOI 10.5281/zenodo.21830169

Zenodo ↗
DCL-03 v0.3Optional disclosure

disclosure-notice-v1

Optional extension for preparing and verifying a public notice associated with AI content.

Published

DOI 10.5281/zenodo.21830264

Zenodo ↗
Published documents. All six specifications are published in ES/EN/FR with persistent DOIs. This page summarises their relationship; normative authority resides in the published documents.

Reference implementation

validator.es implements the current corpus. An independent implementation can be built from the published specifications without depending on this website or on El Canal.