A home for technical decisions

Decisions,
documented.

RFC Zero Co. is focused on creating a better home for technical decision making. We are designing a platform where ideas can be proposed, discussed, revised, approved, and preserved for years.

What we are

A public record of how important ideas become real.

Most decisions disappear into meetings, chat messages, and private documents. RFC Zero gives every meaningful proposal a stable identity, a clear history, and a durable place to be discussed. It is infrastructure for organizational memory.

R

Request

Start with a concrete proposal that others can read, question, and improve.

F

For

Make the audience, ownership, context, and intended outcome explicit.

C

Comments

Collect review, dissent, evidence, revisions, and final reasoning in one place.

0

From zero

Begin with clarity, preserve the process, and build a source of truth over time.

One system, many decisions

Every RFC tells the complete story.

Personal proposals, public standards, internal architecture, operating policies, and product decisions can follow the same clear lifecycle.

RFCZERO-RFC-1

Define RFC Zero

Establish the platform’s purpose, terminology, governance model, and the principles that guide every future RFC.

Accepted
ACME-RFC-24

Adopt passkey authentication

Describe the migration path, security impact, operational risks, and rollout plan for a new authentication system.

In review
EMANUEL-RFC-3

Personal API design rules

Record a reusable set of design constraints for naming, versioning, error handling, and backward compatibility.

Draft
Our principles
01

Important decisions deserve permanent context.

02

Review should improve ideas, not bury them.

03

Revisions belong to one continuous history.

04

Public knowledge should remain readable and addressable.

05

Organizations should own their process and their data.