This review is completed by the isa_chairs@riscv.org (privand unpriv). Eventually this slide should contain what it is and what the timeline is for those in the queue,

From Greg's email:

• Consistency with the RISC-V architecture and philosophy
• Documentation clarity and completeness
• Including proper distinction between normative and non-normative text
• Motivation and rationale for the features, instructions, and CSRs
• Utility and efficiency (relative to existing architectural features and mechanisms)
• Is there enough value or benefit to justify the cost of implementation
• Is the cost in terms of area, timing, and complexity reasonable
• Proof of Concept (PoC)
• Software PoC to ensure feature completeness and appropriateness for intended use cases
• Hardware PoC to demonstrate reasonable implementability
• Inappropriate references to protected IP (i.e. covered by patents, copyright, etc.)