<!--
  Process documents describe how the project operates: workflows, policies,
  values, contribution guidelines. They follow the same lifecycle as other RFDs
  but tend to be shorter and less formal.

  Structure this however it reads best. The only requirement is the metadata
  header (Status, Category, Authors, Date).

  Use HTML comments like this one for draft-time notes and review markers.
  They do not appear in the rendered output and can be removed when the RFD
  advances to Discussion status.
-->

# RFD NNN: TITLE

- **Status**: Draft
- **Category**: Process
- **Authors**: AUTHOR
- **Date**: DATE

## Summary

One to three sentences describing what this document establishes. A reader
should know whether this document is relevant to them without reading further.

<!-- Write the document below. Use whatever structure fits the topic. -->
