From d14dd9f26ab0953c3268b1db25d8e8059adc1315 Mon Sep 17 00:00:00 2001
From: Jimmy Debe <91767824+jimstir@users.noreply.github.com>
Date: Tue, 27 Feb 2024 20:14:47 -0500
Subject: [PATCH] Update README.md

---
 README.md | 15 ++++++++++++---
 1 file changed, 12 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index a54017a..d8b24a2 100644
--- a/README.md
+++ b/README.md
@@ -7,15 +7,24 @@ This repository contains specifications from the [Waku](https://waku.org/), [Nom
 [Vac](https://vac.dev) is an [IFT service](https://free.technology/services) that will manage the RFC process within this repository.
 The goal of the RFC, [Request for Comments](https://en.wikipedia.org/wiki/Request_for_Comments),
 process is to standardize technical specifications. 
-Specifications will adhere to [1/COSS](./vac/1/coss.md) by obtaining a rough consensus within each project.
 
 ## New RFC Process
 
-(todo, explain new process)
+Each project will maintain initial specifications in separate repositories, 
+which may be considered as a **raw** specifications.
+All [Vac](https://vac.dev) **raw** specifications and discussions will live in the Vac subdirectory.
+When projects have reached a rough consensus for a specification living in their repository,
+the process of updating the status to **draft** will begin in this repository.
+Specifications will adhere to [1/COSS](./vac/1/coss.md) before obtaining the **draft** status.
+
+Implementations should follow specifications as described,
+all contributions will be discussed before the **stable** status is obtained.
+The goal of this RFC process will to engage all interseted parities and 
+reach a rough consensus for techcinal specifications.
 
 ## Contributing
 
-Please see [1/COSS](https://rfc.vac.dev/spec/1/) for general guidelines and specification lifecycle.
+Please see [1/COSS](./vac/1/coss.md) for general guidelines and specification lifecycle.
 
 Feel free to join the [Vac discord](https://discord.gg/Vy54fEWuqC).