# Hard Problem Template

## Problem Summary
<!-- Brief 1-2 sentence description of the problem -->

## Context
<!--
Background information needed to understand this problem:
- What component(s) are affected?
- Why is this a "hard problem" vs a regular bug/feature?
- What customer scenarios are impacted?
-->

## Problem Details
<!--
Detailed explanation of the problem. Consider including subsections like:

### Proposed Solution/Classification Logic
- Decision trees or step-by-step logic
- Feature flags and their defaults
- Integration points with existing features

### User Experience
- How will this appear to users?
- What controls/settings will be available?
- Status visibility and feedback mechanisms
-->

## Solutions Considered and Rejected
<!--
List approaches that have already been explored and why they won't work:
- Solution 1: [Brief description] - Rejected because [reason]
- Solution 2: [Brief description] - Rejected because [reason]
-->

## Open Questions
<!--
What questions need to be answered to solve this?
Consider organizing by category:

### Technical Implementation
1. Question about implementation details
2. Question about ownership/authority

### User Conventions and Configuration
3. Question about user-facing decisions
4. Question about configuration options
-->

## Meeting Notes
<!--
To be filled in after the meeting:
- Discussion summary:
- Decision:
- Rationale:
- Action items:
-->

## Follow-up
<!--
Links to:
- PRs implementing the solution
- Related issues
- Design docs created as a result
-->