ARB process design, RFC governance, decision log and technical review workflows
┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐
│ Proposal │───►│ Review │───►│ Decision │───►│ Record │
│ (RFC) │ │ (Meeting) │ │ (Vote) │ │ (ADR) │
└──────────┘ └──────────┘ └──────────┘ └──────────┘
Author ARB Board Approve/ Decision
writes reviews Reject/ logged
Defer
# RFC: [Title]
**Author**: [name]
**Date**: YYYY-MM-DD
**Status**: Draft / In Review / Approved / Rejected
## Problem Statement
[What problem are we solving and why now?]
## Proposed Solution
[Technical approach with diagrams]
## Alternatives Considered
| Option | Pros | Cons |
|--------|------|------|
| Option A | ... | ... |
| Option B | ... | ... |
## Impact Analysis
- Services affected: [list]
- Database changes: [yes/no, describe]
- API changes: [breaking/non-breaking]
- Performance impact: [estimate]
- Security implications: [describe]
## Migration Plan
[How to get from current state to proposed state]
## Risks
1. [Risk with mitigation]
## Open Questions
1. [Question that needs ARB input]
| Change Type | Review Required? |
|---|---|
| New external dependency | ✅ Yes |
| New database | ✅ Yes |
| New programming language | ✅ Yes |
| New microservice | ✅ Yes |
| Architecture pattern change | ✅ Yes |
| API breaking change | ✅ Yes |
| Internal refactoring | ❌ No (team decision) |
| Library update | ❌ No (unless major version) |
| Bug fixes | ❌ No |
| New feature (existing patterns) | ❌ No |
| ID | Date | Title | Decision | Rationale |
|----|------|-------|----------|-----------|
| ARB-001 | 2026-01 | Database choice | PostgreSQL | ACID, JSON support, team expertise |
| ARB-002 | 2026-02 | API framework | NestJS | TypeScript, modular, good ORM integration |
| ARB-003 | 2026-03 | Mobile framework | Flutter | Cross-platform, Dart performance, single codebase |