P4-REQ-21-10-007
Statement
Each generated file SHALL include the generated-file header defined by the Developer Handbook.
Source
Part 4, Section 21.10: Repository and Build Artifact Requirements.
Rationale
Generated files require explicit metadata describing their source definition, generator, generation context, regeneration rule, and manual-editing status.
The generated-file header helps reviewers distinguish generated outputs from hand-authored source and supports repeatability and controlled regeneration.
Applies To
This requirement applies to:
-
generated types;
-
generated DDS support code;
-
generated bindings; and
-
other governed generated outputs included in the Phase 0 baseline.
Verification
Verification SHALL confirm that each governed generated file includes the required generated-file header.
Verification activities should include review checks confirming that:
-
the source definition is identified;
-
the generator or generation process is identified;
-
regeneration guidance is present;
-
the manual-editing rule is stated; and
-
the header conforms to the Developer Handbook.
Traceability
This requirement connects Phase 0 generated files to their governed source definitions and generation process.
Related requirement identifiers:
Related source section:
Status
Draft
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.