Regulatory Access and Source-Code Response

Provide controlled regulator access to AI documentation, development data sets, source code and model access when legally required.

When a competent authority lawfully requests technical information or access, assign legal and technical leads to determine the scope and conditions. For high-risk AI, assess the relevant documentation, data and any additional conditions for source-code access. For GPAI evaluation, follow the formal decision's technical means, access requirements and time limit. Prepare controlled access, verify it works and retain an appropriate record. Respect any lawful instruction restricting evaluation logging and do not impose constraints that materially obstruct the required evaluation. A request for documentation is not automatically a request for all source code or unrestricted production access.

On a lawful request or decision; within its applicable deadline; periodic technical-response readiness tests.

Request or decision and legal-scope assessment Technical access plan and tested configuration Required documents, data or model-access package Confidentiality and permitted logging arrangements Delivery, access and follow-up records

Test a representative authorized access route against the request. Check that required material is available within scope and deadline, while unrelated access is controlled. Verify any specific evaluation-logging condition before enabling audit logs.