The source code is the key!
When you’re doing a system that has to be validated you have to be able to match the source code to the Executable file that’s running. (the .EXE file)
People stuck in the weeds not knowing when to accept a W for the win.
The public doesn’t need the source code. The public needs the assessment from the source code and the validated confirmation that the transfer of 6,000 votes from President Trump to Joe Biden occurred.
That opens up major problems for certification in Michigan. It can’t be glossed over.
If there wasn’t human error in the “glitch” transfer of votes, the blame falls on the Dominion machine/software.
That’s what the American public needs to hear TODAY!
The EXE file which was used on that day at that time.
You know, the mainframe guys have “disassembler” programs, that can read a “load module” (probably an archaic term now) and regurgitate back up an assembly code listing - which can in turn, in the right situation, be very useful to people who happen to be very knowledgeable about how certain compilers work. Like, the guys who wrote the compiler.
Source code IS WORTHLESS in this scenario without the exact same environment the executable binary running in the machine was built with. Source may have not changed but if a different version of the compiler/linker was used, it may produce a different binary. Different static libraries on the OS development system would change the binary.
The program might accept a value that is fed in at run time, a value that can adjust the counts, e.g. by a certain percentage. If that is the case, then examining the source code, or even executing the program, would only tell you the program was wide open to fraud, it wouldn’t prove that fraud had been committed.