TEMPLATE.md: Distinguish between alignment on syntax and alignment on goal

joshtriplett · joshtriplett · commit 41abd87ff309 · 2024-12-19T20:04:51.000-08:00
diff --git a/src/TEMPLATE.md b/src/TEMPLATE.md
@@ -39,6 +39,8 @@
 >
 > *This text is NORMATIVE, in the sense that teams should review this and make sure they are aligned. If not, then the shiny future should be moved to frequently asked questions with a title like "what might we do next".*
 
+*However, for most proposals, alignment on exact syntax should not be required to start a goal, only alignment on the problem and the general sketch of the solution. This may vary for goals that are specifically about syntax, such as ergonomic improvements.*
+
 ## Design axioms
 
 > *This section is optional, but including [design axioms][da] can help you signal how you intend to balance constraints and tradeoffs (e.g., "prefer ease of use over performance" or vice versa). Teams should review the axioms and make sure they agree. [Read more about design axioms][da].*

Original file line number	Diff line number	Diff line change
`@@ -39,6 +39,8 @@`
`39`	`39`	`>`
`40`	`40`	`> This text is NORMATIVE, in the sense that teams should review this and make sure they are aligned. If not, then the shiny future should be moved to frequently asked questions with a title like "what might we do next".`
`41`	`41`
	`42`	`+However, for most proposals, alignment on exact syntax should not be required to start a goal, only alignment on the problem and the general sketch of the solution. This may vary for goals that are specifically about syntax, such as ergonomic improvements.`
	`43`	`+`
`42`	`44`	`## Design axioms`
`43`	`45`
`44`	`46`	`> This section is optional, but including [design axioms][da] can help you signal how you intend to balance constraints and tradeoffs (e.g., "prefer ease of use over performance" or vice versa). Teams should review the axioms and make sure they agree. [Read more about design axioms][da].`