---
qep: N
title: <Title in Title Case>
author: "@your-handle"
status: Draft
type: Process | Standard | Informational
created: YYYY-MM-DD
discussion: <link to the QEP discussion issue or thread>
---

<!-- Number unpadded, e.g. 7 — the filename zero-pads it to four digits: qeps/qep-0007-short-slug.md -->

# QEP-N: <Title>

|              |                                      |
| ------------ | ------------------------------------ |
| **QEP**      | N                                    |
| **Title**    | \<Title>                             |
| **Author**   | @your-handle                         |
| **Status**   | Draft                                |
| **Type**     | Process / Standard / Informational   |
| **Created**  | YYYY-MM-DD                           |
| **Discussion** | \<issue link>                      |

## Summary

Three to four sentences: what is being decided, in plain language.

## Motivation

What problem does this solve, and why now? What goes wrong if we do nothing?

## Proposal

The actual decision being asked for. Be specific and concrete — this is the part
that becomes binding once the QEP is Accepted.

## Alternatives considered

The main options you weighed and why they were not chosen. This section is where
much of a QEP's long-term value lives.

## Rollout

How the decision gets implemented: migration steps, tooling, who does what, and any
timeline. Omit if not applicable.