@candied_orange: I have edited the answer to make it more clear. But it is not about the specific subsets used by each individual method, since this would lead to a combinatorial explosion.

Using functions/modules where most appropriate and classes where most appropriate is absolutely a good design practice.

@DocBrown: In the scenario described in the question, the documentation is created by and for the developer team. So if an organizational process changes in a different department, how will this documentation for the developers get updated? Of course you can appoint some poor developer to be "responsible", but how will they even know some process or workflow have changed in a different part of the organization?

How do you keep this wiki updated when processes and workflows change in the organization?

The question is reasonable, but the answer is: there is no better term than "non-empty".

I suspect "non-empty" is going to cause less confusion.

The question is not about if there is bugs in the code. Soundness refers to the soundness of the type system of the language.