Documenting the design and build decisions: Which practice, performed during the build, best positions the

Documenting design/build decisions and their rationale is what later evidences compliance and risk management.

The question

Preparing for AIGP? Take the free 5-min readiness quiz →

1. Retaining the final production container image so the deployed system can be redeployed on demand later.

   Plausible but keeping an artifact does not explain the reasoning behind design choices and risk trade-offs.
2. Archiving the internal chat logs from the project so past conversations can be searched when questions arise.

   Almost right as a record, but unstructured chat is not deliberate documentation of decisions and rationale.
3. Documenting the design and build decisions and their rationale to establish compliance and manage risks. ✓

   Documenting design/build decisions and rationale is exactly what evidences compliance and risk management later.
4. Keeping the raw training dataset unchanged so the model could in principle be retrained on it in the future.

   Plausible but preserving data supports reproducibility, not an account of why design decisions were made.

How to remember it

Documenting design/build decisions and their rationale is what later evidences compliance and risk management.

More Understanding How to Govern AI Development questions

• A probability and severity harms matrix that ranks each: Which technique most directly serves that →
• The data fails on lawful basis: Under data governance requirements, which conclusion is best supported before →
• Documented data lineage and provenance linking each record: What does this gap most directly indicate is →
• All 426 Understanding How to Govern AI Development questions →