A2. Model Registry Entries Central catalogue of all model versions. Each entry contains provenance metadata linking the model artefact to the exact code, data, configuration, and pipeline execution that produced it. Entries carry cryptographic signatures and follow a stage management lifecycle: experimental, staging, production, archived. Auto-registered at each training run with origin, training data version, code commit, hyperparameters, pipeline execution ID, evaluation metrics, content hash, and digital signature. Responsible party: CI/CD pipeline auto-registers. Technical SME maintains the registry and configures promotion gates. Regulations addressed: Article 12 (record-keeping and traceability); Article 18 (ten-year retention); Annex IV(2)(b)–(e) (model description, training methodology, evaluation). Key outputs

• Per-version provenance record with cryptographic integrity
• Stage transition audit trail