ArchForge
RFC · Decisions & Governance

RFCs

Float a proposal, gather the arguments, and reach a decision in the open.

FreeProEnterprise
Get started →All artifact types
archforge.app / rfc-014
RFC-014
Standardize internal RPC on gRPC
In Review
Proposal to replace bespoke JSON-over-HTTP internal calls with gRPC + protobuf for typed contracts and streaming.
PK
Priya K.
Strong +1 on typed contracts. How do we handle browser-facing edges that can’t speak gRPC?
DL
Declan L.
Edge stays REST via a gateway transcode. Internal hops only.
MR
Marco R.
Let’s capture the migration order as a follow-up playbook.
What it is

A Request for Comments is where a change is proposed and pressure-tested before it becomes a decision. Reviewers weigh in inline, trade-offs surface early, and once consensus lands the RFC graduates into an ADR — with the whole discussion preserved.

Structured discussion
Threaded comments attached to the proposal, not scattered across chat and email.
Review states
Draft → In Review → Approved / Rejected, with reviewers and outcomes recorded.
Graduates to an ADR
An approved RFC becomes the decision record it justified — no copy-paste, the lineage is kept.

Explore other artifact types

See all →
ADR
Decision Records
Capture the why behind every choice
PRN
Principles
The beliefs that guide every decision
STD
Standards
The guardrails teams build within
REF
Reference Architectures
Blueprints teams can actually adopt

Bring your rfcs into one place.

Start free and capture your first RFC in minutes — connected to everything else from day one.

Get started →Talk to sales