Skip to main content

Certificates & Trust Badge

Passing a run is ephemeral; a Certificate of Conformity is the durable, verifiable artifact that proves it. It is the physical embodiment of the CertOps motto — "Trust, But Verify." When a run is Certified, you can mint a signed certificate that a compliance officer, an auditor, or a customer can independently verify.

What a certificate is​

A certificate is a signed, immutable record that a specific suite passed all its blocking quality gates on a specific run. It captures:

  • the suite name and run number it attests to,
  • the verdict (Certified) and the time it was issued,
  • a quality summary — the headline metric results behind the pass,
  • an optional tag (e.g. prod),
  • a cryptographic signature that makes tampering detectable,
  • and a PDF (delivered as a short-lived pre-signed link).

Certificates are only issued for Certified runs — attempting to generate one for a rejected run is refused.

Issuing a certificate​

From the CLI, address a run by its run number (the short #42 id, not the UUID):

certops certificate generate 42

Fetch an existing one for a run:

certops certificate show <run_uuid>

Under the hood these call POST /v1/certificates/generate/{run_number} and GET /v1/certificates/run/{run_id}.

The public Trust Badge​

Every certificate has a public verification endpoint that requires no authentication — this is what powers a "Verified by CertOps" badge you can embed anywhere:

certops certificate verify <certificate_id>

This hits GET /v1/verify/{certificate_id}. Anyone — a prospective customer, a regulator — can confirm the suite name, run, verdict, and signature for themselves. The public response deliberately omits the PDF link, exposing only the facts needed to trust the badge, never the internal report.

Where it fits​

certops run  →  Certified  →  certops tag (optional baseline)
             →  certops certificate generate <run_number>
             →  signed Certificate of Conformity + public Trust Badge

A certificate closes the loop: the manifest defines the standard, the run enforces it, and the certificate is the receipt you can show the world.