Document transparency and AI regulation
From 2 August 2026, the EU AI Act applies generally, including certain transparency obligations. Validator provides a verifiable document-traceability layer that can support transparency, audit and compliance processes.
Article 50 of the EU AI Act sets transparency obligations for certain providers and deployers. They include technically detectable marking of certain synthetic outputs, informing people when they interact with certain systems, and disclosure of deepfakes and certain AI-generated or manipulated text published to inform the public on matters of public interest, subject to the exceptions in the Regulation. These obligations apply from 2 August 2026.
Spain is processing Organic Bill 121/000096 on the proper use and governance of artificial intelligence, introduced on 28 May 2026. As of 21 July 2026 it remains before Parliament and the amendment deadline has been extended to 2 September 2026. It is not yet law.
The regulatory framework does not prescribe one technical solution for every document. It does make it increasingly important to explain and document, proportionately, when and how AI was involved and under whose responsibility.
A visible notice or mark can state that AI-generated or manipulated content is present. It does not always document how the system participated, what human review occurred, who assumed responsibility, or which exact document version the declaration referred to.
Institutional documents, academic publications, professional reports and administrative communications may need an additional layer: a verifiable declaration bound to a specific version and auditable with open tools.
A PTC declaration records the stated conditions of AI participation: operator, system, co-creation mode, human review, purpose and other contextual data. It then cryptographically binds that declaration to the document object.
If the linked content, the declaration or its contextual conditions change, verification detects the divergence. The current profile’s three hashes protect distinct scopes: document object, PTC block and declared ethical context.
Validator creates and verifies PTC declarations and checks their technical conformance with the current normative corpus. It can show that the declaration corresponds to the declared document object and that all three hashes are coherent.
All processing runs locally in the browser. Documents are not sent to a server, no account is required, and a portable version is available for offline environments and internal networks.
Validator covers a specific function within a compliance process: verifiable document traceability. It can complement transparency, labelling, technical marking, supervision or archiving duties; it does not automatically replace them.
Validator does not by itself determine the material truth of a declaration, scientific quality, the operator’s good faith or full legal compliance in a specific case. Nor does it replace obligations applying to providers, deployers, editors or platforms.
Its result does support a precise statement: the artifact technically conforms to the PTC protocol and the preserved declaration corresponds to the verified document object. That evidence can be integrated into internal policies, audits, publications and transparency procedures.
PTC originated as an open document-traceability protocol. Its regulatory usefulness is complementary: it documents a dimension that a visible label alone may not preserve.