How are new extensions formally proposed and tracked in the RISC-V ecosystem?

[Yash Kaushik]

Hey everyone,
I've been exploring the RISC-V extension landscape and noticed that some extensions present in instr_dict.json don't appear in the ISA manual yet, and vice versa. Is there a formal process or tracking mechanism for extension proposals like a GitHub issues tracker, a task group, or a ratification pipeline where the current status of an extension can be looked up? Trying to understand how an extension moves from draft to ratified.  

[Bill Traynor]

You can view the Specification Lifecycle here: https://riscv.org/specifications/development/#lifecycle

And specs under development are listed here:  https://riscv.github.io/adm-spec-dashboard/

On Thu, May 21, 2026 at 7:15 AM Yash Kaushik <yash005...@gmail.com> wrote:

Hey everyone,
I've been exploring the RISC-V extension landscape and noticed that some extensions present in instr_dict.json don't appear in the ISA manual yet, and vice versa. Is there a formal process or tracking mechanism for extension proposals like a GitHub issues tracker, a task group, or a ratification pipeline where the current status of an extension can be looked up? Trying to understand how an extension moves from draft to ratified.  

--
You received this message because you are subscribed to the Google Groups "RISC-V ISA Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isa-dev+u...@groups.riscv.org.
To view this discussion visit https://groups.google.com/a/groups.riscv.org/d/msgid/isa-dev/ea19d9bc-a968-4906-88c2-0e06c8977ae2n%40groups.riscv.org.