Currently, this item is in the onboarding checklist:

Update project CoC reporting methods to include OpenJS Foundation escalation path

In investigating this for a currently incubating project, I've personally found it excessively difficult both to fully understand what the escalation path actually is since it seems to currently be not explicitly defined and have not found any official guidance on what implementing this for a project means - both in the sense of what kind of things a project can expect if the escalation path is used and what that path even looks like.

For context, one assertion that was made to me was that CoC violations in given projects can be escalated through this path and reviewed by the body they're escalated to - this is extremely concerning to me given the possibility of the escalation resulting in a turnover and a project being forced to allow someone to continue participating. This is an extremely concerning prospect, as it puts project membership in danger and it creates an extremely toxic power dynamic both between project members and the violator and between the OpenJS CPC group and projects.

Given the above concerns, I'd also like to recommend that we either temporarily address this for onboarding projects by either striking it from the onboarding checklist until the CoC WG can provide a more explicit checklist item that's well documented, defined, and positive for the projects or provide official temporary guidance to projects that are going through the onboarding process on how to address this point with absolute guarantees about how their community safety structures will not be overturned.