Some of you are probably groaning about me bringing up hardware theory yet again. But I promise you that this one will be a lot more straightforward.

  
From the pilot, we did see that there is an abandoned workstation with the brain scanner (the thing that looks like a vr headset) connected to it.

  
In episode 8, we did see Kinger accessing Caine's code. However, if you paid attention to the cmd window, you may have noticed it wasn't a command prompt, but a terminal prompt (they featured a Linux terminal, but the terminal in Unix and Linux distros are almost identical).

  
You will also notice that Kinger actually initiates a telnet connection, with his login credentials. But why would he need to make a telnet connection if the circus is running on the abandoned computer?

  
That's because it's not. The circus and Caine's AI is running on a different system, within the same network, which would presumably be a larger server. This server would be running a UNIX distribution (Linux was slowly gaining in popularity with Red Hat, but UNIX was the dominant OS between the two), which is why the telnet connection is necessary. Telnet allows Kinger to remotely connect to the server's terminal, and control the server (despite not having a GUI and limited to the command line). He can then enter and send commands to tweak Caine as needed.

Gooseworx erroneously depicts the computer running Windows 95, but in reality, it would have been running Windows NT 4, as the user accounts would have been network accounts, which again, would have its data files copied over the network, which makes Caine being able to access the mind files possible. A separate server running NT 4 server for the user accounts, and another running UNIX for Caine and the circus (and other projects).

  
For comparison, I feature the macOS terminal, as it is a UNIX certified distribution. Despite telnet being removed from macOS starting in version 10.13 due to a lack of encryption, I use Termius, which allows me to achieves the same thing, but more securely. In the example I provide, I'm using my Mac Mini to remotely connect to my MacBook Pro, which allows me to enter commands in its terminal session, in this case, I install Homebrew. The IP address visible is just the local network IP assigned by the router. 

  
The same way I remotely connected to my other Mac to install Homebrew, is the same way Kinger remotely connects to the server to try to fix Caine.

  
Now I can sleep at night.

Let's talk about how Kinger accessed caine's code