Overview

This document tracks the research and development progress of our project. It serves as the central hub for maintaining and improving our technical documentation, with the RFC Repository below acting as the single source of truth where all development documents (RFCs) are stored and organized by their current maturity status.

It also defines how the Logos Blockchain team creates, reviews, approves, and maintains technical documentation throughout its lifecycle. It covers:

• The purpose and required contents of Requests for Comments (RFCs) and Specifications.
• The maturity stages a document can move through (Raw → Draft → Verified → Merged → Stable → Deprecated → Retired → Deleted).
• The approval and disapproval criteria at each stage, including required reviewers.
• Versioning rules and responsibilities for updating dependent documents via specification backlinks.

<aside> 💡

We introduced this process to make it easier to track changes and maintain an up-to-date set of specifications. Some specifications were written before introducing this process, so they do not follow these requirements and have been transitioned manually.

</aside>

RFC Repository

• 🚧 Raw
• 📘 Draft
• ⚙️ Verified
• 🔀 Merged
• ✅ Stable
• ⚠️ Deprecated
• ❌ Retired
• ⚰️ Deleted

Documentation Maintaining Process

The basic type of a document that we maintain is Specification. It contains a clear description and must follow the IMPORTANT: Specs Quality Standard. We also maintain supplementary documents such as Analysis, Overview or Template, which are part of our documentation but are not Specifications.

Our documentation is maintained through a Requests for Comments (RFCs) process, which is laid out in this document. This process uses RFC documents to motivate, introduce, analyze, and approve changes to an existing specification, or to propose a new specification.