There are two registers: differences between the CWC Registry and EVIDE

The CWC Registry is used to publicly verify that a specific CWC code has been issued for a given URL or declared content within the </AI> Protocol.

EVIDE, instead, is the evidentiary registry designed for the deposit of digital evidence, outputs and decisions, anchored through SHA-256 hashing, timestamping, and, where applicable, FEDIS support.In short: the CWC Registry verifies a public declaration, while EVIDE anchors and records evidence or decisions in a forensic, evidentiary context.

Explore the protocol infrastructure:

→ The </AI> Protocol
→ From decision to defensible structure: when supervision becomes evidence
→ Read the Public Technical Specification
→ Verify a CWC Code in the Public Registry
→ EVIDE – Evidentiary registry for digital content and decisions
→ CWC Registry Policy
→ Request an Official CWC Verification Code
→ AI Governance Documentation Framework
→ Implementation Guide: verifiable AI supervision
→ Oversight Bias: why human supervision can fail in AI systems
→ Decision Attestation Layer: the missing evidentiary layer in AI governance
→ AI Evidence Officer: proving human supervision in artificial intelligence systems
→ Evidentiary Layer in AI Governance
→ </AI> Protocol FAQ: questions and answers about the framework

Related reading:

→ AI Data Poisoning: The Attack No Antivirus Can Stop
→ Human in the loop: why saying there is human oversight is not enough
→ Real cases: when AI governance fails — and what should have been provable
→ AI Governance: when something has already gone wrong – forensic reconstruction and digital evidence

Work with us:

→ Legal Partners Network

Code Status

• Active – the code is valid and the content is published as originally supervised
• Corrected – the content has been updated after publication; the correction is documented and traceable
• Retracted – the code is no longer valid; the associated content has been removed or formally withdrawn

HOE Class (Human Oversight Event Class)
Indicates the type of oversight event recorded:

• CONTENT – specific web or editorial content
• SOCIAL – content published on social media platforms
• DOMAIN – oversight at site or domain level
• PROCESS – automated processes or decisions
• LEGAL – legal or contractual contexts
• REPORT – technical reports or formal documentation

HOE Level (Evidence Level)
Indicates the evidentiary strength of the oversight event:

• L1 – Declarative – oversight declared without verifiable technical evidence
• L2 – Verifiable – presence of hash, timestamp or verifiable technical elements
• L3 – Forensic – verified identity (e.g. DAPI), cryptographic integrity, FEDIS declaration and complete forensic structure

Note
The CWC Registry serves as a public verification anchor for codes, URLs and declarations associated with the </AI> Protocol.

It is not the same as EVIDE, which is the evidentiary registry dedicated to the deposit of digital evidence and finalized decisions.

L3 classification does not depend on organizational size, but on the evidentiary structure in place.

Full details of the oversight event are retained in the technical documentation associated with the CWC code and are accessible upon request to parties with a legitimate interest.

The CWC Registry is designed to support scalable integration with external professionals and compliance partners.

Structured Adoption of the </AI> Protocol

The </AI> Protocol provides public transparency through verifiable codes.
Organizations seeking a broader governance structure – including verified supervisor identity, internal oversight workflows, output protection and evidentiary documentation – can adopt a dedicated operational framework.
→
Learn more about the AI Governance Documentation Framework

Evidentiary validity independent of the CWC Registry

The CWC Registry provides transparency and independent verification for codes and declared content.

However, evidentiary validity does not depend on the registry itself. Each CWC code can be supported by a FEDIS declaration, including SHA-256 cryptographic hash and qualified timestamp under eIDAS regulation. These elements guarantee integrity, certainty of date and non-repudiation, making the proof valid regardless of the recording platform.

When the objective is to register and anchor evidence, outputs or finalized decisions in a structured evidentiary context, the dedicated reference point is EVIDE.

The CWC Registry makes the code verifiable. FEDIS makes it defensible. EVIDE makes the evidentiary deposit explicit and accessible.

Note: The CWC Registry is a public access point for verification, not a technical dependency for proof validity.

The framework is publicly defined as “The </AI> Protocol” and is forensically certified through CertifyWebContent.
This documentation constitutes a verifiable, timestamped record of its structure, concepts, and implementation.