MCX records map directly to the EU AI Act's disclosure obligations — risk classification, transparency, technical documentation, and conformity. One regulation, covered properly.
The bulk of Article 50 transparency duties apply 2 August 2026, as originally scheduled. A May 2026 proposal would push the high-risk deadlines back — but it is not yet law. Building the evidence early is the only safe assumption.
The 7 May 2026 Digital Omnibus reached only a provisional agreement to defer high-risk deadlines — Parliament and Council still have to formally adopt it. The August 2026 transparency obligations were never part of that deferral. Credible compliance evidence takes 12–18 months to build, so starting now is the only position that holds either way.
A single MCX record documents an AI model against the EU AI Act articles that govern it. The schema enforces the required fields per risk class, so a high-risk record can't be published with the high-risk obligations missing.
Every record declares its EU AI Act risk class, and the schema requires the right fields for that class.
Intended purpose, intended users, out-of-scope uses, explainability, input/output guidance, human-oversight measures, and expected lifetime.
Architecture and delivery form, training-data sources, scope, and known gaps, plus performance, bias, robustness, and cybersecurity results.
Records the conformity-assessment outcome and CE-marking status. MCX records the result — it is not a Notified Body and does not perform the assessment.
Automation level and the human-oversight measures a deployer needs to operate the system within the law.
Post-market monitoring approach, logging, and serious-incident records — kept current as the system changes.
For GPAI models: training compute, copyright policy, and a training-data summary, with extra fields when a model is systemic.
Publisher identity, EU AI Act role (provider / deployer), contact, and a named human attestation accountable for the record.
The full field-by-field mapping is published openly. See the schema on GitHub →
Validators confirm a record conforms to the schema. They do not confirm the disclosure is accurate — that accountability rests with the publishing provider's attestation.
Conformity assessments under Article 43 are performed by accredited bodies. MCX records the outcome where relevant; it does not produce a certificate.
Field mappings are best-effort community work, not a legal opinion. Deployers interpret records against their own compliance posture.
The founding cohort shapes the schema before public launch. Credible compliance evidence takes 12–18 months — starting now is the only position that holds.