====== P4-REQ-21-11-002 ======

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

===== Statement =====

The Developer Handbook SHALL define file-header conventions.

===== Source =====

Part 4, Section 21.11: Developer Handbook Requirements.

===== Rationale =====

File-header conventions provide a consistent mechanism for identifying an artifact's purpose, ownership context, logical or implementation source, modification guidance, review status, and traceability.

A standard header makes governed source files easier to review and prevents implementation artifacts from entering the baseline without sufficient context.

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

This requirement applies to:

  * hand-authored source files;
  * applicable scripts;
  * governed configuration source files where required; and
  * other files governed by the handbook.

===== Verification =====

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

Verification activities should include review checks confirming that:

  * required header fields are identified;
  * artifact purpose is addressed;
  * logical or implementation source is addressed;
  * modification guidance is addressed; and
  * traceability information is addressed.

===== Traceability =====

This requirement establishes the handbook rule used to govern Phase 0 source-file headers.

Related requirement identifiers:

  * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-11-001]]
  * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-11-003]]
  * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-10-006]]

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>