Update ARC1 admin and info

Author: d0cd

README.md

@@ -10,9 +10,27 @@ Aleo Request for Comments (ARCs) are protocol-level, network-level, and applicat
 ## ✍️ Getting Started
 
 To create a new ARC proposal:
-1. Copy template [ARC-0000](./arc-0000) into a new folder with the latest ARC number (ARC-XXXX)
-2. Open a [Github Discussion](https://github.com/AleoHQ/ARCs/discussions/categories/arcs) for your ARC number
-3. File a [Pull Request](https://github.com/AleoHQ/ARCs/pulls) to add your new ARC proposal
+1. Open a [Github Discussion](https://github.com/AleoHQ/ARCs/discussions/categories/arcs) with your proposal using template [ARC-0000](./arc-0000) and an available ARC number.
+2. File a [Pull Request](https://github.com/AleoHQ/ARCs/pulls) with your proposal in a new subdirectory.
+
+### Progressing an ARC
+
+An ARC will start as a "Draft" and progress through the following stages:
+
+Once a proposal is up:
+1. The community will discuss and review the proposal. A maintainer will monitor the ARC and change its status to "Active" once it is ready.
+   a. ARCs will be prioritized by number of votes and whether a prototype exists.
+   b. ARCs will be discussed during certain community calls. Proposers will have the opportunity to join and participate in the discussion.
+   c. Up to this point, the ARC can be withdrawn by the proposer or withdrawn by the maintainers if there is no activity for a long time.
+2. A governor or a team member of the Aleo Network Foundation (ANF) will create a formal proposal on Aleo governance (https://vote.aleo.org/) and initiate the voting process.
+3. The community will vote on the proposal for approval.
+4. If the proposal is accepted, its status will be updated to "Accepted" and the associated pull request will be merged into the ARCs repo. If the proposal is rejected, the status will be reverted to "Draft".
+5. The relevant parties should complete the implementation. Updates can be made to the ARC as needed through new PRs, which do not need votes.
+6. Once the implementation is finalized, the status will change from "Accepted" to "Final" or "Living", depending on the nature of the proposal.
+
+### Statuses
+
+See [ARC-0001](./arc-0001) for a detailed explanation of the statuses.
 
 ## 📜 License
 

arc-0001/README.md

@@ -29,14 +29,13 @@ graph LR
     end
 
     draft([Draft]) -.-> withdrawn([Withdrawn])
-    active([Active]) -.-> withdrawn([Withdrawn])
     
     subgraph standards
         active([Active]) --> decision{Decision}
         decision{Decision} --> accepted([Accepted])
     end
     
-    decision{Decision} -.-> rejected([Rejected])
+    decision{Decision} -.-> rejected([Draft])
 
     subgraph standards
         accepted([Accepted]) --> final([Final])
@@ -49,11 +48,9 @@ graph LR
 
 `Active` refers to a proposal with a reference implementation that is ready for review.
 
-`Withdrawn` refers to a proposal that was previously marked as `Idea`, `Draft`, or `Active`.
+`Withdrawn` refers to a proposal that was previously marked as `Draft`, or `Active`.
 
-`Accepted` refers to a proposal that was `Active` with a reference implementation, and has been approved by reviewer(s).
-
-`Rejected` refers to a proposal that was `Active` with a reference implementation, and has been denied by reviewer(s).
+`Accepted` refers to a proposal that has been approved by the community and is ready for implementation.
 
 `Final` refers to a proposal that was `Accepted`, and the reference implementation has been incorporated into Aleo. 
 

parser/index.js

@@ -15,7 +15,7 @@ const requiredMetadata = ['arc', 'title', 'authors', 'discussion', 'topic', 'sta
 
 const topics = ['Protocol', 'Network', 'Application', 'Meta'];
 
-const statuses = ['Draft', 'Active', 'Withdrawn', 'Accepted', 'Rejected', 'Final', 'Deprecated', 'Living'];
+const statuses = ['Draft', 'Active', 'Withdrawn', 'Accepted', 'Final', 'Deprecated', 'Living'];
 
 // Executes sanity checks for CI.
 const ci = () => {