But thanks to some research and documentation browsing, I will only need to make 4... dynamic column allocation! Part of a Kivy screen is python code, and part is a language for screen layout in a language specific to kivy... an exact analog for the java/kotlin android files with their xml layout files, which means I can read the header row for each csv file and dynamically allocate columns on the screen!

The difficult part to figure out was the need for a "logic layer" that glues everything together... what Python was made for! Here I have meta data that includes arguments for function calls based on each game's configuration. In this way pick 2 knows it needs 2 columns, while bonus ball games and the match 6 know they need 6 columns. This takes the place of when I run the scripts having to enter the specific configuration of each game in the function call. This output configuration can be used for both the classification and the follower scripts. The second set of files will be needed to display the column statistics for the classifiers.

4 files instead of 20! The added benefit is the ability to add any game configuration in the future... such as if they bring back a variant of the Super 7... with only the need to add a csv file and it's associated meta data profile.

Got the idea while searching stack overflow and found guidelines in the kivy docs on implementation.

Did a test render for the pick 2, and the screen was clean with perfectly aligned sample data, so the next step is to fully wire in the follower script and compare output to the original follower script to ensure it matches. 

Getting there!