DCL-03 v0.3 — Technical Specification of the disclosure-notice-v1 Profile: Verifiable Public Notice for AI-Generated or AI-Modified Content

DCL-03 v0.3 — disclosure-notice-v1 DCL-03 defines the normative disclosure-notice-v1 profile for creating a verifiable public notice that declares AI intervention on an exact file protected through the Canal Transparency Protocol (PTC/CTP). The profile introduces a protected PTC DISCLOSURE block that is composed with a PTC FILE REFERENCE generated according to FRS-01. Both form a single canonical object protected by a single PTC. DCL-03 specifies: the grammar and byte-level serialisation of PTC DISCLOSURE; closed values for the declared type of AI intervention; treatment of the notice language; syntax and limits of an optional verification_url; composition with file-reference-sha256-v1; deterministic generation of PUBLIC_NOTICE/notice.txt; requirements for optional notice.html, notice.svg and qr.svg presentation artefacts; integration with the Validator Package Format defined by PKG-02; independent GREEN, AMBER and RED disclosure states; conformance vectors, negative cases and interoperability requirements. In version 1, PTC DISCLOSURE may appear only as the second block of a canonical object whose first block conforms to file-reference-sha256-v1. It may not appear independently and it does not create a second PTC or a fourth normative hash. notice.txt is the only derived public-notice artefact whose byte-for-byte equality forms part of the disclosure verification axis. HTML, SVG and QR representations are presentation artefacts and are not independent cryptographic authorities. The disclosure result remains separate from the PTC, source-file and package-conformance results. DCL-03 does not create a global verdict and does not apply a “worst result prevails” rule. DCL-03 can verify that a protected declaration states one of the permitted categories of AI intervention and that the normative public notice corresponds deterministically to that declaration. It does not determine automatically whether content was generated or modified with AI, certify the material truth of the declaration, classify content legally as a deepfake, certify compliance with a specific legal obligation, prove that a notice was actually shown to the public, or guarantee the future availability or content of a verification URL. Normative references R-01 v1.1 — Canonical Text Specification for the Canal Transparency Protocol (PTC/CTP). DOI: 10.5281/zenodo.21406620 PTC-F v1.2 — Functional Specification of the Canal Transparency Protocol (PTC/CTP). DOI: 10.5281/zenodo.21406680 FRS-01 v0.3 — Technical Specification of the file-reference-sha256-v1 Profile for the Canal Transparency Protocol (PTC/CTP). DOI: 10.5281/zenodo.21830122 PKG-02 v0.4 — Validator Package Format 2.0: Transport, Preservation and Reconstruction of a Verifiable Structure. DOI: 10.5281/zenodo.21830169 DCL-03 forms part of the normative specification set of the Canal Transparency Protocol together with R-01, PTC-F, ARCH, FRS-01 and PKG-02. Reference implementation Validator implements the normative specification set as the reference implementation of the Canal Transparency Protocol and is also distributed for local execution. DOI: 10.5281/zenodo.21833853 Language editions This record contains the technically frozen v0.3 specification in Spanish, English and French. The Spanish version has linguistic precedence. The English and French editions are linguistic translations of the same normative specification and do not create separate technical versions. Normative identifiers, profiles, field names, paths, hashes, preimages, exact fixtures, PTC blocks and the nine normative notice.txt strings are preserved where required. Human–AI transparency Final decision and responsibility: Manuel Barrera Anglada. Drafting and consolidation: GPT-5.6 Thinking (OpenAI). Adversarial review: Claude Sonnet 5 (Anthropic), including review of v0.1 and cross-check of the v0.2 independent review. Independent review: DeepSeek, v0.2, subsequently cross-checked by Claude Sonnet 5. Human decision and final approval were retained throughout the process. Status: Technically frozen — authorised basis for implementation.