CSOAI   Home · Certification · Standards

The certifier is not the vendor — why AI safety certification has an independence problem

CSOAI · June 2026

Every AI compliance tool on the market today shares one structural flaw: the company assessing your AI system is the same company selling you the fix. That isn't certification — it's a sales funnel wearing a clipboard.

Real certification regimes (ISO, UL, accounting audit) survived a century because of one rule: the certifier is not the vendor. When the EU AI Act's Article 50 obligations land for new generative systems on 2 August 2026, buyers will need attestations a regulator or customer can trust — which means attestations issued by a party with nothing to sell them.

That is the entire design of CSOAI Watchdog Certification:

1. CSOAI certifies. The Council for the Safety of AI (CSOAI LTD, UK 16939677) sets the expectations and signs the certificate. 2. MEOK AI Labs builds. The engineering lab ships the open-source MCP fabric that runs the checks — 290+ servers in the official MCP Registry. 3. Anyone verifies. Every certificate is Ed25519-signed with a public verify URL. Your auditor checks the signature against our published key — without contacting us, ever.

A certificate that requires phoning the issuer to validate is a brochure. A certificate anyone can verify offline is infrastructure.

Honest scope: a Watchdog Certificate proves identity and integrity — that CSOAI issued this exact result and it hasn't been tampered with. It does not assert legal accuracy. Independence plus cryptography plus honesty about scope: that's what certification should have been all along.

→ csoai.org/certification · verify any cert at csoai.org/verify