Modularize the process

As part of a larger project of revisiting the W3C Process, simplifying it, and reducing the overall number of normative requirements, I would like to start by modularizing it. My hope (to be verified) is that it will improve usability and make it easier to experiment with process improvements (see also #1187 on experimentation). I propose work within the Process CG on an initial modularization that merely reorganizes the material (including changes approved since Process 2025) but otherwise does not change normative requirements. Once modularized, and with AB authorization to experiment, we would start to improve priority pieces (whatever module they are part of).

At a high level I propose these modules:

• Participation, which includes all policies, decisions and disputes, meetings.
• Document and group lifecycles
• Governance, which includes AC, AB, TAG, staff, technical agreements with other bodies, evolution of the Process, and experimentation.

After the initial modularization I hope to be able to work with the AB and Process CG on experiments as well as other simplifications to the Process. These discussions would also involve the W3C Systems Team (and potentially open source projects) to define, prioritize, and implement tools to make life easier for editors, group, AC Reps, and others.

I realize modularization will raise a number of topics that we'll discuss in the Process CG, including the number of documents, crosslinking, maintaining anchors, and so on.

No file or test is named; start with the issue proposal and review the current Process Document, including changes approved since Process 2025. Work through the Process CG discussion to define the module boundaries, while treating preserved normative requirements and decisions on document count, crosslinks, and anchors as completion criteria.