15.4 File-Header Requirements

Go To Phase 0 Developer Handbook Requirements

The Developer Handbook must define a standard header for hand-authored implementation files.

The file header must identify:

1. Artifact name
2. Artifact purpose
3. Owning document or profile
4. Related FX logical element or implementation concern
5. Artifact category
6. Generation status
7. Authoring or ownership context
8. Modification guidance
9. Traceability reference
10. Copyright or license statement
11. Review or approval status where required

A source file without the required header must not enter the Phase 0 implementation baseline.

The file header supports traceability. It allows reviewers to understand why a file exists, which logical or implementation concern it supports, and how contributors may modify it.