Image 6.1: Setting up an array variable to hold X, Y, Z location data and time
Here we set up a data variable to hold four things - your X location in the universe, your Y, your Z, and the current time.
The idea in this illustration is to take the X, Y, Z values of the location of the man and load these values into an array variable. The man is shown with his head located at 0,0,0.
Image 6.2: Creating a four by two dimensional array to hold location and time, and a program counter
Now we add a second column of boxes. This will hold a counter integer. That way, we can loop the program and not overwrite the data.
In this illustration, we add a second coluimn to hold a counter. This way, we can load our variable through time by inputting a loop factor. This illustration illustrates the value of adding one to our new column. This means we are on iteration one of our loop (just starting). On the next interaction of the loop, we will load the number two.
Image 6.3: An actual program that loads location and time data into the array over time
Here we write a computer program. It is a loop of 900 iterations. When it runs, it gathers X, Y, Z, and time data.
This is the actual program of the running loop to load the variable over time. This program loops 900 times. On each iteration of the loop, it loads X, Y, Z location data, the time, and the iteration number of the loop. The iteration number of the loop is loaded into variable A. It increments (A = A + 1) on each iteration of the loop.
Image 6.4: A computer program loop that reads each location and time, then writes the result out to the screen
After we run the program above, it fills the data array. This program is used to write the data out of the array.
Now that we have run our program, our array variable is loaded with 900 data rows, each with different location data. This program is written to get the data back out of the array. It too loops 1000 times, each time writing the location data to the screen.
Image 6.5: The actual output, in table form, when the program above is executed
Here is the actual data, including each iteraction of the loop, written to the screen.
When we run our read-data program, this is the result. You can see that for each iteration of the loop, the system recorded a loop counter, time value, and X, Y, and Z values. The output verifies that the array variable was indeed loaded as we intended.
Image 6.6: This is the result of mapping each row in the array (X, Y, Z and time) onto the environment
This image showing the actual X,Y,Z,T data being plotted onto the environment. Each red dot is a data point plotted from the array.
In this view, we show the location data from the array variable plotted onto the environment. Each red dot represents a data point that was entered into the array. The plot shows a man walking along a road. On each interaction of the loop, the system records the location and time of the man. When this data is read back and plotted onto the environment, it looks like this.
Image 6.7: Here we design a database table to hold the data of the lifeline array, instead of holding the data in memory
Rather than hold the location data in a variable, the illustration shows how we set up a table in a database to hold this data.
Recording our location data into a variable resident in memory is limiting. If we keep recording data, at some point, the memory will become exhausted. A better idea is to create a database table and load the data into there, instead of an array. This is the actual record layout of a database table used to record location data. This way we can fill our system with location data almost indefinitely without running out of memory.
Image 6.8: This is a continuously running program that records our location data, then writes it into a database
This is a computer program that picks up X,Y,Z,T data and writes it to the database table.
This is the actual computer program used to fill the database table with location data. The program will run as a continuous loop. On each iteration of the loop, it records the current value of the location. It also records the current loop counter. The database functions identically to the array but without the memory constraints.
Image 6.9: Data written to the database after running the database SQL program
This is the data held in the database table. By using a database, instead of holding data in memory, the table can expand without slowing down the computer.
Thiis is the actual contents held in the database table after the program above is run. As you can see, the values for location are added to the table. Conceptually, we have a similar program in our mind that records data over time. The program begins from our first moment and runs until our last moment.
Image 6.10: Adding a field, with datatype blob, to the lifeline database table. This field will hold the current environment.
In this view, we have added a field called environment to the array. A blob is a datatype that can hold an unlimited amount of data. Here we use it to store the moment/environment in total.
In this view, we are adding a new variable to our database table. The new variable is of BLOB datatype. BLOB (Binary Large Object) is a data type designed to store large binary data such as images, audio, video, or other multimedia files. It is particularly useful when you need to store unstructured binary data directly in the database. In our illustration, we are going to use the BLOB field to store the environment in its totality.
Image 6.11: Distributing storage of reality on two separate servers. One to record reality and one to store it.
In this view, we have distributed our system on two servers. One server runs the reality storing loop. The other server runs the database.
To make our system more robust, we are going to distribute it across two servers. On the left server, we are going to hold the current environment and our location loop program. We call it the lifeline program. On the right server, we are going to hold the database program that houses our location data table.
Image 6.12: The memory of the current environment is already in memory the moment we experience it
This is an rendition of the current moment environment. The environment is already in memory when experienced. It is that memory that gets stored into the blob data field.
This is an image of the environment. The idea is that this picture represents the entire surrounding three-dimensional environment. This includes site, sound, thoughts, and everything else that makes up the current environment.
Image 6.13: An artist concept of the reality computer absorbing the current environment
This is an illustration of the environment being stored into the blob data field, then the record being sent across to the database computer where it is stored permanently.
This is an artist rendition of the entire environment being gathered up and put into the BLOB variable. It is as if the mind has absorbed the current moment and read it into the BLOB data field. This action takes place on the left, the environment computer. It is an entire server used to experience and absorb the present environment. It works in the present moment only.
Image 6.14: The is the data array, including its numeric fields, and the blob to store the environment
This is another look the the record layout. As you can see, the environment is stored in the blob field, along with the X, Y, Z, and time data.
This is a visual rendition of the record layout. It shows two integer fields for holding counters. It shows four number fields for storing location data. It shows one BLOB field for storing the environment in total. This resides on the left, the environment computer.
Image 6.15: A diagram of the reality computer, gathering the environment in a continuous loop, and sending to the database computer.
Here is a concept drawing of the program loop, running in the reality computer. The current environment data is sent across to the database computer, where it is stored as a record permanently.
This is a computer view of the entire system. The location data loop is a running program on the left, the environment computer. On each iteration of the loop, the data is sent across to the database computer. In the database computer, the data gets recorded into the database. The record has counter variables that allow the data to be stacked into the database as shown here.
Image 6.16: A rendition of the reality computer when its reality processing program stops functioning. All environments are present in the database computer.
This drawing is to simulate what happens at the end of life. In this drawing, the left computer stops working without warning. When it does, all moments of life are stored in the right computer.
This illustration shows what happens at the end of life. At some point in life, the left environment computer stops processing the environment. The running program loop simply stops, never to start again. This happens without warning. When this happens, the right database computer contains every moment of life, retained from the beginning to the end. All moments combine into one continuous space-time continuum of unlimited space and time.
Image 6.17: View of the exact location of where afterlife exists within the physical universe
The physical location of afterlife is the final X,Y,Z,T location when the reality computer stopped. However, within that moment, all the data of life still exists. Time no longer applies.
This illustration shows the last moment. The physical location of the afterlife is the point in time and space represented by the red pointer. Within that single point lies a database full of moments and environments throughout life, as shown by the database table data on the left.
Image 6.18: Theend of life butterfly concept is when consciousness transitions into a new dimension, emerging better as a butterfly
This is an artist concept of the well known butterfly concept. In this concept, consciousness transitions into a new state. That new state is far better than its former state.
The idea that the end of life is the destruction of consciousness is not true. What is true is that the end of consciousness will result in something better. It is called the butterfly concept. As before, the butterfly is an unpretentious cocoon. After it becomes a magnificent butterfly. This mimics the emergence of consciousness. It goes in as a location within the environment and emerges as unlimited time and space.
Image 6.19: At the end of life it seems like the butterfly would be free to go anywhere in space-time
It would seem that the butterfly would be free to go anywhere within the space-time it finds itself within. However, what really happens is much better than that.
This is an artist rendition of what we feel should happen at the end of life. It shows a butterfly set free within a time-space of memory. On the left, we see the data in the reality table. The butterfly is aware of the two data points, as shown in red. The top point is where he was, as shown by the arrow. The bottom point is where he is. Under this scenario, the butterfly is aware of just the environments of the unlimited environments in the table.
Image 6.20: At end of life, actually the butterfly is freed completely. It expands, and thus goes everywhere throughout space-time simultaneously.
The final frame shows what happens as the end of life. Consciousness transitions to all time and space. It is as if consciousness is everywhere all at once.
This slide shows what really happens. In the data table on the left, the butterfly becomes aware of ALL the environments in the table, as shown by every data row being red. The result is that conscious awareness goes everywhere within time-space all at once. This results in eternal awareness throughout time and space. You can think of this as an exposition of awareness throughout time and space. Conscious awareness goes everywhere within time and within space. That is what happens at the end of life.
