8.6 Regeneration Rules [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== 8.6 Regeneration Rules ======

[[fxdemo:05-part:start | Go To Top ]]

[[fxdemo:05-part:08-generated-artifacts:start | Return to Generated Artifacts ]]

The team should define when and how developers regenerate [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]]. Regeneration should follow documented scripts or commands so that different developers produce consistent outputs.

Developers should regenerate Artifacts when:

  - An [[dido:99_annexes:annex-b-terms-and-definitions:i:idl|IDL]] source file changes.
  - A catalog source changes and generated documentation depends on it.
  - A [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]] template changes and generated Configuration depends on it.
  - A generator script changes.
  - A generator version changes.
  - The team refreshes the Phase 0 [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]].

The generation process should run from a documented [[dido:99_annexes:annex-b-terms-and-definitions:r:repository|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.

----

<WRAP centeralign>

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

</WRAP>