Skip to content

Latest commit

 

History

History
160 lines (110 loc) · 5.86 KB

File metadata and controls

160 lines (110 loc) · 5.86 KB

Classification

Type — select all that apply:

  • feat — New content, template, or framework section
  • fix — Factual, legal, regulatory, or structural correction
  • docs — Documentation improvement (style, clarity, structure)
  • policy — Policy template addition or revision
  • i18n — Translation or localisation
  • chore — Tooling, CI, metadata, repository hygiene
  • governance:proposal — Significant change · triggers 14-day review period
  • governance:constitutional — Constitutional change · triggers 30-day consultation period

Severity (for fix type only):

  • Critical — Incorrect guidance that could cause legal or regulatory exposure
  • High — Material inaccuracy in compliance or normative content
  • Moderate — Inaccuracy with limited immediate impact
  • Low — Minor correction, broken link, formatting

Summary


Motivation and Context


Related Issues


Regulatory and Standards References

Instrument Article / Section Relevance to this PR

Changes Made

File Nature of Change

Contributor Checklist

Complete all items applicable to your contribution type before requesting review. Leave N/A items unchecked with a note if genuinely not applicable.

Content and Accuracy

  • All factual, legal, and technical claims are accurate and verified against authoritative sources
  • Regulatory references cite specific articles/sections, not document titles alone
  • RFC 2119 keywords (MUST, SHOULD, MAY, SHALL) are used correctly and consistently
  • No proprietary vendor dependencies introduced without open-source alternatives

Language and Style

  • Language is institutional English — clear, precise, and accessible to technical and non-technical audiences
  • Technical or legal terminology is explained on first use where necessary
  • No informal, colloquial, or marketing language

Structure and Formatting

  • Headings use ATX style (#, ##, ###)
  • Tables include header rows and |---| separators
  • Code blocks use fenced syntax with language identifiers
  • All internal and external links are valid and accessible
  • New documents are referenced from README.md or the appropriate parent document

Template-Specific (if applicable)

  • Placeholders follow the [ORGANISATION NAME] / [DATE] convention
  • Template includes an applicability statement (target organisation types)
  • Template includes a version history table at the end

Licence and Intellectual Property

  • All contributed content is original or derived from sources with a licence compatible with EUPL-1.2
  • Third-party content is identified, attributed, and carries a REUSE-compliant copyright header
  • Commits are signed off: git commit -s (Developer Certificate of Origin)

Changelog

  • CHANGELOG.md updated under [Unreleased] with a concise description of this change

Process

  • Searched existing issues and PRs — this is not a duplicate
  • For governance:proposal changes: issue opened and 14-day comment period observed
  • For governance:constitutional changes: issue opened and 30-day consultation period observed
  • Relevant affiliations or conflicts of interest declared below (if any)

Conflict of Interest Declaration


Validation and Testing


Notes for Reviewers