Child Safety: add privacy-preserving compliance infrastructure

[moelayyan90]

What this changes

Repositions the institutional child-safety surface as privacy-preserving compliance infrastructure and adds a regulator-facing age-assurance evidence layer.

Added

• GET /v1/child-safety/compliance-profile
• GET /v1/child-safety/age-assurance/schema
• POST /v1/child-safety/age-assurance/evaluate
• GET /v1/child-safety/regulator-pack
• /child-safety/age-assurance
• /child-safety/regulatory-readiness
• EU / UK / ISO regulatory-readiness roadmap
• regulator / government evidence packet
• automated tests for the new evidence boundary

Privacy / claims boundary

• rejects raw DOB, passport number, document images, full name and address on the age-evidence endpoint
• does not return or retain the supplied proof reference
• distinguishes caller-attested evidence from facts independently verified by XGuard
• explicitly does not claim government approval, EU trusted-list status, Ofcom approval or ISO certification

Institutional positioning

The existing base per-event safety API prices remain base API prices only. Regulated enterprise deployments, government pilots, age-assurance-provider costs, independent testing, legal review, certification work, human review and dedicated support are separate scopes.

External work still required before any approval claim

Independent security assessment, empirical age-assurance testing, fairness/accessibility evidence, DPIA / child-rights impact assessment, provider trust verification, jurisdiction-specific legal review, applicable conformity assessment/certification and formal scheme/regulator submission.

Draft PR intentionally: CI and review should validate the implementation before merge.

[moelayyan90]

Execution checkpoint — 2026-08-20

• Regulatory/age-assurance implementation and public institutional surfaces are in this draft PR.
• Privacy boundary explicitly rejects raw DOB / identity-document fields and does not convert caller-declared trust into an approval claim.
• The repository CI workflow is configured to run verify:release on pull requests, but no commit status/check has surfaced for the current head yet. Do not merge solely on source inspection.
• xguardgate.com institutional email domain verification has been triggered in Resend but remains pending; do not send regulator/government outreach from the domain until verification completes.
• External gates remain: independent security testing, empirical age-assurance accuracy/robustness/reliability/fairness evidence, DPIA/child-rights assessment, applicable conformity/certification work, and a formal regulator/scheme submission route.

Related execution tracker: #348.