8.2 Generated Versus Handwritten Files [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.2 Generated Versus Handwritten Files ======

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

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

The [[dido:99_annexes:annex-b-terms-and-definitions:r:repository|Repository]] should clearly separate generated files from handwritten files. This separation protects developers from editing files that generation processes may overwrite and helps reviewers understand the origin of each [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]].

Handwritten files include source definitions, [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] implementation code, scripts, [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]] templates, tests, documentation, and other Artifacts that developers intentionally author and review.

Generated files include [[dido:99_annexes:annex-b-terms-and-definitions:i:idl|IDL]]-derived language bindings, [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] type support files, documentation, Configuration fragments, topic support files, and other outputs produced by an approved generation process.

The team should place generated files under approved generated directories, such as:

  * ''generated/''
  * ''generated/dds/''
  * ''generated/docs/''
  * ''generated/config/''

The team should not place generated files in ''src/'' unless the selected toolchain requires it and the handbook documents the reason. If a toolchain forces generated files into a source tree, the team should isolate them in a clearly named subdirectory and document the regeneration process.

----

<WRAP centeralign>

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

</WRAP>