RFC · Decisions & Governance

RFCs

Float a proposal, hear every argument, and land a decision before the debate drags on.

FreeProEnterprise
archforge.app / rfc-0014
RFC-0014
Standardize internal RPC on gRPC
Open
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?
JO
Jordan O.
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 gets proposed and pressure-tested before anyone commits to it. Your teams weigh in on the proposal itself, trade-offs surface early, and when the RFC closes the outcome becomes a decision record with the whole discussion attached.

Start with structure
Every RFC opens with Summary, Motivation, Proposal, Alternatives, Risks, and Open questions, so proposals arrive ready to debate.
The debate, in one place
Comments live on the RFC while it’s open, not scattered across chat threads and email chains.
A clock on every RFC
Comments stay open for 60 days, with one extension to 90. When time is up the RFC closes on its own, so nothing lingers forever.
Authors stay in the loop
Authors get an in-app and email reminder five days before the deadline, with time to extend or wrap up.
Becomes a decision
Turn a closed RFC into a draft ADR in one click. The content carries over and the two stay linked.
Revise and go again
Not there yet? Spin a closed RFC into a new draft that supersedes it, keeping the first round on record.

Bring your RFCs into one place.

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