Release Process

The Playbook is versioned so readers know which content is draft, current, deprecated, or retired.

Release Checklist

1. Confirm required pages have complete metadata.
2. Confirm mkdocs.yml navigation matches the intended release.
3. Run mkdocs build --strict.
4. Update CHANGELOG.md.
5. Update version references where required.
6. Tag the release after approval.

Changelog Rules

Use these categories:

• Added
• Changed
• Deprecated
• Removed
• Fixed
• Security

Versioning

Use MAJOR.MINOR.PATCH where practical.

• MAJOR: major Playbook restructuring or incompatible governance changes.
• MINOR: new approved sections, standards, or substantial content.
• PATCH: corrections, clarifications, and maintenance updates.