# RFCs (Request for Comments)

This directory contains formal specification documents for significant Episteme/Aphoria features.

## RFC Index

| RFC | Title | Status | Date |
|-----|-------|--------|------|
| [RFC-001](./rfc-001-enterprise-policy-aliases.md) | Enterprise Policy Alias System | Proposed | 2026-02-05 |

## RFC Process

### Status Lifecycle

- **Proposed:** Initial draft, open for feedback
- **Accepted:** Approved for implementation
- **Implemented:** Feature shipped in a release
- **Superseded:** Replaced by a newer RFC
- **Withdrawn:** No longer pursued

### Creating a New RFC

1. Copy the template from `rfc-001-enterprise-policy-aliases.md`
2. Use the next sequential number (RFC-002, RFC-003, etc.)
3. Fill in all sections
4. Submit for review
5. Update this index

### RFC Sections

Every RFC should include:

- **Executive Summary:** One paragraph overview
- **Problem Statement:** What problem are we solving?
- **Design Goals:** Numbered list of principles
- **Technical Architecture:** How it works (with diagrams)
- **Security Considerations:** Trust model, threat vectors
- **Performance Analysis:** Complexity, benchmarks
- **Backward Compatibility:** Migration path
- **Alternative Approaches:** What we didn't do and why
- **Implementation Roadmap:** Phased delivery plan
- **Open Questions:** Decisions needing stakeholder input

## Related Documentation

- [Architecture Overview](../architecture.md)
- [Aphoria Product Spec](../../applications/aphoria/spec.md)
- [Aphoria Architecture Docs](../../applications/aphoria/docs/architecture/)
