Google turns up nothing on that concept, but I agree that it is essential. You need a strong leader who can sense when stakeholders don't want to put up with that shit and when it's OK, and counterbalance that with how much of a dumpster fire the codebase is becoming.
You have to define who is in the team and who is not. Maybe Stakeholders are not. But inside the (cross-functional) team I would advise against "submarines" (german name for a secret project).
If the team can't handle this, the problem is somewhere else.
There's a difference between things that are secret because of people find out they will care, and things that are secret because people should not weigh in due to lack of knowledge or interest. I'm not sure how complex the system you are thinking of is, but in a system of even moderate complexity, the concept of team becomes abstract very quickly.
