From 06708dcb3bacd13926f90b535a9b07061c6c121c Mon Sep 17 00:00:00 2001
From: Mark Larah <mark@larah.me>
Date: Sun, 14 Sep 2025 23:06:43 -0500
Subject: [PATCH 1/2] add a template rfc

---
 rfcs/README.md   |  1 +
 rfcs/TEMPLATE.md | 45 +++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 46 insertions(+)
 create mode 100644 rfcs/TEMPLATE.md

diff --git a/rfcs/README.md b/rfcs/README.md
index aed1c425..55593188 100644
--- a/rfcs/README.md
+++ b/rfcs/README.md
@@ -16,3 +16,4 @@ That said, please follow these suggestions:
 
 * New proposals should be presented in a [working group meeting](../agendas). Submitting a document here is not sufficient or required to introduce a new proposal.
 * Favor documents which define a problem and explore a solution space rather than propose a specific change. The intent of documents found here are to help ask and answer questions to build confidence and advance an RFC.
+* A template is provided [here](./TEMPLATE.md) as a starting point for new RFCs.
\ No newline at end of file
diff --git a/rfcs/TEMPLATE.md b/rfcs/TEMPLATE.md
new file mode 100644
index 00000000..198f09b0
--- /dev/null
+++ b/rfcs/TEMPLATE.md
@@ -0,0 +1,45 @@
+<!-- This template is provided as a suggested starting point. You may alter the
+format where necessary. -->
+
+# RFC: <Title>
+
+**Proposed by:** [<Full Name>](https://github.com/<username>) - <Organization>
+
+<!-- Briefly summarize and explainin the concepts introduced by the RFC. Usually
+one or two short sentences or paragraphs. -->
+
+## 📜 Problem Statement
+
+<!-- Briefly explain the problem being solved. Assume no prior knowledge (other
+than the current GraphQL specification) and start from first principles. Usually
+one or two short paragraphs. -->
+
+**Example**
+
+<!-- Provide a minimal code example here if possible. -->
+
+## 💡 Proposed Solution
+
+<!-- Explain the proposal! Be detailed enough to explain the idea and major edge
+cases - but avoid being overly detailed. The primary goal is to communicate the
+idea at a high level. The specification edit PR will cover all the precice
+implementation details. -->
+
+## ⚠️ Risks
+
+<!-- Think: Why *shouldn't* we do this proposal? List any unaddressed risks or
+edge cases we need to consider. -->
+
+## Appendix
+
+<!-- Additional appendix sections are encourged as the editor sees fit. You are
+encouraged to keep the main body of the RFC focused on the chosen solution. -->
+
+### 🎨 Prior Art
+
+<!-- If applicable, list any existing userland solutions that relate to this
+RFC. -->
+
+### 🤔 Alternatives Considered
+
+<!-- If applicable, list any alternate naming or implementations considered. --> 
\ No newline at end of file

From 5edb9919fec266e7f3e495b42dc41572270d5384 Mon Sep 17 00:00:00 2001
From: Mark Larah <mark@larah.me>
Date: Sun, 14 Sep 2025 23:12:51 -0500
Subject: [PATCH 2/2] Update TEMPLATE.md

---
 rfcs/TEMPLATE.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/rfcs/TEMPLATE.md b/rfcs/TEMPLATE.md
index 198f09b0..71ed201c 100644
--- a/rfcs/TEMPLATE.md
+++ b/rfcs/TEMPLATE.md
@@ -22,7 +22,7 @@ one or two short paragraphs. -->
 
 <!-- Explain the proposal! Be detailed enough to explain the idea and major edge
 cases - but avoid being overly detailed. The primary goal is to communicate the
-idea at a high level. The specification edit PR will cover all the precice
+idea at a high level. The specification edit PR will cover all the precise
 implementation details. -->
 
 ## ⚠️ Risks
@@ -42,4 +42,4 @@ RFC. -->
 
 ### 🤔 Alternatives Considered
 
-<!-- If applicable, list any alternate naming or implementations considered. --> 
\ No newline at end of file
+<!-- If applicable, list any alternate naming or implementations considered. -->