Diagram on the TOC process page that does not correctly reflect the current version of the process

[riaankleinhans]

Orgiginal from Slack
There is a longstanding unresolved point of confusion wrt moving levels. The existing process diagram on the TOC process page that does not correctly reflect the current version of the process.
In days of olde... projects with a sponsor to move levels were to present to the SIG/TAG in order to receive a domain recommendation within the DD from the TAG. That was removed due to inconsistencies in the evaluation and considerations to arrive at a recommendation (and general lack of understanding of when in the DD it occurs).
This has since been removed from the written process, but exists in the diagram.

I think it is beneficial for projects to present and discuss their project with the TAG either for their own benefit (non-DD path) as well as for the benefit of the TOC (particularly when serving in an extended technical domain capacity such as the TAGs do).

This should not be a requirement, unless the project would like a TAG recommendation. But this would need to be explicit in whatever updates we make, and certainly not a requirement for moving levels UNLESS we introduce clear structure for the TAGs to consistently evaluate the project in order to produce a recommendations. Which, if this was done, would introduce countless delays and likely make the process longer.

TODO:

• Resolve the mismatch between the writen content and the diagram once the project criteria task force work have been concluded.