ADR-003 Use Single-Process Approach for Architecture Requests + Issue templates

[jhagberg]

Add GitHub Issue Templates and Labels

Summary

This PR adds GitHub integration to make it easy for people to ask architecture questions:

• Issue template for architecture-question
• Configuration for additional contact links
• Proposed label structure for workflow management

Proposed Labels

I suggest we create these labels manually after merging:

Core Labels (Recommended to Create)

Label	Color	Description	When Applied
architecture-question	#0E8A16	Questions for board	Always (auto by template)
high-impact	#D93F0B	Affects all platforms	Optional (when relevant)
urgent	#B60205	Needs quick response	Rare (sparingly used)
adr-needed	#5319E7	Should become ADR	Board adds (during discussion)

Usage pattern:

• Every issue gets: architecture-question (automatically)
• Some issues get: high-impact (when affects all platforms)
• Few issues get: urgent (only when truly time-sensitive)
• Board adds: adr-needed (during discussion if precedent-setting)

Optional Status Labels

Label	Color	Description	Usage
needs-decision	#FBCA04 (yellow)	Discussion ongoing, decision pending	Board workflow
waiting-for-feedback	#FEF2C0 (light yellow)	Waiting for requester response	Board workflow
resolved	#0E8A16 (green)	Question answered	Board closes issue

Optional Category Labels

Label	Color	Description
integration	#1D76DB (blue)	Integration between systems
standards	#1D76DB (blue)	Standards and specifications
security	#D93F0B (red)	Security-related
infrastructure	#BFD4F2 (light blue)	Hardware/storage/compute

Discussion question: Should we start with just the 4 core labels and add more as needed? Or create the full set upfront?

Blank Issues: Enabled ✅

Set to true to lower barrier. Anyone can open issue without template.

Rationale: Better to be welcoming than strict. We can require templates later if needed.

Question: Agree, or should we require template usage?

Discussion Questions for Reviewers

1. Label set: Start with 4 core labels or create all 11 upfront?
2. Blank issues: Keep enabled (true) or require template (false)?
3. Template tone: Too casual? Too formal? Just right?
4. Template fields: Missing anything important? Too many fields?
5. Contact links: Should we add Slack channel if we create one?

[alneberg]

How could the core labels be useful if they are required? For example if everything is labelled urgent? I'm probably just misunderstanding something though.

[jhagberg]

Great question! Sorry poor wording on my part.

I mean
"These are the core labels we must CREATE in the repository"
NOT "These labels must be applied to every issue"
I will update the PR text!

How could the core labels be useful if they are required? For example if everything is labelled urgent? I'm probably just misunderstanding something though.