8.6 Regeneration Rules

Go To Top

Return to Generated Artifacts

The team should define when and how developers regenerate Artifacts. Regeneration should follow documented scripts or commands so that different developers produce consistent outputs.

Developers should regenerate Artifacts when:

1. An IDL source file changes.
2. A catalog source changes and generated documentation depends on it.
3. A Configuration template changes and generated Configuration depends on it.
4. A generator script changes.
5. A generator version changes.
6. The team refreshes the Phase 0 Baseline.

The generation process should run from a documented Repository location and write outputs only to approved generated directories. It should fail clearly if required inputs are missing, if output directories are unavailable, if the generator version is unsupported, or if generation would overwrite a protected handwritten file.

When Git tracks generated Artifacts, developers should commit regenerated outputs together with the source changes that caused them. When Git does not track generated Artifacts, developers should document how reviewers can reproduce them.