Request for Comments (RFCs)

This section contains RFCs for proposed changes and design decisions that require discussion.

What are RFCs?

RFCs are design documents that propose changes requiring user input or team discussion. They outline:

Problem - What needs to be solved
Proposed Solution - How to solve it
Alternatives - Other approaches considered
Open Questions - What needs to be decided
Trade-offs - Pros and cons of each approach

RFC Process

Create RFC - Document the problem and proposed solutions
Discuss - User/team reviews and provides feedback
Decide - Choose an approach
Document in ADR - Record the decision
Implement - Build the chosen solution

RFC Format

# RFC-XXXX: [Title]

**Status:** [Proposed | Under Discussion | Decided | Implemented]
**Date:** YYYY-MM-DD
**Author:** [Who created it]
**Related:** [BACKLOG-XXXX, etc.]

## Problem Statement

[Describe what needs to be solved]

## Proposed Solutions

### Option 1: [Name]
**Description:**
[How it works]

**Pros:**
- [Benefit 1]
- [Benefit 2]

**Cons:**
- [Trade-off 1]
- [Trade-off 2]

### Option 2: [Name]
[Same structure]

## Recommendation

[If applicable, which option is recommended and why]

## Open Questions

- [Question 1]
- [Question 2]

## References

- [Links to related docs]

All RFCs

Active RFCs

RFC-0001: Foundation Model Training Strategy - Proposed
How to implement the foundation model for Phase 1 MVP
Options: Full custom model vs. simple start vs. hybrid approach
Decision needed: Speed vs. sophistication trade-off

Decided RFCs

No RFCs have been decided yet.

Implemented RFCs

No RFCs have been implemented yet.

When to Create an RFC

Create an RFC when: - Multiple implementation approaches exist - Significant architectural decisions need input - Technology choices have major trade-offs - Design patterns need to be established - User preferences are needed for direction

The orchestrator can help create RFCs when encountering decision points during implementation.