📜 RFC Process
The WealthFam RFC (Request for Comments) process is designed to ensure that major architectural decisions are vetted for Precision accuracy, cross-repository compatibility, and long-term maintainability.
🚀 When to Write an RFC
You MUST write an RFC before starting work on:
- Core Schema Changes: Modifying primary ledger tables in DuckDB.
- Cross-Service Communication: Changing how the Parser talks to the Backend.
- New Ingestion Channels: Implementing IMAP, Plaid, or new file upload logic.
- Breaking API Changes: Updating public endpoints used by the Mobile App.
🏗️ The Lifecycle
1. Proposal Phase
Create a new Markdown file in the Docs/Management/RFCs/ folder following the template 0000-feature-name.md.
- Summary: What is the problem?
- Technical Blueprint: How does it work? (Include Mermaid diagrams).
- Precision Impact: How does this affect data integrity and idempotency?
- Unresolved Questions: What items need team feedback?
2. Discussion Phase
Open a Pull Request for the RFC. The Engineering and SRE teams will leave comments focusing on:
- Performance bottlenecks.
- Security vulnerabilities (especially regarding PII in SMS/Email).
- Deployment complexity.
3. Vetting Phase
Once the RFC is approved by at least 2 core members, it is moved to the "Accepted" state. Implementation can begin in the respective repositories.
4. Implementation Phase
All code PRs should reference the RFC number (e.g., Ref: RFC #123).
🛡️ Precision Review Checklist
Every RFC must answer:
- Is it Idempotent? If the server crashes during this operation, can it be safely restarted?
- Is it Verifiable? How do we audit that the data produced is correct?
- Is it Scalable? Does this perform well with 10k+ transactions in DuckDB?
*Better Decisions · Technical Clarity · Engineering Excellence*