8.7 Protecting Handwritten Code from Overwrite [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.7 Protecting Handwritten Code from Overwrite ======

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

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

Generation processes must protect handwritten code. A generator should not overwrite handwritten source files, scripts, [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]], tests, or documentation unless the team explicitly designs and documents that workflow.

The [[dido:99_annexes:annex-b-terms-and-definitions:r:repository|Repository]] should use directory separation, file headers, naming conventions, and script safeguards to prevent accidental overwrite. Generation scripts should write only to approved generated directories by default. If a script receives a custom output path, it should validate the path before writing files.

Generated files should include clear warnings where practical, such as:

  * This file was generated. Do not edit directly.
  * Regenerate it from the approved source definitions and the generation script.

If developers need to extend generated behavior, the team should prefer extension points, wrapper classes, partial classes, separate handwritten modules, or Configuration-based customization. The team should avoid editing generated files, as regeneration can overwrite those changes.

Protecting handwritten code keeps the Phase 0 [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]] reviewable and reproducible. It also preserves the distinction between governed source definitions, generated implementation projections, and developer-authored runtime logic.

----

<WRAP centeralign>

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

</WRAP>