Thanks for keeping an eye on the documentation! Documentation usually doesn’t get the love it deserves, so any effort here is appreciated. Generally I agree with Bülent that this is not an “oversimplified” view and like his suggestion to split it up by workflow. Alternatively I could see benefit in a very simple diagram, but no subprocesses described. Basically Sentence Collector/Sentence Extractor/Bulk Upload -> Common Voice DB -> Recording/Validating on CV website -> Dataset without the subprocesses.
I would also like to avoid more duplication of diagrams, mostly when it comes to the Sentence Collector as we already have diagrams and explanations here: https://github.com/common-voice/sentence-collector#detailed-flow
The Sentence Extractor also has a quite extensive documentation here: https://github.com/Common-Voice/cv-sentence-extractor#common-voice-sentence-extractor . For this specifically, I can see that it’s not clear whether the Sentence Extractor does cleanup or not. It currently does not, it’s all based on the rules file. Essentially it validates every sentence and if it does not fulfill the rules, it tries the next one. Of course up to the limit per article of 3 sentences in the case of Wikipedia for example. A high-level diagram for this flow might be beneficial within that README, but I’d argue it should be very high-level and only include steps absolutely necessary. I can give this a shot tomorrow!
In the end, as processes and code changes, I would also like to avoid to forget documentation be updated, as it’s clear it would happen more often the more diagrams we have and the more detailed diagrams or explanations are in different places. Therefore the closer the diagram and explanations live to the actual process, the easier it is to not forget to update it.