Project Theory

This article explains the theoretical problems of recovering the inspired text of the Bible. It starts with some simple points from communications theory. This theoretical model suggests the nature of the problems that any inspired system of error detection and correction must solve. It then reviews our many failed attempts at manuscript recovery. Each of these enriched our understanding of the problem in various ways. Finally, it explains our working understanding about how the letter-perfect inspired text of the Bible will ultimately be recovered.

Please use the standard contact form to provide comments or feedback.

Communication Theory

The computer world has some theoretical models for understanding problems with error detection and correction in transmitted messages. These models give some insight to the problems we face in recovering the letter-perfect inspired text of the Bible.

Sending messages over computer cabling, for example, is very different than sending messages between Earth and Mars. Computer cables see few errors and retransmission is fast and easy.

Messages to and from Mars are subject to complex errors mostly caused by sunspots and the locations of the planets around the sun. Transmission of messages across the expanse of space is thus much more difficult. Errors in this environment are much more likely. The distance between sender and receiver limits the speed of retransmission.

It should be obvious that the design of error detection and correction systems for these 2 situations are very different.

In the most general case, error detection and correction systems are tuned to 1) the type of message being sent, 2) the difficulty of retransmission and 3) the expected nature of transmission errors.

The Bible is obviously not a computer communications problem. But it has the same theoretical problems. What is the nature of the message being sent? How hard is retransmission? What sort of errors would be expected to happen with the text across time?

Ultimately, any real system used by the text will address these theoretical challenges.

Nature of the Message

We understand from our 3d alphabet work that the text was originally written with 22 letters and 3 punctuations. There are 25 such drawn characters in this system. These characters make up the font used for inspired text.

For readers perhaps new to our work, the 3d system is highly constrained. There are about 150 3d models that make up the entire system. This set of models has a very simple set of governing principles. The entire set of models follow those principles and work together to both error detect and error correct all of the drawn forms of the letters used to write inspired text.

So the inspired message has a complete error detection and correction system running at the bottom layer of any text, the drawn forms of the letters. Because this exists at the letter level, we have long been looking for the same system at the level of running text as written by scribes and read by people.

So the running text is a long string of 25 different characters. This is the fundamental nature of the message of the text. Any error detection and correction system must be able to discriminate between these 25 different drawn forms.

Recent 3d work suggests that 6 of the letter characters and 1 of the punctuation characters have something like duplicates. This is not a difference in drawn forms, but might still be impacting the running text.

So any error detection system would need to be able to distinguish from perhaps 32 different cases at each letter position in running text.

Note that 32 is a power of 2. Expressed as binary, we could just as easily say we are looking for 5 different on/off flags that apply against each letter in the running text.

The exact expression of this system is unknown. We are ultimately hunting for some system that is confirming inspiration. It must be running in parallel to the running characters in the text. It must be providing some source of error detection and correction data at about this pace.

Process Of Inspiration

The text itself was originally given to authors who wrote down what they were told. More formally, we say they wrote the inspired text as they were inspired to write. Here is the defining verse on this point.

16All Scripture is God-breathed and is useful for teaching, rebuking, correcting and training in righteousness, (2 Timothy 3:16 NIV)

The process where the text is 'god breathed' makes inspired text different than text written by men alone. Ultimately we are searching for some aspect of running inspired text that reveals or proves some god-breathed characteristic.

Note, the verse quoted here rejects the idea that scripture is inspired because it is accepted by some faith community as inspired.

Nearly all religious books on Earth are accepted by their community as scripture. We accept this is true even of the Bible in Christian communities. Community support does not set apart the Bible, nor the churches that hold to it. It does not stop additional documents, say the Book of Mormon, from entering the fray.

Proof of inspiration will not rest in the testimony of a faith community. We believe the answer is technical, some technical aspect of the written text itself will provide the proof of inspiration. We already know this to be true for the drawn letter forms, so our expectation is well grounded.

Inspired writers were normally writing about something that they themselves witnessed. For this reason, inspired writers are spread out across history. They wrote about events from their own time in history. Exceptions to this general idea do exist in the text.

For a simple example, consider the Book of Judges. It was written by Samuel to demonstrate concretely the problems of having kings. Samuel's writings thus span several centuries preceding his lifetime. Samuel was not a direct personal witness to all of the events in Judges.

Samuel may have had access to public records. He may have had access to personal diaries from those centuries. Even if he had some access to earlier written records, the important point here is that Samuel wrote it down in some inspired way. Samuel was the active agent in the 'god-breathed' process.

Luke has another example worth considering. Here is the important verse:

3Therefore, since I myself have carefully investigated everything from the beginning, it seemed good also to me to write an orderly account for you, most excellent Theophilus, (Luke 1:3 NIV)

This introduction suggests the original author had access either to earlier notes, or more likely personal access to the original witnesses. The process of writing the account that follows is the time when it became 'god-breathed.'

As with Samuel, and all other inspired writers, the process of inspiration kicked in when the writer was deciding exactly how to write the stories that they already knew to paper with pen and ink.

Because there are no obvious textual markers used to check the work of the inspired writers, we believe the proof of inspiration was entering the running text at the same time as the process of inspiration was happening with writers.

The proof of inspiration will somehow mark otherwise normal written text as inspired. That text must reveal inspiration through some aspect that makes it different from the text of regular non-inspired writers.

This must especially mark something that is different from the work of the editors. It will also mark something that is different from all other religious books.

We do not believe this is a content related marker. We believe it runs at the level of the string of letters in written text.

This is a very high bar for inspired text to meet. That system of inspiration becomes the basis for faith in the text. From there, what it ultimately says about salvation can also be trusted.

Media Used For The Text

The text records 2 primary different types of media used to record inspired scripture. These were ink on scrolls and carved stones. Scrolls were the common form, but stone copies formed the basis for master copies.


The normal media for writing for most of history has been parchment or leather with hand drawn black ink letters. The ink formula is normally soot suspended in water mixed with a fuser. The fuser was normally some sort of vinegar. This same general formula for ink is still used in laser printers today.

In order to produce a scroll, inspired writers and the scribes making copies would need access to water, wood, burned for soot, and a vineyard for making vinegar. These ingredients were needed in order to produce the ink for making copies.

The recipe for ink is behind the treaty after the Gibeonite deception. Here is the relevant verse:

21They continued, "Let them live, but let them be woodcutters and water carriers for the entire community." So the leaders' promise to them was kept. (Joshua 9:21 NIV)

This is important because this is near Shechem. We believe this to be the location of Abraham's ranch. It was also the location where the text was carved in stone. The NT knows the place as Sychar.

The Gibeonites were not carriers of water and wood for the entire country. They were carriers specifically in that location. This is important because they were providing supplies for making copies of the text that would be carried to the whole country.

There is a long series of stories that chain from this passage about Gibeon. Those stories lead to Samaria, and eventually to Naboth and his vineyard. This was apparently the source for the vinegar used in the ink.

1Some time later there was an incident involving a vineyard belonging to Naboth the Jezreelite. The vineyard was in Jezreel, close to the palace of Ahab king of Samaria. 2Ahab said to Naboth, "Let me have your vineyard to use for a vegetable garden, since it is close to my palace. In exchange I will give you a better vineyard or, if you prefer, I will pay you whatever it is worth." 1 Kings 21:1-23But Naboth replied, "The LORD forbid that I should give you the inheritance of my fathers." 1 Kings 21:3 (1 Kings 21:1-3 NIV)

Naboth's heritage apparently goes back to the time of Joshua son of Nun. We believe this was the single source of the fuser used for making copies. This is why Naboth would not stand down when asked to sell out his vineyard.

When kept dry, manuscripts built this way can last indefinitely. The Dead Sea Scrolls are widely thought to be over 2000 years old. Though not thought inspired themselves, they demonstrate that good copies on historically known media can last a very long time.

Carved Stones and Tombs

The other media for keeping inspired copies was stone. This happened on mountain sides of Ebal and Gerizim, both located near Shechem.

This general region was used for observing the Tabernacles holidays. Late in the time of the Judges it was used for national assemblies, especially appointing of new kings. So this was a natural place for a public copy of inspired text to be carved in stone.

The Shechem area was also the general region of Abraham's ranch.

Stone as a solid media will endure, but the public nature of a monument copy of the text would make it susceptible to public defacement.

For this reason a tomb made a better place for keeping copies safe over long periods of time. This also happened near Shechem as Acts records. Here is the important verse.

16Their bodies were brought back to Shechem and placed in the tomb that Abraham had bought from the sons of Hamor at Shechem for a certain sum of money. (Acts 7:16 NIV)

Use of the tomb for family burials provided the cover. Superstitions over dead bodies provided some enduring protection.

When the inspired text was widely known, there would always be a known good copy around to check against if a mistake was found in any individual copy. A friend's scroll would be the quickest and easiest way to find the error. When available, the stone monument copies could be referenced for finding errors with individual scrolls.

In times of distress, say when Jezebel is killing prophets, then those few who knew the location of the tomb/cave could go there. Elijah likely returned to that place in 1 Kings 19:9. He was likely rebuilding the master public copies from the vault copies. Later editors likely gave that simple purpose a difference venue.

The use of the tomb/vault as the hidden reference copy was used from the time of Abraham to the Field Ripe for harvest. The Field Ripe For Harvest is the last time that vault was opened. This cave was used for about 2000 years in total.

Scrolls buried within that tomb/vault appear to have been refreshed about once every 500 years.

This is well below the time intervals of the dead sea scrolls. So ink on scrolls kept in caves was a reasonable archive for use across that interval.

At other times in history, without any reference to known good copies, then the text would need to be completely recovered from the systems that mark inspiration. We are in such a time now.


In computer networks, when a receiver of a message detects an error, they typically ask the sender to retransmit the message.

In modern, hard-wired, computer networks, retransmission is easy. Computer networks keep copies of all messages around until they know the receiver has confirmed they have received an accurate copy.

If there is a error on the receiver's end, the network sends the last known good copy down the wire again. This is fast and easy and happens almost transparently to typical users. Errors on these networks become time delays as seen by typical users.

This is like a scribe checking their master copy when an error has been found in a new copy of the scroll. If the master copy is not hard to reference, then checking against that master copy is a quick and an easy way to find and fix errors.

In the case of inspired scripture, what would happen if the oldest extant copies of the manuscript are shown to contain an error? In this case there is no longer a known-good copy around for reference.

In this case, asking again for divine inspiration would be the only choice left.

But, asking again for divine inspiration has a very different problem.

Part of the proof of inspiration is that the text was dictated in small sections across a long span of history. This was especially interesting in periods of history where humans only had very low technology. In those eras writing itself was hard to do. It was nearly always very expensive and scrolls were very valuable artifacts.

Retransmission, really re-inspiration, would upset an aspect of how god works in history across time. The authors are building a textual record that transcends time. That writing spread across time is witness to what was going on.

The story of the Tower of Babel is indicative of the problem. The people of that day wrote a legacy for themselves, claiming their text to be divine. Many other religious texts have followed down through history. Passages of the Bible which are not inspired are doing the same even now.

Retransmission via re-inspiration would easily look like any number of other similar frauds seen across history.

So we expect that retransmission through re-inspiration of inscribed text is not going to happen.

Instead, there must be some way to study text as received and from that either prove it is inspired, or else know how to correct it to its provably inspired form.

This case exists in computers already, and we can learn from that. In these sorts of networks the message typically needs to be encoded in a way where retransmission is not needed.

This means that the transmitted message contains designed-in constraints as to what is legal in the message. The receiver must check that those constraints are met. If those constraints are not met, the receiver must use the data that was received to figure out the correct message.

Messages being sent around that can self-correct are longer than they would otherwise need to be.

Error correcting parity bits, used in computer server memory systems, are perhaps the best known example of how messages are made longer. Depending on the design, a 32 bit word of real data might carry around an additional 4 bits. This is enough to both detect and correct any 1 bit error in the real data.

Those extra bits can be used to fix defective messages without the need to retry. These extra bits of information are the expected real cost for not needing a retransmission.

This computer example shows an aspect of the theoretical problem. Longer messages are but one way to make messages recoverable. The other way to make messages recoverable is to limit what messages are legal.

This has profound implications in terms of detecting errors introduced as inspired text but which were originally only written by people. The divine inspiration could have been limiting messages into legal forms, while human authors, without divine inspiration, would not have known or understood any such constraints. Their work should be expected to overload the error detection system.

Whatever the system is that proves divine inspiration, it will be able to both detect and correct errors. It will not need retransmission, neither re-inspiration, nor reference to a vault copy.

From communications theory we know this means either 1) the messages are longer than would otherwise be needed, or 2) not all possible messages are legal, or 3) some combination of 1 and 2.

As the only thing transmitted by scribes through history are strings of text, it is likely to be the case that not all possible written texts will be legal.

Block Chain Copies

In the early days of computers, back up copies of computer files were kept in abandoned salt mines. Such mines near Kansas City were a popular place to keep backups.

Backups kept this way cannot be speedily recovered. It typically took a few days to get a tape retrieved from such a mine. Then it took time to get the tape read back onto the computer's disk drives.

Modern computer backups are usually done through distributed copies. A typical business laptop is backed up to a distant server, ideally in a distant place outside of potential war zones. Should the laptop, or the server, ever go down, the other can be used for recovery.

In these scenarios there is only a limited number of copies, the primary and then a secondary.

Computer block chains go one step further. Information on block chain systems is copied to hundreds or thousands of nodes. This is the high tech version of distributed libraries.

Loss of any single node, or even a cluster of nodes, does not cause any significant loss of information.

For the past 2000 years the back up system for inspired text was block-chain like. Copies of scrolls were kept in libraries around the developed and developing world.

Of course the Roman Empire of the first century was not long-term stable. But, many places within the empire were safe enough for keeping interesting copies.

These days, dusty copies of recoverable inspired text must be found by looking in libraries spread around the world.

Because Rome was in effect a perpetual war zone, the interesting copies of the inspired scrolls were not exactly within the Roman Empire, but on the eastern fringes.

In the internet age finding much of this information is even easier. Digital copies of reference manuscripts are available for public download from places like the Internet Archive.

Unfortunately, the internet is not fundamentally a block chain system, which means it is not as robust as libraries. Truth is only what those who control search functions want it to be. The ease with which digital copies of anything can be downloaded looks to be a limited historical season. We take advantage of it while we can.

Human DNA?

The vault recovery of inspired scrolls in the NT era was done AFTER a by-hand recovery of the text from extant public texts. This insight took us many years to see. It bears on our work in many ways. Most important is that it was 1) done by hand 2) before the vault was opened.

As will be explained below, we feel we need to follow this order as we do our recovery work.

If there remains a master vault copy somewhere, we would expect it to be uncovered only after recovery from extant texts.

We currently hunch that human DNA stands a good chance of the place where that master copy might be found. Curiously enough, the Human Genome is in everyone, so it is block chain like in terms of redundancy. For now, it is also easily downloaded from the internet.

Use of copies essentially hidden in plain sight is another reflection of divine character. Joshua can preserve the text, just as he can preserve people.

Nature of Expected Errors

2 distinctly different sources of errors are possible in inspired text. These 2 sources of errors are the theoretical basis that any error detection and correction system would be able to detect and correct.

Textual Errors

In eras when the text was handled by faithful scribes and known good copies were readily available, then the errors would normally be within the scope of the written letters themselves.

These errors would express themselves as spelling or punctuation related errors. There are quite a few different exact types of errors in this space. All that matters is the running text had errors from well meaning but careless scribes. The resultant scrolls would be generally correct, but contain minor textual defects.

Malicious Errors

In eras with hostile kings and priests the nature of the expected errors shifts to include whole cloth additions. There are many passages in the text that hint at or inform the nature of these sorts of changes.

The nature of this problem is best understood by looking at the problem of kings. Kings are the fundamental drivers for malicious errors.

The key passage about kings is found in Samuel. Samuel had grown old, and the people came to him and wanted a king. They wanted to be just like all the peoples around. They did not want to be special any more. Here is the key quote:

5They said to him, "You are old, and your sons do not walk in your ways; now appoint a king to lead us, such as all the other nations have." 6But when they said, "Give us a king to lead us," this displeased Samuel; so he prayed to the LORD. 7And the LORD told him: "Listen to all that the people are saying to you; it is not you they have rejected, but they have rejected me as their king. 8As they have done from the day I brought them up out of Egypt until this day, forsaking me and serving other gods, so they are doing to you. 9Now listen to them; but warn them solemnly and let them know what the king who will reign over them will do." 1 Samuel 8:6-9 (1 Samuel 8:5-9 NIV)

Note carefully, that the people already had a king, god himself, and they were now rejecting that king for an earthly king. Their previous king had been Pharaoh. They had been freed of Pharaoh around 400 years earlier. They were returning to Egypt.

They were granted their request, first with Saul, and then many more who would span across the rest of their time living in Canaan.

So how do kings get divine endorsement when they are fundamentally the villains in this story?

Stated simply, they want to fake divine endorsement.

They get that false endorsement by finding some way to claim divine authority. Since the public venerates the text, they can transfer that veneration to themselves by changing the text to venerate themselves and their priests.

The fundamental desire to put words in god's mouth is the motive behind all the known Bible editors. This is the second source of textual errors.

The passage quoted above is contradicted across the text of the Bible. Why? Because the Bible has been extensively edited by kings and their priests.

Their changes to the text made it seem that god agrees with their policies and practices which are otherwise quite godless.

Generations future to the editing king do not know there was a different version in the past. Remember, scrolls were usually very expensive and few people had personal copies, so purging inspired text from the public sphere was relatively easy.

Any theoretical error detection and correction system that operates against the Bible will be able to not only detect and correct scribal errors at the level of how words are spelled, but it will also be able to flag large blocks of text that were added whole cloth.

The Need For Delivery

In modern communications theory it is well known that the message must first reach the recipient before any error detection and correction systems can even be applied.

For example, the Cat 5 cable must be plugged in. For another example, the receiving dish for messages from Mars must be turned on, working, and be pointed at Mars.

Once the connection through to the receiver is working, enough of the message must then get through without being garbled before detailed error detection and correction is even possible.

Inspired text has the same problem. If significant parts of the text were ever lost to history, then there would be no way to recover the contents later on.

Kings and Priests were interesting participants in solving this theoretical problem. Because their edits meant the text was important to endorsing themselves, they then went to war to defend the text. This is in part how this theoretical problem was satisfied.

Since kings are the fundamental opponents to the divine voice we should not expect their edited text to do a very good job of explaining divine character. Just through the study of contradictions and editors we can show the text of the Bible does not characterize god very well.

Another way this theoretical problem of delivery was satisfied was with the 'law of babel.' That law, first seen written in Daniel's day, required those editing kings to always add to inspired text. This principle was treated as common law, not just for the text itself, but for all other laws too. Read the stories surrounding Esther for a complete example.

As worked out, this meant that neither the common law, nor the inspired text, could ever be repealed. All any king could do was add to the canon.

So the interests of the editing kings are satisfied by their additions while the needs of eventual recovery are also satisfied.

The hardest part of the recovery effort becomes correctly telling what was added by editors and what was inspired.

On the other hand, by storing inspired text within the manuscripts defended by the force of arms and carried by kings, the inspired text was covertly spread around the world.

The inspired text became widely embedded and impossible to forever rid from the lives of people. Once that seeding process was over, all that would remain was for the markers that prove inspiration to be rediscovered and applied

Tied To 3D Systems

When we first started seeing the 3d system behind the letters themselves we started imagining that the entire manuscript must have a similar system running behind it.

The shapes of the 2d letters are fully error detectable and correctable given the principle of the design used to create all of the various drawn shapes of those letters.

The number of individual design constraints is massive. No line segment anywhere in the drawn forms of the letters can be changed without causing a breakage somewhere else in the 3d system.

But the principle behind that design is simple. It is based on a set of 2d projections from 3d objects. All 2d projections are shared on at least 2 different 3d objects. The alphabet's entire set of models tells important stories. They are themselves tied upwards into the meanings of words.

Ultimately, we are looking for something like the 3d system for proving inspiration. The problem is making the leap from that system up to the running text.

We have looked at several different possible systems of inspiration in our attempts to recover inspired text. Each step along the way gave us important lessons learned and moved us forward in our education on the problems of recovery.

The following sections review what we have looked at along this journey and what lessons we learned along the way.

Early Grids

We first had conviction that the Bible contained large additions in early 2011. We were driving the Oregon Coast south to visit Disneyland in California. At dinner one night we had a conversation and a Bible study. At the end of that meal, we were on the hunt for whole cloth additions, the type of additions added by kings and their priests.

As those additions served the purposes of kings and priests it was possible to study the problem from the level of a giant Bible study. The current BRB app's Filter tags are the ongoing result of that study.

Within weeks of that first inspiration, we also thought the pattern of inspiration must be related to the arrangement of letter strings. We thought the entire inspired text, when taken as 1 long string, must do something interesting when rearranged onto various fixed sized grids.

This was expressed at the time through the imagery of bricks in a wall or stones on a road.

For many months we searched the text for stories that might be giving the size and dimensions of such grids. This was ultimately a fruitless hunt.

Even if we were to find those dimensions, they would not indicate what constraint must be satisfied between letters on the grid. Remember, whatever system is in use it must be able to correct spelling errors. This means it must be able to pick 1 letter out of a field of 25 different letters at each cell in the grid.

Lessons Learned

  • The main lesson learned from those days was that this risked being complex and might take a long time to figure out. If we had known we'd be at this for over a decade, we probably would have given up.

  • We were also going to need prophetic help. In those early years we were not as aggressive on this final point as we should have been.

Acclension Declension

We called our first partially successful try at manuscript recovery the 'Acclension and Declension System.' That system was built on a convoluted table built from Psalms. It could identify and remove added vowels from many words.

The system could be run in software, but was easiest to understand as a set of small cards like those from a game.

The form it took was a deck of business cards, 25 such cards. The cards were set in portrait mode, with short side down. The letter for the card was drawn in the bottom 1/3rd of the card. There was a series of carefully spaced small boxes above each letter.

To use the cards, they were arranged on a table such that they spelled the word under test.

Words passed this system when it was possible to connect dots between cards all the way across the word. The dots rose across a word, so the term 'Acclension.' The dots seemed to fall across words, thus the term 'Declension.'

Words that failed could be tested again by changing the spelling. Typically this meant removing the cards for the letters thought to be added vowels. We were using rules of spelling changes taught us in a Hebrew class years before. In that class we were taught how to spot added vowels. We were now seeing something that worked in a more formal way.

Possibly inspired spellings were affirmed by finding a way to 'thread' cards by connecting dots above the letters of the word. Without a series of connectable dots, the word itself failed.

Lessons Learned

  • We gave up on Acclension and Declension because it could not span the gaps between words. Any real audit system would need to audit continuously across the entire manuscript without gaps.

  • The derivation of how those dots were organized was quite complicated. We cannot now even understand our limited notes on how we did it.

  • So how is anyone supposed to trust any claim that this system proves inspiration? We currently list all of Psalms as uninspired, so any table from that book is suspect.

  • This history now suggests another problem. The 3d system for the letters is complicated in detail, but the principle behind it is very, very simple.

    The 3d system is so simple that even a child can understand the principles. Though a child could not recover the letter shapes, they could easily understand what was going on. Children can use the 3d principles to correct their own penmanship, so it does have important application to running text.

    Any real inspired audit system for the text will be similarly simple to understand. We accept, of course, that it must be applied everywhere across the entire text, so across around 2,000,000 words, which is significant work.

Bible Codes

Bible Codes is a system that has been around for a long time. In that system the Hebrew text of the OT is considered 1 continuous series of letters, importantly the OT text is condensed, and used without any word gaps or other punctuation.

That resultant string of letters is then blocked at various counts of letters, called the 'skip distance.' That skip distance is open, and can be set to any convenient value.

The running text is then broken up into lines at that skip distance. Those lines are then aligned and run down a page. This blocking is effectively placing the text on arbitrarily sized Sudoku like game boards.

This blocking creates vertically aligned series of letters which are then scanned for interesting words. The actual Bible Code software often finds letter strings on the vertical, or crossing side, that are either known words or small phrases.

The more interesting case is when native Hebrew speakers note words that are names of interesting people and places around the globe. These words are typically not in any normal Hebrew lexicon.

This system was curious as a possible route to finding inspired text. Perhaps with some tweaks, we thought, it could generate running text and not just phrases. So we wrote extensive software to study this question.

The goal was to find continuous secondary text woven into the primary document. This is NOT like the Bible Code work which is generally happy with small words or names.

Our Changes

We made 2 fundamental changes. We included punctuation in the tests, and we accepted the lesson of added vowels. The spelling of words would need to be corrected if this was to form whole sentences.

If there was a solution, then it would be found by applying lots of computer time to try every possible spelling correction for every word.

This also means trying to solve the problem using many different skip lengths. We also looked at various weaving patterns. The text might have been inspired in a bi-directional form, known as boustrophedon, for example. So that had to be tested too.

The ultimate goal here was to use a rediscovered secondary document as proof of inspiration of the primary or widely known first document.

This is not simple, because the grid size and spelling of words is unknown. Software had to test many billions of cases.

In the end, this does not seem to be the solution path to proving inspiration.

Lessons Learned

  • Computer people call this a brute force solution. Brute force solutions usually signify a problem. The physical world usually has an elegant solution and this was not elegant.

  • We were applying modern high tech tools to this problem. This is a huge mistake.

  • Anyone who might come along later who wanted to verify the work would need to be similarly skilled in those same high tech tools. Use of high tech, or any other specialized tools, is a marker of a fundamental problem.

  • Use of skilled tools is limited to people trained in those tools. So an average reader of the text could never be expected to confirm the solution for themselves. The text generally likens this to a class of problems created by priesthoods.

    Any real inspired system of manuscript error detection and correction will be understandable by anyone. It will not require a priesthood. Even nit-wit parents should be able to pass that skill to their children.

  • In this attempt we first recognized the big problems involving the lexicon.

    Note how this works, even with Bible Codes. The discovery on the other side, or vertical side, of the grid is based on a scan of a lexicon. But the lexicon can only be formed from extant texts.

    There is a problem of circular reasoning built into this whole approach. Ideally, the lexicon only gets built once the inspired text is known to be inspired by some other means. Recovery must be possible without needing a lexicon.

  • This also hints that error detection and correction should be possible without knowing the inspired language itself, or at least not very well.

Qu Map

We spent considerable time working on the mysteries of what we now call the Qu Map. There is a link to that app off the main page.

Our first Qu Map classroom was Disneyland in Anaheim, California.

At first we were sent there because of a series of prophetic dreams. We later decided to use Disneyland as a surrogate for the temple in Jerusalem. We wanted to understand what it was like to travel regularly for the holidays.

For several years we were annual pass holders and spent all of our annual Biblical holidays at that park.

One particular day helps explain how much time we spent there. We were at the ticket booth updating our annual passes and were told there was a problem that we needed to fix at guest relations. We went over there to be out of the lines.

The woman at the counter in guest relations figured out the problem. We had moved and the addresses on our IDs were not the same as on file for the passes.

While updating our accounts to reflect our new address, she commented to us. Did we know, she asked, that this was the 100th day into the park on these passes?

Our trips there had been a staggering amount of time, trouble and treasure. We had gone because were were prophetically lead there. We had learned a ton of stuff for all that effort.

All of that travel was what might be called a 'prophetic foil.' These are situations where you think you are following Joshua for 1 reason, but he has a very different reason in the end.

Design Examples

The Qu Map is a 5x5 grid of the 25 Glyphs of the Paleo Alphabet.

The Paleo Alphabet itself placed deep meaning on each letter. There are 3d models that explain the objects behind each letter. These, in turn, give rise to word definitions based on the exact spelling of each word.

When applied to a map, it means there are characteristics at each location on the map that are also expressions of those same 3d models.

We were learning all of this as we were regularly visiting the park. We found the park was built on the meanings of the 3d systems that are behind the letters and the map.

The Qu Map has a particular concentric circular arrangement of those letters, starting with the dot punctuation character at the south side center position. The Dot is like sown seen.

At Disneyland this is the ticket booths. You are sowing your seed, money, when you enter the park. You would hope to reap a harvest, of fun, by the end of your time in the park.

The next glyph, Wa, the star, is east on the Qu Map. The map is fixed against compass directions on Earth. At Disneyland, this is the Star Tours Ride. The name of the ride is calling out the matched letter.

The rest of the alphabet continues around the outside of the map. See the Qu Map app for extensive details.

Eventually, at the final 25th glyph, the Qu Map series arrives at the center. At Disneyland, this is the central hub and the venue for closing fireworks.

Walt Disney appears to have been gripped with a prophetic vision for the original design of that park. Like Henry Ford, Bill Boeing, and Elon Musk in our generation, Walt Disney appears to have been what we call an 'Industrial Prophet.' Each is captured with a vision and the means to build something that changes the world in some interesting and important way.

Walt Disney only built out parts of the current park in his lifetime. After his death, others continued adding major and minor rides to the park. Those rides have been filling in the Qu Map grid in Disneyland for about 60 years. The new 'star wars land' in the northwest corner mostly finished the Qu Map at that park.

Qu Map At Scale

Importantly, the same Qu Map design is found on larger maps. The USA itself is built out using the same Qu Map design. The dot punctuation is New Orleans, and the Grain ports. The Wa is Pensacola and the naval bases there. The map continues around the USA, including Alaska and Hawaii, finally finishing near Memphis at the confluence of the Ohio and Mississippi rivers.

Built up regions of Earth appear to be following the Qu Map design at an even more massive scale. The Nile river in Africa mapping to the Mississippi in the USA. Cairo, in Egypt, likely mapping to the town Cairo at the Mississippi and Ohio confluence.

Places where the built up map are found appear to be marking places were Joshua's hand can be seen in the affairs of people on Earth.

Lessons Learned

  • This is the first system we found were the divine hand can be seen extensively in the affairs of men across the globe.

  • The Qu Map is the grid on which letters are drawn. So the Qu Map ties letters of the alphabet to locations within the drawn forms of letters. This opens all narrative in the text as possibly informing any inspired error detection and correction system.

    This was a super critical lesson that matters later to full manuscript recovery.

Bible In Genome

One of our long time blog subscribers had a career in various fields related to biology. She had nudged us towards looking at the Human Genome as a possible location for what would effectively be a vault copy of inspired scripture. In 2022, we eventually took her up on the challenge.

There are some basic facts about the Human Genome that you should know:

  • Only a small percentage of the Human Genome is known to function biologically. Some of the Human Genome might have a currently unknown biological function. The bulk of the Human Genome is called 'junk DNA' and has no recognizable biological purpose. If language is stored in human DNA, then that junk DNA would be the place to look.

  • The information density of DNA is substantially higher than any other known technology for storing information. The entire Human Genome, if used to just encode Bibles, would have room for around 500 copies.

  • Individual base pairs in DNA molecules fundamentally store 2 bits of binary information. This molecular structure would lend itself to some sort of binary encoding of running text. Base pairs form triples, suggesting the ideal encoding would be based on 6 bits of binary data. The Paleo alphabet needs less than 5 bits for encoding.

  • DNA has 12 distinct ways that textual information could be oriented atop the base pairs as found in DNA molecules. Each orientation must be checked.

History of the Sequencing Effort

It was evident by around 1970 that there was a need to learn the sequence of human DNA. Initially this was a very expensive, manual, and slow process.

By the mid 1990s the US Government started a project to get a complete sequence of the Human Genome. By 2003 this effort was declared finished, but in fact there were areas of the genome that technology of 2003 could not accurately sequence. The equipment needed to finish the sequence would take another 15+ years to develop.

A small group of researchers continued the project after government funding and political attention ended. In particular, they focused on perfecting the machines themselves so they could finish the task. The first complete sequence was published to the internet in early 2022. This was almost 20 years of additional work.

Reference copies of complete DNA sequences are particularly important. As sequencing of DNA remains very expensive, most research is done using differences against a known good reference DNA data set.

Sequence of Someone

Every single person on Earth is thought to have a different DNA sequence. Study of differences between people, and communities, is a common area of study.

The first sequencing effort used the DNA of a Mormon woman from Salt Lake City. She had been sick and in the hospital when her DNA was sampled and sent to a lab. She had given permission for cell cultures to be kept and used for research. Her medical history was also well known.

Mormons are an interesting community in a genetic sense. The limited DNA of the founding families is now shared across many different Mormon families. Few groups are so coherent. So any research of how DNA differs between family members is generally easier to do with Mormons.

There was a problem with this specific woman as the accidental choice for the subject of the first complete DNA sequence. That problem? You already know enough to guess. She was a woman, and not a man. So that first complete sequence did not cover all of the chromosomes in human DNA.

DNA from another man was eventually used to supplement the missing chromosome. But this means the first complete DNA sequence of a human is not of a specific human, but a combination of 2 different humans. Such is government funded research.

Current DNA sequencing efforts are focused on sequencing the DNA of people from different ethnic backgrounds from around the Earth. Differences in DNA from this sample set will shed light on how much DNA differences impact ethnic differences in people.

Simulated Sequencing

There are many popular DNA services that attempt to scan a customer's DNA and return some information about their genetic heritage.

These services are inexpensive because they do not fully sequence the sample sent in by the customer. Only certain very small areas of the DNA are needed to answer the real questions of ancestry that people have. So, only those small parts are actually sequenced via machine.

This example understates the serious problem of trust with DNA sequence data. The sequence of some creatures is filled in by software for over 99.9% of the sequence. In effect, software is regularly used to produce a DNA simulation, not a real DNA sequence.

This was done regularly in 2020 at the start of Covid. No biological samples were isolated well enough to do a formal DNA sequence of the Covid virus. By not having isolated cultured samples, no tests could be done to verify those samples caused Covid 19 symptoms.

When not flat out lies, claims to have sequenced Covid 19 were simply claims to software simulations of DNA sequences. We live in an empire of lies, and DNA sequencing data is at the forefront of those lies.

Evolutionary Implications

Hunting for a copy of scripture in the Human Genome has a bunch of implications.

If you believe in evolution, then this could not have happened. If it did somehow end up in human DNA, then evolution would teach it must have happened by chance. This is just like thinking that the Bible rose up from the dust by chance.

Bret Weinstein, a well known professor of biology, is on record saying that if scripture is ever found in human DNA, then evolution itself is proven false.

We agree.


The fundamental question is how could scripture ever have gotten inside human DNA? We don't know. We are not biologists.

But, we can convert that question to another question that we can answer.

When would scripture have ended up in human DNA?

Note importantly, the inspired text itself is written to predict and inform all of human history on Earth forward from the time of Adam and Eve. So the book itself is teaching that this history must have been known at the time of Adam and Eve.

Adam is said to have been created, or raised, from the dust of the Earth. The inspired text could have been inserted into his DNA at that time. Eve, created from Adam, would have picked up his DNA too, less of course 1 chromosome, or rib.

From this first couple it would be passed down through their children. It should have ended up inside the cells of everyone later in history.

If Adam and Eve are only refugees into this solar system, as suggested by the parable of the lost sheep, then that DNA based copy of scriptural history might not be in every single person currently on Earth.

So it may or may not be in the DNA of the Mormon woman who was sequenced for the Human Genome project, even if it is in the DNA of some people somewhere. So not finding anything in the 2022 downloadable copy of the Human Genome does not prove it is not in human DNA somewhere.

Sequencing Process

The Human Genome is read in modern DNA sequencing machines. Those machines go through a series of individual steps. First, the long DNA strands are broken down into shorter pieces. This turns the big problem into a bunch of smaller problems.

Then, those smaller fragments are grown into clusters of multiple copies of the same fragment. This makes the small fragment large enough to see by optical means.

Then, light is shown through those clusters. Each different type of base pair gives off a different color. So the DNA sequence is then read off by scanning the colors in the shadows produced by those fragments.

Software, both in the sequencing machine and then on servers, combines the raw data from those small sequences back into a single whole DNA sequence data file.

The entire process is done repeatedly, both on different machines and in different labs around the world. This provides redundancy and some assurance that the sequence has been correctly recovered.

Handwriting On The Wall

The literary purpose of the Book of Daniel involves his skill in language and literature. Daniel was the scribe to Nebuchadnezzar and likely invented Hebrew as we know it now.

The Book of Daniel includes a series of parables about how the text was transformed and hidden across history. Many of those parables include timelines that all generally end at or in the decades after the WWII era. Daniel also includes parables about how the era of empires and kings that Nebuchadnezzar began will eventually come to a close.

Daniel 5 contains a story that is normally taken as history, and not seen as an end-times parable. But, it is likely a parable about the fall of the world empires that follow Nebuchadnezzar. That fall is marked by the discovery of handwriting on a wall.

If you are unfamiliar with the story of the 'handwriting on the wall' you may want to read it again. That story centers around an event that has remarkable resemblance to the process of sequencing DNA. Here is the key verse:

5Suddenly the fingers of a human hand appeared and wrote on the plaster of the wall, near the lampstand in the royal palace. The king watched the hand as it wrote. 6His face turned pale and he was so frightened that his knees knocked together and his legs gave way. Daniel 5:5-6 (Daniel 5:5-6 NIV)

Taken as a parable, the fingers are the parallel duplicate strands of DNA. The lampstand is the sequencing machine that holds the lamp that shines light through the fingers. The wall is the place where the colors that represent DNA base pairs can be seen at scale.

As the story continues, the king is frightened. His experts are baffled. They cannot read the writing.

The DNA sequencing effort was done at government expense. It was surrounded by experts. They do not know what most of the DNA means. It has no biological function.

Daniel, who knows the ancient language, is called in. He knows the text and can read the message. He tells the king his kingdom is going to be given to another. It happens soon thereafter.

As a parable, how might this apply now?

Once the DNA sequence is read by an old prophet who knows the language, then the entire kingdom falls.

This was encouragement to keep going.

Woman's Bucket

The story of the Woman At The Well is a parable about how souls and bodies merge at conception. Full details are beyond our scope here, but the water in the bucket is the human body. The bucket is the human soul.

Research at the University of Virginia has shown that injuries at death often transfer to the next life. These bodily injuries often become birth marks or birth defects in the next life. As nothing but the soul transfers between lives, the soul is what is injured in these cases.

To use the terms of this parable, the bucket forms or shapes the water. The soul, the bucket, forms the shape of the body, made mostly of water.

The woman in that story has had many such trips to the well. Her soul, as the bucket, has drawn new bodies, the water, many times.

The woman herself is ultimately caught in a reincarnation loop. Her general soul issues involve husbands. This is why she keeps going around. She is being offered a way out of that loop.

That story importantly precedes the story of the Field Ripe For Harvest. That field contained a special cave, the main scroll vault used since Abraham's day. It was figuratively planted by previous generations by inspired writers.

Abraham, and many others, had hidden copies of the inspired text in that cave. Elijah visited that cave. Jeremiah purchased the same cave. Joshua's brother Joseph sold the cave when the region was being evacuated prior to the Roman invasion. In our day, there is nothing left to find there.

But, the parable of the Woman at the Well, sitting ahead of the opening of that field, suggests there might be a copy hidden in the water of the bucket, or the DNA suspended in water inside all human cells.

This parable is another source of encouragement to keep working on the problem of finding scripture in human DNA.

The Experiments

As early as 2003 the Human Genome sequencing project had been publicized as complete, but that was a lie. The tech of 2003 was unable to sequence the entire genome because of long repetitive sequences in the DNA itself.

In early 2022, the first complete sequence of the Human Genome was posted to the internet on Github. In mid 2022 we set out to test if the inspired text might be stored there.

We, of course, do not have inspired text to test against. We do not have a trustworthy lexicon. We will not have such a lexicon until after we have recovered the inspired text.

This time, at least, we understood the problem better. So hunting for a known text is not (yet) possible. Hunting for the encoding of Paleo letters to DNA codons is possible, so we set out looking for that.

There are serious complexities in DNA itself. Assume an encoding of the text that resembles how modern computers encode text, a very risky assumption, then there are still very many ways that text could be encoded in DNA.

Instead of looking for a text we do not have, we used a well known trick used since the 1700s to decode unknown scripts. The trick is to find well known and common names both across the text and in close proximity.

Names like Abraham, Isaac and Jacob will be spelled in roughly the same way no matter the script. We can treat codons of DNA like an unknown script and then apply that trick against DNA.

So the trick is to look for those names across the entire genome given all possible combinations of letter encodings, but also against all possible orientations of the raw data in the genome. The goal is to find common names at a rate higher than expected by chance alone. We are also looking for some of those names to occur together in clusters.

Lessons Learned

  • Looking for a 6 bit encoding system for the Paleo alphabet caused us to review certain aspects of the 3d system. That encoding seems to spring from 1 set of objects in that system. This was a major step towards the cipher system. This was a critical discovery that allowed us to move forward on other issues of manuscript recovery.

  • If the inspired manuscript is encoded in any way that a modern computer programmer would recognize then inspired text is not in human DNA.

    Of course some other encoding system might be used there instead. Modern computer .zip files, for example, would look like gibberish to this sort of scan even though zip files can easily encode massive amounts of text. The DNA might still be carrying encoded text in a way that similarly hides its contents.

  • It is also the case that there may be some intermediate level of encoding. Some aspect of the alphabet might have been used to carry running text in DNA that is both simple, but not like ASCII encoding at all.

    This might be related to some as yet not understood audit pattern. An actual encoding system could also be related to some aspect of the 3d system behind the alphabet.

    So our 2022 experiments were inconclusive.

  • More importantly, this entire study has the problem of special knowledge. Only domain experts in both computers and DNA could possibly hope to find the text. Those experts can never be trusted. So this is not a safe path to recovery.

  • It could be a path to confirmation. Especially if the inspired text was already recovered in some other way.

  • Our intent is to return later to the Human Genome once we have already recovered the text and built a trustworthy lexicon.

Historical By-Hand Recovery

The history of Joshua between when he was 12 years old and when he was 30 years old is not documented in the Bible. All we know for sure is that at some point he left his parent's house in Nazareth and went to Capernaum where he had is own house.

We started seeing clues in the text that suggest what he did at that house. We think he built, or rebuilt, a complete working copy of the Tabernacle items as setup by Moses and Joshua son of Nun.

Some of his disciples appear to have been called much earlier than normally thought. They helped him in this recovery effort. Take John the Baptist as an example.

John was Joshua's cousin. He had a miracle birth a few months ahead of Joshua. The families would have kept close. John was likely there through this entire process. He provides strong hints about this fact by his choice of words about Joshua at the Jordan.

Philip brings his friend Nathanael to Joshua. At that meeting there is a strange reference to the Fig Tree. This is a symbol or type used in other places. It was likely an actual object that readers who knew the process would immediately recognize. It was big, Nathanael had sat under it and studied it.

Philip is later named in the feeding of the 5000. That parable is tied to the systems of the manuscript. Philip is called by name in that parable because he knows that system and watched or helped it being used. He could interpret what was going on.

At least these men, maybe more, were involved in the by-hand recovery work that preceded public ministry as we know it. There may have been others involved too.

David's Fallen Tent

In Joshua's day, this was a copy of what the Acts 15 writers call David's fallen tent. Our goal is now to recover all the contents of that tent.

Once we knew this happened in the first century, we then knew the real process was very low tech and must have been a process that was taught and used by others.

The error detection and correction system was taught through low tech artifacts that are discussed in stories spread all across the text. To continue we now need to find and rebuild those artifacts.

Instead of wood and cast metal parts we are using mostly 3d printed plastic.

This is ultimately the theory of inspired manuscript recovery.

  • Rebuild David's fallen tent as called out as an end-of-the-age event in Acts 15.

  • Include every artifact. Details of each are scant and spread across the text as riddles. These riddles must be found and solved as a prophetic work project.

  • Once those artifacts are rebuilt, then use those artifacts in their natural low-tech way.

  • Recover the text mostly by hand, using computers only for book keeping.

This forms the heart of our current goals. To read more see our Goals article.