During the London 2026 Collab Summit at Bloomberg's (thanks for hosting!), we identified the need for a new policy describing how to:

1. add a new subsystem
2. doing significant modifications to existing subsystem
3. making things easier to review in case of "heavy" code PRs

I would take on preparing this policy, but I would need input from reviewers on what would make their lives easier.

I've added a list underneath of what I would like to see, feel free to comment underneath and I will update the list

Key Requirements for this policy:

• applies to any PR over 3000 (+/-) changes
• requires the same approval path of a semver-major change (2 TSC approvals).
• discourage non-collaborators to open them (ban them)
• require an open issue/design document shared before the work start
• add a review guide in the top description pointing to the key files to review
• applies when adding a new dependency
• ...