====== P4-REQ-21-11-003 ======

[[dido:99_annexes:annex-d-requirements:part-04:start| Return to Requirements]]

===== Statement =====

The Developer Handbook SHALL define generated-file header conventions.

===== Source =====

Part 4, Section 21.11: Developer Handbook Requirements.

===== Rationale =====

Generated files require metadata that identifies their source definition, generator, generation context, regeneration rule, and manual-editing status.

Defining generated-file header conventions supports reproducibility and allows reviewers to distinguish generated artifacts from hand-authored implementation logic.

===== Applies To =====

This requirement applies to:

  * generated types;
  * generated DDS support code;
  * generated bindings; and
  * other generated artifacts included in the Phase 0 baseline.

===== Verification =====

Verification SHALL confirm that the Developer Handbook defines generated-file header conventions.

Verification activities should include review checks confirming that:

  * source-definition identification is required;
  * generator identification is required;
  * generation context is addressed;
  * regeneration rules are addressed; and
  * manual-editing rules are addressed.

===== Traceability =====

This requirement establishes the handbook rule governing generated-file identification and regeneration metadata.

Related requirement identifiers:

  * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-11-002]]
  * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-10-007]]

Related source section:

  * [[fxdemo:04-part:21-phase-0-implementation-requirements:21-11-developer-handbook-requirements:start]]

===== Status =====

Draft

----

<WRAP centeralign>

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

</WRAP>