Badge & mark usage
A badge that points to proof.
A CAI badge is only meaningful if it is checkable. The policy is short and it is the whole policy: a badge must link to the signed survey it represents, stamped with the rubric version, so that anyone who clicks it can verify both the number and who issued it.
Embed it
Point it at your repo; link it to the survey.
The badge SVG is served by the issuer at a canonical, cacheable endpoint — immutable per published run. Swap OWNER/REPO for yours. The link target is always the survey, so the badge is never a bare number with no provenance.
Markdown
[](https://app.watchdog.canine.dev/api/oss/OWNER/REPO/report)
HTML
<a href="https://app.watchdog.canine.dev/api/oss/OWNER/REPO/report"><img src="https://app.watchdog.canine.dev/api/oss/OWNER/REPO/badge.svg" alt="CAI"></a>
reStructuredText
.. image:: https://app.watchdog.canine.dev/api/oss/OWNER/REPO/badge.svg
:target: https://app.watchdog.canine.dev/api/oss/OWNER/REPO/report
:alt: CAI
The rules
Three, and they are all about provenance.
Must link to a record
A badge links to the specific signed survey it represents — never a bare number with nothing behind it.
Must state the rubric version
So the score is reproducible against the exact criteria it was computed under. Rubrics are immutable; the version is what makes the number checkable.
Must not imply certification
The CAI is a measurement, not a certificate. A badge says measured, with a verifiable record. It never says certified, approved or guaranteed.
The badge SVG and its endpoint are served by the surveyor; the policy above belongs to the standard, so every issuer's badge is held to the same bar. A badge you cannot click through to a verifiable survey is not a CAI badge.