The certificate
A signed, dated, revocable document that states what NeuralRing verified about your AI supply, at what assurance, against the policy you stated, over the coverage shown.
What it contains
The lines of your manifest with their rings, the policy label, the coverage number, the framework gap counts, the anchors that bracket the records, and the signature over all of it.
How it is verified
Anyone with the document can re-check the signature against NeuralRing's published key with a small script — offline, without an account, without NeuralRing being reachable.
When it changes
It expires with the claim-watch interval, is re-issued when you change a line, and is revoked when a fact it rests on worsens — the revocation is public too.
Example Ltd
- Coverage
- 86.2 % · attested 6,388 of metered 7,410 · 1 declared · unobserved
- policy
- jurisdiction EU/EEA · min_tier 1 · min_assurance verified · exclude parent US · max_retention 30 d · custody customer/eu_operator · transfer none_needed_eu · no training use
- Lines
- 7 · 4 pass · 1 fail · 1 n/e
- SEAL
- —
- Gaps
- DORA 2 · GDPR-transfers 1 · AI Act 0 · ISO 42001 2
- Verify it without NeuralRing
- neuralring.eu/certificate/crt_SAMPLE00000000000000000000
A certificate is revoked automatically when the claim-watch cascade moves any layer of a line it covers; the next issue carries the diff.
The AI Supply-Chain Certificate
A certificate is a signed, dated, revocable statement of what NeuralRing verified about an organisation's AI supply — provider, infrastructure and model, ring by ring — at what assurance, against the policy the organisation stated, over the coverage shown. It is computed from records, profiles and the routing filter that already exist; it never contains a verdict word, and it names its validity window.
Sample — first page (illustrative values)
Every value on a real certificate is copied or counted from the bundled files — never estimated. The sample is fixed text for illustration.
What it proves — and does not
- Proves: which providers and models the organisation declared or was observed using; each line's check result under the organisation's own policy, with the routing filter's reason codes; the three rings per line at their own assurance; the coverage (attested of metered, with declared-but-unobservable items lowering it); how many gap rows each framework mapping has; and WHEN — the external anchors bracketing its records.
- Does not prove: that any obligation is met. The non-determination note is on every certificate: records + substrate only — the auditor keeps the judgement. NeuralRing is not a conformity-assessment body; nobody accredited it.
- Status is derived, never stored: valid inside the window, expired after it (a re-evaluation is a new certificate, never an extension), revoked automatically when the claim-watch cascade moves any layer of a covered line — the revoked certificate stays retrievable with its reason, and the reissue carries the diff.
Verify it without NeuralRing
unzip neuralring-certificate-<id>.zip && cd neuralring-certificate-<id> node verify-certificate.mjs certificate.json node verify-pack.mjs pack/manifest.json curl -s https://neuralring.eu/.well-known/neuralring-attestation-key.pub
The bundle carries the supply manifest, the records (inside a real proof pack), the assurance profiles, the gap statements, the coverage, the anchors block and the public key. A certificate whose statements do not follow from its own bundle fails.
Public verification page: /certificate/<id> (in-browser signature check + revocation state). Related: Request the certificate · ATTESTATION.md · External anchors.
It does not say that your organisation meets an obligation. It says what was verified, and how strongly.