Public Certification Registry

The Public Registry is in development.

We are building the public verification service that will allow people to check an issued Clause5afe certification, its approved scope, and its current status. No certification records are currently published.

Authoritative record

What a public certification record is designed to show.

Public verification should be specific enough to test a claim while preserving private evidence, evaluator work product, security-sensitive material, and client-confidential information.

Certification IDDurable public identifier
Certified organizationLegal or approved public organization name
Certified systemSystem and product identity within the approved public scope
Version / scopeThe version, deployment boundary, and use context covered by the certification
IssuedCertification decision and publication date
Valid throughCurrent certification validity period
Current statusThe approved public status, effective date, and any publishable status context
MonitoringWhether continuous monitoring is activated for the certification, where publishable

Status behavior

A certification should not disappear when its status changes.

Registry history preserves the public meaning of a certification over time. Status terminology follows the approved controlled policy set; the website interface does not define or override it.

Current state

A public record must make clear whether the certification may presently be represented as active for the published system and scope.

Interim or conditional state

Where the governing certification policy permits an interim, conditional, hold, or suspension state, the Registry must show its public effect without implying a broader certification than the controlled decision supports.

Non-active state

When certification is no longer current, the historic record should remain verifiable rather than disappear, with the approved reason/status terminology and effective date preserved.

Changed decision

A correction, appeal outcome, reinstatement, superseding certification, or other governed status change should create auditable history rather than overwrite the public past without trace.

Independent verification

One record. Different diligence questions.

Buyers and procurement

Check that a certification claim resolves to the system, scope, version, and status being represented in a transaction or diligence process.

Boards, investors, and insurers

Verify the published certification record directly rather than relying on a screenshot, presentation, or static badge.

Regulators and public institutions

Review the public certification record and its stated boundaries without receiving private client evidence or internal evaluator material.

The public

Confirm whether a Clause5afe certification mark corresponds to a current public record and report suspected misuse when it does not.

Publication boundary

The Registry is public. Certification case data is not.

Client applications, evidence, findings, reviews, decisions, material-change records, and controlled case history belong in the authoritative private certification system. Only approved publication fields may cross into the public Registry through a narrow read-only interface.

Certification PlatformApproved publication recordPublic Registry

Certification marks

A badge should point back to proof.

Any issued Clause5afe certification mark or QR verification must resolve to the current Registry record rather than function as standalone proof. Suspected misuse routes into a controlled review process.