PKG-02 v0.4 — Validator Package Format 2.0: Transport, Preservation and Reconstruction of a Verifiable Structure

PKG-02 v0.4 — Validator Package Format 2.0 PKG-02 defines an interoperable ZIP format for transporting, preserving and reconstructing a verifiable structure composed of an exact source file, its FRS-01 reference, a Canal Transparency Protocol (PTC/CTP) declaration, derived copies, routing metadata and, optionally, public disclosure materials. The specification defines which artefacts travel together, the authority of each artefact, how they are located, how their coherence is checked and how a verifier must respond to contradictions, structural defects or security risks. PKG-02 specifies: the minimum and extended structure of a Validator Package Format 2.0 archive; the roles and authority hierarchy of the source file, canonical object, PTC, derived copies and manifest; the grammar and semantics of manifest.json; deterministic relationships between the integrated record and its derived copies; generation, verification and reconstruction procedures; package conformance as an independent verification axis; ZIP path, entry and resource security requirements; compatibility with previous Validator packages and safe repackaging; interoperability, contradiction and adversarial-treatment vectors; optional transport of public disclosure materials governed by disclosure-notice-v1. A Validator Package Format 2.0 archive is a container for transport, preservation and reconstruction. It is not itself the protected cryptographic object and does not replace the authority of the exact source file, the canonical object or the PTC declaration. PKG-02 preserves the existing PTC architecture: one protected canonical object, one PTC and the three normative hashes. It does not create a fourth hash or a global cryptographic verdict for the package. The manifest is used for routing and reconstruction but is not treated as a source of truth. Assertions contained in manifest.json must be checked against the actual artefacts to which they refer. PKG-02 does not redefine R-01, PTC-F, ARCH or FRS-01. When public disclosure materials are present, their normative content and states are governed independently by DCL-03 / disclosure-notice-v1. 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 ARCH v0.3 — Normative Architecture and Governance Specification for the Canal Transparency Protocol (PTC/CTP). DOI: 10.5281/zenodo.21406665 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 DCL-03 v0.3 — Technical Specification of the disclosure-notice-v1 Profile. DOI: 10.5281/zenodo.21830264 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.4 specification in Spanish, English and French. The Spanish version is the frozen reference document. The English and French editions are linguistic translations of the same normative specification and do not create separate technical versions. Normative identifiers, JSON keys, internal paths, physical artefact names, executable fixtures, PTC declarative values, byte sizes, preimages and SHA-256 hashes are preserved where required. Human–AI transparency Final decision and responsibility: Manuel Barrera Anglada. Drafting and consolidation: GPT-5.6 Thinking (OpenAI). Adversarial reviews: Claude Sonnet 5 (Anthropic), including reviews of v0.1 and v0.3. Independent reviews: DeepSeek, including reviews of v0.2 and v0.3, subsequently cross-checked. Human review and final approval were retained throughout the process. Status: Technically frozen — authorised basis for implementation.