====== 4.4 Generated Artefact Directories ======

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

[[fxdemo:05-part:04-repository-layout:start | Return to Repository Layout ]]

The ''generated/'' directory should contain [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]] produced by repeatable generation processes. These may include [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] language bindings, [[dido:99_annexes:annex-b-terms-and-definitions:i:idl|IDL]]-derived [[dido:99_annexes:annex-b-terms-and-definitions:t:type|Types]], generated documentation, generated [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]] fragments, or other outputs created from [[dido:99_annexes:annex-b-terms-and-definitions:g:governed|Governed]] source definitions.

A representative structure is:

<code>
generated/
    dds/
    docs/
    config/
</code>

The team should treat generated Artifacts as derived outputs. Each generated Artifact should trace back to a source definition, generation command, or generation script. The [[dido:99_annexes:annex-b-terms-and-definitions:r:repository|Repository]] should make it clear whether generated Artifacts are committed to [[dido:99_annexes:annex-b-terms-and-definitions:g:git|Git]] or remain local build outputs.

Generation processes should not overwrite handwritten source files. They should write outputs only to approved generated Artifact locations. If a generated Artifact requires manual modification, the team should revisit the generation process rather than turning the generated file into an undocumented handwritten Artifact.

----

<WRAP centeralign>

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

</WRAP>