Corresponding slack discussion in TOC private: https://cloud-native.slack.com/archives/G01MNU51LFM/p1736305335718719

* We do not hold projects back from moving levels on factors outside the project’s control that are probabilistic occurrences because many factors can change at a moments notice.

Not exactly sure where to add this, so i left this out. Going to open the PR shortly!

* For graduated projects all critical and high issues from the security audit must be resolved.  For medium & low items - they should (not a requirement but strongly encourage) have a corresponding issue opened on the repo to track it to closure.

Confirmed this is already in the dd-toc-guide.md

First 💕 thank you! For the not holding back projects bit, I would put that at the end of the paragraph of line 166. It would fit perfectly.

First 💕 thank you! For the not holding back projects bit, I would put that at the end of the paragraph of line 166. It would fit perfectly.

Awesome, PR is updated: https://github.com/cncf/toc/pull/1533/files PTAL! Thanks Emily!

@TheFoxAtWork @linsun this is adding requirements for specification projects to the DD guide - where are those requirements initially captured and reviewed? From what I recall, the private-toc thread was initiated because the TOC does not have requirements specified. However, if that is inaccurate - those requirements for specification projects should be linked in the attached PR.