This blog starts with evidence that Joshua performed a by-hand recovery of inspired text before digging the vault near Sychar. It then covers our recent by-hand recovery of the commandments. With this success we can now recover the whole thing.
Field Ripe For Harvest
In previous blogs I've covered the story of Joshua's visit to the woman at the well. This was at Sychar, also known as Shechem. Joshua went there to open the field ripe for harvest and recover copies of the inspired writings.
We now understand Joshua was recovering those manuscripts to provide a second witness to documents that he had already manually recovered from extant copies of the text. Digging up the vault copy was an intentional double witness to the inspired manuscripts.
In order to have done a manuscript recovery Joshua must have built a copy of the Tabernacle items. Those items show how the systems of the text function. They are enough to reveal the audit systems as well as systems of manuscript multiplication. Let me give some evidence from the Gospel of John that he already had the inspired texts.
Philip And Nathanael (John 1, BRB)
The first story to consider is the interactions between Philip, Nathanael and Joshua. It begins at John 1:43. In this story Joshua calls Philip to follow him. Then there is interaction between Philip and Nathanael.
Philip makes the claim that the one written about by Moses and the prophets is the same Joshua who is the son of Joseph from Nazareth.
Philip's argument does not normally have a clear textual basis. In regular Bibles, Moses has a Joshua son of Nun, but there are no other important references to the NT Joshua.
But, if Philip had a recovered text, with Joshua as the divine name, then Philip is not making any sort of stretch of interpretation. Philip is only pointing out that the Joshua he has been reading about is the same person as Philip knows. Nathanael at least goes along, and when he does he visits Joshua.
In this interaction, possibly highly edited, Joshua makes a reference to Nathanael, that he saw him 'under the fig tree.' With that statement alone we get Nathanael's confession that Joshua is god.
This fig tree reference is also massive trouble in regular Bibles. That tree must always be taken as something personal between Joshua and Nathanael. Fig trees are common so as readers our question is what was Nathanael doing under that tree.
In all my years attending different churches I never heard anyone suggest why this was so important to Nathanael. Instead of focusing on Nathanael, we need to focus on that tree.
Fig Trees show up importantly in several stories. The first is in Judges 9:10. It is one of 4 trees referenced in parable form in that story. This story is told in a 'once upon a time' form. In previous blogs I have shown how this may be events around Noah. If so, then Nathanael may have a previous life memory of Mars and Joshua may be referencing that memory. This still may be OK, but there is a better internal answer from text.
Joshua tells another story of the fig tree starting in Matthew 21:10. He is on his way into Jerusalem. He sees a fig tree that only has leaves. He finds no fruit. He curses the tree. The tree withers. The tree will not produce any more.
By Matthew 21:21 Joshua tells his disciples that they can also curse the tree. He then continues the thought and says that by the same faith they will toss a mountain into the sea.
I have never heard of anyone tossing a mountain into the sea, nor has anyone else, so this is taken figuratively. But wait. There is a mountain in the Eden Map. These strange references are references to articles in the Tabernacle, also known as the Tent of Time. The mountain has a twin item, the 'fig tree' that uses the same geometry over again in an inverted way.
So the mountain and fig tree are the same. The mountain is tossed upside down to create the fig tree. Both are very important to the inspired language system.
So cursing the fig tree is indicating that the similar tree for the Hebrew language system of Jerusalem has no fruit on it. It is a sterile tree.
As the mountain and tree are easily understood models that are about the language system of the text, anyone can curse the tree or toss the mountain.
And, that language system curses the language system centered at Jerusalem.
Going back to Nathanael. He was seen sitting under 1 of those trees. Presumably the copy in Joshua's museum at or near his own house. Understanding that tree is what gives Nathanael the basis for his confession of faith.
This story of Philip and Nathanael is ahead of the field ripe for harvest, so it affirms the idea they had both tabernacle items and recovered text before that field was dug up. Another story ahead of digging the vault is the story of Nicodemus, it follows the story of Philip and Nathanael by 2 chapters.
Nicodemus (John 3, BRB)
John 2, which follows the calling of Philip and Nathanael is the story of the Feast at Cana. We believe this was the wake for Joseph. At that meeting officials were there to formally settle Joseph's estate. Joshua then became the responsible son for managing Joseph's house. He then had the keys to the field ripe for harvest.
Nicodemus is one of the special guests at that event. He comes to Joshua and asks several questions. Joshua famously rebukes him. Nicodemus is a teacher and should know the book, but Joshua says that he must be born again because his understanding is so bad.
In verse 10 Joshua says that we speak of what we know. He is using a plural here. He is not just speaking about what Joshua alone knows.
Who are the we that he is referencing?
Joshua had brought traveling companions, see John 2:2. They were his disciples. Philip and Nathanael and perhaps others. This entire group is speaking the same story. They are all speaking about the same truths that this leader does not know.
Joshua is rebuking Nicodemus using his own barely educated students. He is contrasting those students to the highly trained public teacher.
How were Joshua's students trained? They had read the hand recovered text and knew all sorts of stuff that was foreign to Nicodemus.
Woman At Well (John 4, BRB)
The link here is to John 4, where we find the story of the woman at the well. Late in this story Joshua discusses the field ripe for harvest where he will dig up the recovered text.
The well and the bucket mentioned in this story are referencing the 3d systems that are displayed on the mountain in the museum. Those objects in part build a well with a bucket, the setting for this encounter.
But the mountain itself gets tossed into the sea and generates the fig tree. The mountain and thus the fig tree is the path to more volumes of recovered text.
Joshua speaks to the woman on this point in an important way. He says that if she had asked, he would give her 'living waters.'
This is an important idiom. It is the term that indicates more volumes. When Isaac finds living waters in Gen. 26:19 he has found the same thing from the bits of the text that he had available in his day.
Joshua is speaking in a way that we as readers are to know that he already has those documents. He has generated them just as he recovered the base text. His disciples know them too. This is why Nicodemus was so roundly rebuked.
John At Jordan (Luke 3, BRB)
Another story ahead of the field ripe for harvest is the story of John the Baptist at the Jordan river. The link here is to Luke chapter 3 if you want to read it for yourself.
The first part of this story, Luke 3:4-6, involves a series of statements about the remodeling of the landscape. Paths will be made straight. Valleys will be filled and mountains leveled. Crooked and rough places will be repaired. Then all flesh will see the life of god.
Landscape remodeling appears to be a series of statements about hand-recovery of the text. Valleys filled would be places with missing text. Mountains leveled would be extra text. Crooked and rough would be letter level problems. Once this is done, then all flesh can see the life of god in the recovered text.
John knows this because he watched it happen. Joshua had recovered the text and John was there. Maybe John even helped with some of it.
Recovery of text involves using the Tabernacle items. The Acts 15 stories which we have covered here extensively discuss the recovery of David's Fallen Tent. That tent is a copy of the Tabernacle and all the items within.
That the writers of Acts 15 were in such a place is an interesting additional point. They held the items that Joshua himself had built. They knew what was going to be lost. But, before it was totally lost, we find Paul setting up more copies. Let me explain.
Acts 18:3 includes a reference to Paul sharing the same trade as Aquila and Priscilla. It calls them out as tent makers.
The normal use for this citation is to think of Paul as having a highly paid mobile skill so that he can travel with minimal tools and still provide for himself.
But, think of this story idiomatically. There is a single reference tent, the Tent of Time, popularly called the Tabernacle. That tent teaches how to read. It especially shows the systems of design used in the language's construction. Any reference to tent anywhere in inspired text is supposed to invoke an image of that reference tent. All readers should know it.
If Paul's profession is making that specific type of tent, then we can say much more about what he was doing when he traveled and set up assemblies.
He was traveling around in order to make local copies of all the articles in the Tent of Time. Paul would only need to carry the base document with him as he traveled. He only needed the 'Testimony of Joshua' itself. This is probably referenced in 2 Corinthians 4:7 and called a treasure in a jar of clay, or 'earthen vessel.'
That master copy could grow the other documents once the local fellowship had the tabernacles articles and knew how to use them. This would be a strong basis of faith because it would be faith based on the strange supernatural nature of the written inspired text.
Acts 17:16-21 discusses a time when Paul was in Athens waiting for his traveling companions. That paragraph focuses on how his audience there wanted to hear something new.
Of course we normally read this as being about Joshua and his personal resurrection. But the resurrection itself is idiomatic for the raising of the dead text. Read idiomatically, Paul is preaching from the additional volumes. Those volumes contain something new. Those volumes are what got him into trouble with local authorities.
Tulsa is a prophetic Jerusalem, and so a venue for a prophetic resurrection. Ryan and I have been in Tulsa since October. We have been there following prophetic leading to visit to start the process of recovering of the text. We were interested in borrowing a specific downstairs bedroom that had been called out to us years ago as the 'garden tomb' where the resurrection would happen.
The first couple months were filled with intense revelation on the Eden Map. From there we shifted into a prophetic season where we have been understanding the articles that go into the Tent of Time. Starting at the same time as the Asbury revival, a prophetic gusher opened up to us. The date for this blog is day 39 in this ongoing prophetic season. I have been counting the days in my diary watching to see when this season might stop. It has not stopped so far.
Part of that prophetic flow has been detailed instructions on the tabernacle items that explain the audit system that all text must pass to be considered inspired. One of the items that matters to this is the shepherd's staff.
That staff still needs 3d modeling. It is complex because of the need for strength across its length. Almost on a lark we set out to see if the commandments would fit in 1 run. So we drew the audit pattern that would normally be carved into the staff. We used inkscape, a 2d drawing program. Then we started fiddling with the text of the commandments to see if they would audit.
The bottom half of the commandments were easy. Those are short and easily passed the audit. As we moved to the top we had trouble. We stopped for the night, then tried again in the morning. This time on the hunch that the entire set was originally all short, we tried auditing short forms of each commandment, starting at the very top of the section. That worked. We had recovered our first string of inspired text.
In the end the commandments read simply, "I am Joshua god. Don't have gods outside me. Don't make any image. Don't bow and serve. Don't swear. Remember Sabbath. Honor father and mother. Don't kill. Don't (commit) adultery. Don't steal. Don't testify a testimony falsely. Don't covet."
The entire string fits perfectly at 1" scale on a 5 cubit shepherd's staff. This is 1 row in 1 robe of letters. This is 1/2400th of the monument face.
What I have just reported to you here in this blog is my prophetic version of Mary's report to the fellowship that Joshua was risen.
We will see the whole thing in perfect health at a later time and in the right place. Though resurrected in Jerusalem he was seen in other places, like on the road to Emmaus and in Galilee.
If you want to run to the tomb to see what I am reporting, you can. Go look up Exodus 20 in the BRB and see it mostly empty, but with a few words lying there.
Lessons Of Recovery
The most important thing we saw was the OT divine name. It is Joshua. This point is what Philip was making to Nathanael. This name is spelled in the 3 letter form that we expected, YoShaOo. The texts passed by history have an additional Ve before the Oo. That Ve is not inspired.
We had to substitute this name for the MoReYo term found in the Aramaic/Syriac texts that we have been passed by history.
Only the Aramaic version of the commandments pass the audit. We were monitoring the Hebrew as we were doing this work. The Hebrew spellings of the key vocabulary words in the commandments fail the audit system. We now have hard evidence that the Hebrew OT is not inspired. The Hebrew is a translation, as some believe, from Aramaic.
We need many more things for this to go faster. We are handicapped by not really knowing the language. We will build a high quality lexicon to help. We need a full and accurate font kerning table for the Paleo alphabet. That will take experiments in other areas of recovered text to fully verify.
Once we knew what we were doing, this took us about 2 full work days using Inkscape as our tool. It is a visual process. If we can get our pace up to, say, 10 per day, it is still nearly a year of work to recover the entire text as we know it now.
In Joshua's day the starting point was about 1/2 of the text we have now. If not using any god powers, by hand, this might have taken Joshua and perhaps his early disciples like Philip a year to complete.
We are adjusting our work to begin a full recovery. We have looked at recovery several times over the past 10 years. Over those years we learned many lessons on what not to do in terms of the computerization of this problem.
I expect this to be a mostly manual process, but with helpful software to speed it along. Software will manage the inbound Bible files and the outbound Testimony files. Software will manage the lexicon, the edit process and track in the final files exactly where the inspired text was found in the Bible.
All of this will be connected through to new and updated apps on our website. This was a manual process 2000 years ago and it needs to be a similarly manual process now.
Ryan has already shifted from dealing with the English BRB to dealing with our Paleo bible texts. There is still much cleanup to do there, including aligning different inbound texts with standard English versification.
I expect Ryan will be doing most of the recovery work. He has much of the Bible in his head already. I believe he has been prepared by Joshua for this very important task. It is something that more than 1 person could work on, we will see if there are more hands for this work.
I will be trying to keep ahead of him in terms of the software tooling to speed this along. I must also turn to a bunch more 3d work.
Over our First Fruits trip we were shown the Tent of Time items that eventually explain the mechanisms of manuscript multiplication. The parable of the feeding of the 5000 is built upon this process.
The inspired text has a simple audit system that any shepherd can learn and use to check their own copy of the text. The staff can be held up under any run of letters on the monument to allow verification there. These tasks are easy. We think the text is more constrained than the staff demands. That constraint is that there are secondary writings built within the text we know.
At this point I only understand the path into this multiplication problem. There are problems related to symmetry in the Eden map that must be fixed and then another round of 3d models need to be designed that explain the whole process.
I must go understand this and then attempt to apply that learning to the text coming out of Ryan's work. A few points in our recovery of the commandments are still disputable. So we cannot yet carve them in stone. These points will clear when we can multiply that text.
Joshua not only recovered the text by hand, he also recovered it from the vault. This provided a double witness to the base text.
I expect we will do the same here. Just as in his day, the manual recovery must come first. Once that is done I will look again at the Human Genome. I still believe this is the modern vault where it will be found.
BUT, I'm learning the text and its very strange design systems. I do not believe the text is encoded in a way that would make sense to any modern computer programmer.
There is a step in the general process of manuscript handling that the text prophetically calls 'weaning.' A genome based copy is probably not weaned and will need to go through weaning. If you don't know the Tabernacle and its detailed systems you cannot just go dig up the text. The vault copy is well guarded.
We have many friends in Oklahoma who have been tracking this work. We made our first friend in Oklahoma over 20 years ago. Oklahoma is special because it hosts America's prophetic Jerusalem.
To all of our friends, but especially to those in Oklahoma, your wait has not been in vain. The resurrected form of the text came out of the ground like a gusher in Tulsa, Oklahoma. We are witnesses.
We have been called back to the west coast and are traveling this weekend. The full resurrected form must be seen somewhere else. We are not sure where that will be. For us it is still many months away.
Tent Of Time
Wherever we are, we will work on the items I have mentioned above. The textual recovery only needs a peaceful place, our laptops and our portable server briefcase. 3d design work can also happen pretty much everywhere.
The 3d models are different. Some of them we carry with us in the car. Most of those need reprinting to current designs, which is no problem.
But we will need a place to build out the larger Tent of Time and all of its exhibits. Somewhere there needs to be a big plastic fig tree that future Nathanael's can sit under and have their own encounters with Joshua.
We have been told prophetically that we will be provided such a place.
For you intercessors reading this blog, please pray with us that we 1) complete the recovery, 2) Understand how to feed the 5000 through manuscript multiplication, 3) find the path to the correct place where all of this gets displayed, and 4) have enough provision to see this work through to completion.
Much more Later,