§7.2 · BUILDING · 4 MIN READ · EDITION 1.0
Configuration as a controlled artefact
Model version, instructions, retrieval settings and rules should be versioned and change-controlled exactly like a work instruction.
An unannounced model or instruction update can silently change behaviour on a use case that was already validated; treat vendor updates as change events that trigger a review.
The qualification record should freeze the exact configuration that was evaluated, so a later drift can be detected by comparison.
PUT THIS INTO PRACTICE
- 01Version every configuration element.
- 02Treat vendor-side updates as change events.
- 03Compare live configuration against the qualified baseline periodically.
RELATED INSTRUMENTS
CITE THIS SECTION
§7.2 · Edition 1.0 · Configuration as a controlled artefact