Built 1:1 to the UK Defence AI Centre / Alan Turing Institute System Card template (Overview · Concept of use · System detail · Security · Safety · Iterative requirements). JSP 936 mandates AI assurance — but there is no formal way to independently validate a supplier's claim, and no central store for cards. This closes both: an Ed25519-signed, offline-verifiable, shareable card. Don't trust a dashboard — verify it below.
Paste any JSON (your real system-card fields) and sign it with the sovereign key. It stays here — the payload is signed and returned; nothing is stored.
A signature proves two things at once: who issued the card (the sovereign key) and that not one character has been changed since. You never have to trust us — you check it yourself, even offline, even years later.
message, signature and publicKey to /api/verify (or any Ed25519 verifier). It answers valid / invalid — no account.openssl) verifies it with the public key alone. Example:// Node — verify with nothing but the public key
import crypto from 'crypto';
const pub = crypto.createPublicKey({ key: Buffer.from(publicKey,'hex'), format:'der', type:'spki' });
const ok = crypto.verify(null, Buffer.from(message), pub, Buffer.from(signature,'hex'));
console.log(ok ? 'AUTHENTIC & UNTAMPERED' : 'REJECT');
That's the whole point: assurance you can re-check without us, forever. Post-quantum (ML-DSA-65) is added by the SOV33 substrate for long-term archival.
Card data here is SYNTHETIC / demonstration. Signing & verification are real (Ed25519). POST {card} to /api/systemcard to sign your own fields. Signed card registry · Verify page · MEOK OS