// REGULATORY ALIGNMENT — NOT ARCHITECTURE
This page documents our statutory coverage claims only.
Our governance architecture is proprietary.
Challenge our regulatory claims — not our implementation.
Our governance architecture is proprietary.
Challenge our regulatory claims — not our implementation.
Statutory Coverage
Regulatory Framework Claims
The table below states which regulatory articles and obligations we claim CLEARANCE addresses. These are coverage claims. If you believe a claim is incorrect, challenge it at the address below.
| Framework | Article / Section | Obligation | Covered |
|---|---|---|---|
| UK GDPR | Art. 5(1)(f) | Integrity and confidentiality of personal data including in AI processing | ✓ |
| UK GDPR | Art. 25 | Data protection by design and by default in AI systems | ✓ |
| UK GDPR | Art. 32 | Security of processing — technical and organisational measures for AI | ✓ |
| UK GDPR | Art. 44-46 | International transfer restrictions and adequacy requirements | ✓ |
| EU AI Act | Art. 9 | Risk management system for high-risk AI — documented, continuous | ✓ |
| EU AI Act | Art. 10 | Data and data governance for AI training and validation datasets | ✓ |
| EU AI Act | Art. 13 | Transparency and provision of information to users | ✓ |
| EU AI Act | Art. 14 | Human oversight measures — capability and activation | ✓ |
| EU AI Act | Art. 17 | Quality management system documentation | ~ |
| FCA FG21/1 | §4 | Governance and accountability frameworks for AI and algorithmic models | ✓ |
| FCA FG21/1 | §5 | Explainability requirements for AI-driven decisions | ✓ |
| Consumer Duty | Principle 12 | Good outcomes for retail customers — AI decision oversight | ✓ |
| SMCR | Senior Manager Regime | Individual accountability for AI governance failures | ✓ |
| JSP 936 | Sections 4.2-4.5 | Responsible AI requirements for defence supply chain | ✓ |
| JSP 936 | Section 6 RAISO | Responsible AI Subject Officer designation and accountability | ✓ |
Challenge our regulatory alignment claims.
If we have stated a regulation is addressed and you believe it is not — tell us.
methodology@clearanceai.co.uk
Registration Architecture
Living Certificates
Each cleared organisation and each cleared capability holds a permanent registration number. Certificates are versioned. When regulations change, when organisations change, or when capabilities change, a new version of the certificate is issued under the same registration number. Version history is public and signed. QR codes encode the registration number, not the certificate version — they remain valid through every re-issuance.
Certification Transparency
Operator vs Third-Party Certification
Certificates issued by MissionOpsAI Ltd against its own organisation and its own capabilities are marked operator self-issued and displayed as such in the directory. Independent third-party assessments are marked third-party issued. The distinction is published, not concealed. We operate the CLEARANCE scheme and certify ourselves under it; we declare this openly and invite challenge.
Independent Oversight
Certification Partner Slot
The certification partner slot on every issued WARRANT is reserved for an external accreditation body. Until that accreditation is in place, MissionOpsAI Ltd operates the scheme transparently and invites challenge at methodology@clearanceai.co.uk.