Metamorphisis
In less than 8 and a half hours we will be experiencing Zero hour!! My sympthies to all those who cannot part-take. 
I just wanted to formally post my theory for all to view easily before the movie is released. It is a overly-simplified view of the technical aspects of how Neo was able to stop the Sentinals at the end of Reloaded, and how he is able to do some of the things he can do in Revo -- like see Smith inside of Bane. So, with less than 8 hours until the 0 hour of the Revolution, here it goes:
We know that the Machine mainframe is the source, as Stated in Neo's conversation with the Oracle in Reloaded:
However, the Architect declares that he is the one who programmed the matrix, this would make him the source of the matrix program itself. This, I believe is how Neo "touched" the source without entering the source.
It works like this:
Think of the machine mainframe as a Unix server. Your access flow chart would look like this (Users would be moving from the bottom of the chain up):
Root access at console station
/\
|
root access through network connection
/\
|
Root permissions inside networked shell access (no access to actual root, just the ability to manipulate things as if you were the Admin user)
/\
|
User access with extended permissions (Neo inside teh matrix)
/\
|
User access (all other bodies inside the matrix short of programs)
Hope you followed that because we're now going to use it.
Neo, and all other people inside the matrix, are just users of the system. The program is stored in the buffer of each individual person's pod, so if the system is updated (hardware upgrades, or software update -- like when the anomaly's in the past chose to reload the matrix) there is no temporary loss of connection between those plugged into the matrix and the Machine's Mainframe server.
Neo gained extended permissions inside the Matrix program because of the anomaly code he carries (his subconscious rejected the programming upon birth and is only now coming to fruitation). When he "died", the traumatic experience triggered an extreme manifestation of the code because his mind has already rejected the Matrix, so the matrix, essentially, cannot kill his mind. Once he's gained these "extended permissions" (and his abilities inside the matrix) he starts on the path to the Source, the machine mainframe, and our unix server.
When he visits the Architect, he is also exiting the Matrix program, while still staying connected to the machine computer network. (just as the backdoors appear to be on the outside of the matrix program) By doing this he is entering a "shell account" outside of the matrix program and on the mainframe to communicate with the Architect.
This, and his interaction with the Architect, inadvertently gives Neo root permissions (super user access) on the system. The machines never had to worry about this before, as the anomaly always chose to save the species as a whole, but they understood the possibility of the anomaly choosing to re-enter the matrix. When Neo does this, he does not loose his super-user status, however, and, as he has touched the source, his mind does not completely disconnect from the matrix computer system.
The machines would need a wireless network capability since so many of them are mobile, and yet they all seem to have a central intelligence (the mainframe), so they all know what's going on, both inside, and outside of the matrix.
Because of the implants in the humans that are used to connect them to the matrix, they can pick up on the wireless signal (all metals act as antennea's, it's just a matter of filtering for frequency and interpreting the transmissions), but, their brains do not interpret the signals because it is weak compared to their sensory input, and is not a connection to the Matrix program, but to the actual machine mainframe system (the SOURCE)!! No one has permissions to access anything beyond the Matrix program on the machine mainframe.
Because Neo does gain root access on the Machine Mainframe at the end of Reloaded, he is not locked out of that portion of the wireless signal, so his brain can interpret the data received by it -- thus allowing him to "feel" the Sentinels as he does the Agents inside the Matrix.
The Bane version of Smith has the same root access to the mainframe, so he would know where the sentinels are if he wanted to, say, discharge EMP before the sentinels are within range, AND destroy resistance ships (as it happened at the end of Reloaded).
Also, sentinels would know that Bane is really the program Smith, so they would not kill him upon sight, but rather let him infiltrate the resistance ranks to destroy Zion and kill the Anomaly.
When Neo is blinded in Revo, he is still able to see because of the wireless machine signal that he is recieving. It would be transmitting a sonar like 3D map of the world from whatever reference point you would be standing at. So Neo would be able to see Bane for what he is, Smith, in Revo because, when he is blinded, he see's what the Machines are broadcasting, and they aren't broadcasting the human, Bane, but rather Smith, the program inside of Bane!!
I just wanted to formally post my theory for all to view easily before the movie is released. It is a overly-simplified view of the technical aspects of how Neo was able to stop the Sentinals at the end of Reloaded, and how he is able to do some of the things he can do in Revo -- like see Smith inside of Bane. So, with less than 8 hours until the 0 hour of the Revolution, here it goes:
We know that the Machine mainframe is the source, as Stated in Neo's conversation with the Oracle in Reloaded:
However, the Architect declares that he is the one who programmed the matrix, this would make him the source of the matrix program itself. This, I believe is how Neo "touched" the source without entering the source.
It works like this:
Think of the machine mainframe as a Unix server. Your access flow chart would look like this (Users would be moving from the bottom of the chain up):
Root access at console station
/\
|
root access through network connection
/\
|
Root permissions inside networked shell access (no access to actual root, just the ability to manipulate things as if you were the Admin user)
/\
|
User access with extended permissions (Neo inside teh matrix)
/\
|
User access (all other bodies inside the matrix short of programs)
Hope you followed that because we're now going to use it.
Neo, and all other people inside the matrix, are just users of the system. The program is stored in the buffer of each individual person's pod, so if the system is updated (hardware upgrades, or software update -- like when the anomaly's in the past chose to reload the matrix) there is no temporary loss of connection between those plugged into the matrix and the Machine's Mainframe server.
Neo gained extended permissions inside the Matrix program because of the anomaly code he carries (his subconscious rejected the programming upon birth and is only now coming to fruitation). When he "died", the traumatic experience triggered an extreme manifestation of the code because his mind has already rejected the Matrix, so the matrix, essentially, cannot kill his mind. Once he's gained these "extended permissions" (and his abilities inside the matrix) he starts on the path to the Source, the machine mainframe, and our unix server.
When he visits the Architect, he is also exiting the Matrix program, while still staying connected to the machine computer network. (just as the backdoors appear to be on the outside of the matrix program) By doing this he is entering a "shell account" outside of the matrix program and on the mainframe to communicate with the Architect.
This, and his interaction with the Architect, inadvertently gives Neo root permissions (super user access) on the system. The machines never had to worry about this before, as the anomaly always chose to save the species as a whole, but they understood the possibility of the anomaly choosing to re-enter the matrix. When Neo does this, he does not loose his super-user status, however, and, as he has touched the source, his mind does not completely disconnect from the matrix computer system.
The machines would need a wireless network capability since so many of them are mobile, and yet they all seem to have a central intelligence (the mainframe), so they all know what's going on, both inside, and outside of the matrix.
Because of the implants in the humans that are used to connect them to the matrix, they can pick up on the wireless signal (all metals act as antennea's, it's just a matter of filtering for frequency and interpreting the transmissions), but, their brains do not interpret the signals because it is weak compared to their sensory input, and is not a connection to the Matrix program, but to the actual machine mainframe system (the SOURCE)!! No one has permissions to access anything beyond the Matrix program on the machine mainframe.
Because Neo does gain root access on the Machine Mainframe at the end of Reloaded, he is not locked out of that portion of the wireless signal, so his brain can interpret the data received by it -- thus allowing him to "feel" the Sentinels as he does the Agents inside the Matrix.
The Bane version of Smith has the same root access to the mainframe, so he would know where the sentinels are if he wanted to, say, discharge EMP before the sentinels are within range, AND destroy resistance ships (as it happened at the end of Reloaded).
Also, sentinels would know that Bane is really the program Smith, so they would not kill him upon sight, but rather let him infiltrate the resistance ranks to destroy Zion and kill the Anomaly.
When Neo is blinded in Revo, he is still able to see because of the wireless machine signal that he is recieving. It would be transmitting a sonar like 3D map of the world from whatever reference point you would be standing at. So Neo would be able to see Bane for what he is, Smith, in Revo because, when he is blinded, he see's what the Machines are broadcasting, and they aren't broadcasting the human, Bane, but rather Smith, the program inside of Bane!!
