Put your sealed history on your own trust page

Five facts, nothing more: the badge shows your sealed-day count, coverage percentage, longest unbroken run, the continuity milestone you have earned, and a certificate hash prefix a reader can check.

JSON or SVG, your choice: take the SVG to drop a rendered badge straight into a trust page, or take the JSON to style the same numbers inside your own design system.

It points back at proof: the certificate hash prefix leads a reader to the public verification page, where pasting the full SHA-256 hash returns a readable receipt confirming RAIC issued that record.

You control the address: the badge resolves through an opaque Trust Portal slug you own, so you decide who gets the link and you can change it.

No login stands in the way: the endpoint is unauthenticated and cacheable, which means a prospect, an insurer, or an auditor loads it the same way they load any page on your site.

Read the published contract: the exact fields, formats, and caching behavior live in the continuity badge contract, so your web team implements against a document rather than a screenshot.

No gap dates: a reader sees your longest unbroken run and your coverage percentage, never the specific days behind them.

No ledger volumes: the badge withholds how much activity your organization records, so nobody infers headcount, workload, or scope from it.

No contents and no identifiers: record contents and tenant identifiers stay out of the response entirely.

Claims lose to receipts: anyone can type "we maintain continuous governance records" into a security questionnaire, and every reviewer knows it.

A badge shortens the review: a prospect checks the number themselves in seconds instead of scheduling a call to ask you about it.

Continuity accrues, so it cannot be bought: nobody backfills sealed days, which is exactly why a long unbroken run carries weight with the reader.

Honest limit: the badge proves the records exist and are unchanged since sealing. It does not prove any individual governance decision was correct. Background on the mechanism lives on Verifiable Evidence Lineage and Independent Verification.