Paleo.In Rebuild

This blog explains this week's rewrite of Paleo.In. Before that, notes on changes to some important settings in the BRB and TT family of apps. Finally a short headline review.

Tabernacles Lessons

Ryan and I continue to finish up our end-to-end read of the TT app that we began over Tabernacles. This week we have made it through John.

The main lesson for this season is an understanding of the nature of Joshua. The "Lion's Den" lesson is that Joshua is not a god. Gods are imaginary constructs of men. Joshua is not one of those.

Any text that suggests otherwise is an edit by one of the 6 villain editors.

Because this is such a fundamental lesson, it is taking us time to work through the text and to estimate what the editors did to make this fact not self evident in the historical text as passed by history.

This is particularly strange once we get to the New Testament. We are currently slowly working through that difficult problem.

As I have explained some in recent blogs, it looks like there must have been a subculture that correctly remembered Joshua. The community of minor prophets is an example. That there would even be an inspired copy of books like Esther and Tobit is more evidence of some sort of functioning faith communities and perhaps widespread cultural memory of the text before the editors did their work.

Calling Philip and Nathanael

For readers here to consider this problem, the link here is to John 1:43 in the BRB. This is the story of the calling of Philip and Nathanael.

The key verse is 1:45. Let me quote Philip from that passage here in full: "He who is written about by Moses, in the law, and by the prophets, we have found is Joshua, the son of Joseph, from Nazareth."

If you have all your quote links related Settings turn on, you will see this is structured as a quote, but there is no known cite that we, as readers of the Bible, can go find. The BRB marks this up as "Quote Unknown."

Presumably this actually exists in inspired scripture once inspired references to Joshua are restored.

But, think carefully about the problem presented by this passage. How could Philip have ever said this unless he had actually read that passage. And, Nathanael must have also read that passage. That interaction between those 2 men makes no sense otherwise.

The point of Philip's argument is based on an assumed shared textual understanding between them. He is adding only that they have now found that Joshua in the flesh. Philip's claim is that their Joshua is the Joshua referenced in that otherwise unknown quote.

This has always been a strange interpretive problem for readers of that story. The BRB flags this problem by using a "Quote Unknown" markup.

This story is a proof text for the idea that certain people in the New Testament had copies of a version of the Old Testament that is unknown to us today.

I would now add, those copies must have existed before the start of the timeline of the New Testament. More on this below. Whatever text Philip and Nathanael already share, that public Old Testament text, it did not survive to our day.

This is why we find strange places like this. In the BRB, these are marked as "Quote Unknown." (I see why Ryan has asked for code to catalog those references.)

Cultural Memory

So this is also a proof text that in first century there was a cultural memory of Joshua. That cultural memory had a textual memory. Philip could quote some amount of Scripture and Nathanael knew it by memory. This is just like what we are now already suspecting was going on in the days of the Old Testament.

But note, Philip and Nathanael were not the only ones who shared this cultural memory. They are only showing us a hint to a bigger group of people who were aware of Joshua in the Old Testament.

This point is fundamental for understanding what Ananias was doing when he edited the inspired New Testament to conform to his copy of the Jewish Old Testament. Ananias had to scrub out any such references to Joshua that are only found in the inspired Old Testament.

Since Ananias' Old Testament was already scrubbed of the name Joshua, his editing of the New Testament had to be severe. New Testament references to the Old Testament Joshua had to be changed.

Ananias did this by erasing many otherwise inspired references to the Old Testament Joshua. Those inspired references are now flat out hidden to us in the extant copies of the New Testament. We also have NO familiarity with even this class of Old Testament reference as found in the New Testament. Euphemisms, like "Son of Man" from Daniel, after the Lion's Den, might be inspired in the NT, or else they may have been used to cover direct references to OT Joshua.

Ananias did not always change these references. He left a few behind, like the story of Philip and Nathanael. Ananias appears to have had no easy 1 or 2 word edit that would fix the interaction between those men.

More

As we are reading through the New Testament we are finding stories that were likely written against that now unknown Old Testament manuscript. Some of the other people involved in key New Testament narrative must, at times, have had some familiarity with those inspired stories.

The most interesting of these is perhaps the angel encounters with Mariam. She seems to know of Joshua. She is more concerned about the mechanics of the birth of Joshua. She does not ask the obvious question, "Who is Joshua?" So who was it that sent his angel?

Similar problems and questions and issues of manuscript recovery are spread out all across the New Testament text. This is mind-bendingly strange.

More examples in future blogs as we get the text cleaned up.

Changes In BRB Markup

This week's update to the BRB, so the other scripture apps as well, includes a couple of important changes in the Keyword and Voice settings.

The keywords setting now splits out "Joshua" highlighting from "God" highlighting. This is just in keeping with what we learned at Tabernacles. God references will be to imaginary gods. Joshua gets his own highlight.

The Voice settings are also now changed. Joshua gets his own solid green color for text that is attributed to him. Light green is used when some god appears to be speaking. Maybe the colors should be further apart on the color spectrum, but we are running out of colors that work together on screen. Gods are in some sense an invented replacement for Joshua.

Note there is also a conceptual change in how this is being rendered. Previously, light green was used to mark indirection. So if someone said "Joshua said..." the green for Joshua would go light. Now, only dark green text marks any text that is attributed to Joshua for any reason, by anyone.

Text attributed to the various gods is now light green. Across the majority of the text, this is a better way to mark up the text.

But, beware, without now marking indirection, this makes dark green show up in a few places where false prophets are speaking in Joshua's name. Remember Micah.

It now falls to the reader to determine if the dark green should be trusted. This is just as it is in life, and is good practice for readers of the text. If someone says Joshua said, the reader or listener must gauge if this is true or not.

These changes in BRB markup are rolling out now. Expect a few weeks before all passages have been correctly remarked to conform to this new convention. So just beware, this is an ongoing change in the various scripture apps.

Trip Report

A week ago Wednesday, Ryan and I traveled to Eastern Washington for lunch with our friends there. We left home very early so we could make a stop in Portland, Oregon, to look at some Slate pickup trucks that were being shown off there. I have been without my own wheels since Covid and I wanted to sit in an actual Slate truck. Headroom and legroom were fine. Delivery is still a year out. I am not in any hurry. We then headed east along the Columbia River for lunch.

A few days earlier I had some interaction over the phone with some friends from a fellowship in Vancouver, Washington. I had mentioned that Ryan and I were headed east. But after some conversation, I declined an invitation to stop in Vancouver on this same trip. The day was already full.

After we left our scheduled lunch meeting in Eastern Washington, I found a missed text message with an invite to visit one of the families from that Vancouver fellowship. They live not far from our other friends in eastern Washington. We had some time, so we accepted the invitation and spent dinner with them.

This was the first time since before Covid, since even 2019, when we have spent face-to-face time with anyone not already familiar with our work. We have learned a ton of things since those days. In our time with them, we had a pair of interesting conversations.

2 Conversations

We got there ahead of dinner, but before the whole family was there. We had a short meeting with one of the adult sons before dinner. We then had the expected long meeting after dinner when everyone was there and we could more properly explain the details and principles of our manuscript recovery work.

We have no idea if we will be invited back. But our time there triggered a very long and detailed conversation on our way home about what worked and what did not work earlier in the day.

On the drive home, we worked out guiding principles for a set of changes that we needed to make to our main Paleo.In website. This also clearly set certain work priorities as well as how to approach various topics in the future. Those updates to Paleo.In go live as this blog goes out. Work priorities will shift in another few weeks after we finish work left over from Tabernacles.

Let me explain the principles behind the changes we are making.

Our Mission

The first frame of reference was not actually the family that we met. But the idea of any future fellowship using our work as the basis for their meetings. What, exactly, does any such fellowship actually require from us in order to be successful before Joshua?

The answer to this question breaks down into certain principles and then certain artifacts. The Apostle Paul gives some insight to this problem. He traveled around setting up fellowships. Once they were running, he would remain as friends. He would check on them. But they were mostly independent.

Any other relationship creates a single point of failure. So if Ryan and I ever do anything similar we must not set ourselves up as a point of failure for others. If fellowships are not independent, then groups of them will ultimately recreate troubling systems like church denominations.

So this frames our own work. We should not think of ourselves as running fellowships. Not personally, not online. Our job is to set them up, or more likely, to help others set up Paleo Language based fellowships. We need to supply what they need, then leave. We can remain friends.

It was also evident, by the way, that this group probably already does a fine job of running their own fellowship. We don't need to be involved in that. We just need to keep out of their way.

No current fellowship has all of the inspired documents. Nor do any have the inspired exhibits. This will be true of all existing fellowships. It will be true for a long time. We have lots of work ahead.

Authority

Ultimately, the authority of any teacher or group to speak for Joshua lies in the evidence they claim as providing them with authority.

That evidence ultimately lives in the 3d model systems and in the inspired text. It does NOT live in group connections, personal credentials, nor any other similar system. Authority can be gained with time, but that time must be spent learning about Joshua and the systems that prove the inspired writings.

Our own gifting is in our ability to eventually provide the tools where members of fellowships can grow in their own authority. We do that when we provide the 3d models and the text. This should be our point of contact with anyone involved in our work. This is what Paul was doing.

Hindrances

In reviewing our brief before dinner meeting, we had flash backs to many longer such meetings we have had in the past. Ryan and I sat in the car on the drive home and could recount many such earlier meetings.

These were especially common in Oregon when we lived there. These meetings also happened many times in Colorado. When we left Colorado in 2019 we stopped having any discussions about the Bible. We stopped these meetings for good reasons.

People who do not know us, nor our work, nor our calling, assume we are like everyone else. They want to have a Bible study. In our own past, so did we. We wanted discussion of stories in the Bible.

This can be friendly, or unfriendly. Baptists with Presbyterians have unfriendly discussions, as an example. Ultimately these are called "sword fights" for a good reason. The Bible is the sword. Fights over interpretation are sword fights. These fights test scriptural knowledge.

For new learners, this is helpful as it is a test proficiency with the text. Those who know the text have sword fights with new learners in order to test their knowledge and figure out how to help someone grow.

But for those who have been around for awhile, learned in their denominational details, and learned in the limits of the text, sword fights never produce good fruit.

Our current work is on the problem of how only some parts of the Bible are actually inspired. So one topic for us is the work of the villains. Our other topic is how to fix this problem. The 3d models and audit proving the inspired canon are our subject for that fix.

So the basic logic we use in these conversations does not fit what most people assume about the text. We reach unusual conclusions for valid, but very unusual reasons. Our arguments start with the problem of the inspired text itself. Like a scene from the first Indian Jones movie, we bring a gun to the sword fight.

In these sorts of conversations, we risk making life difficult for others because to match us requires a massive Bible study. Nobody else knows the villains, so we get into useless sword fights. Now get to the point of otherwise unsolvable problems pretty fast. Bang!

Helps

On the other hand, after dinner, we started talking about the Paleo alphabet and 3d models. The alphabet itself was well known to our audience as the "Paleo Hebrew" alphabet.

Letter definitions and drawn forms were ideas they already knew. Even without actual models in hand, we could easily explain the conceptual process of finding drawn forms and inspired definitions for those letters. Our audience could easily follow that story.

From there, we could spell out manuscript level problems and the steps to recovery. Particularly interesting is just the problem of picking the likely historical text from which recovery to the inspired form is theoretically possible. The relative merits of Greek vs. Hebrew vs. Aramaic were also easy to explain.

We could also spell out the need for our work by introducing the overall concept of the editors. This does not depend on specific Bible studies. But it does introduce the problem of messed up texts. Everyone who has ever looked at original language manuscripts knows there are problems. Nobody knows how to solve those problems. Nobody knows where they come from. Nobody knows the intentional nature of the edits. We do. We have earned our authority for explaining and answering this problem.

Along this track of discussion, Ryan and I were easily understood. We were only limited by time in order to explain the whole work. This part of the evening seemed to go pretty well.

Having ready access to at least some of the 3d models would have helped considerably. The silver set matches the early prophetic dreams. The copper set provides letter definitions. Those 2 sets are the most important when introducing our work.

Reflection

We had a long discussion on the drive home. What worked? What did not?

Ultimately, we could see that we were moving up the 7 layers of interpretation. By starting at the bottom, with historical manuscripts, alphabet drawn forms and basic 3d models we were at layer 1.

With enough time, we could easily move up through the other layers.

Moving through layers of interpretation is how to avoid swords fights. Each layer easily builds on the earlier layers.

We were starting on layer 1, and we were obviously understood. The natural progression of such a lesson plan is to start at layer one and then move up from there.

By layer 4, the BRB and TT apps start to kick in. By the time we get to that point, we have moved through audit, so everyone should know we are not using the same text. So there is little room to argue over doctrine and authority or detailed interpretation.

Redefining Our Mission

So by the time we were home we had begun to redefine our mission. We are ultimately out to provide all the artifacts that are needed by the leaders of any fellowship in order for them to correctly lead the members of their fellowship into a walk with Joshua.

The key change here is the indirection. We don't have to do this ourselves. We need to enable others to do this successfully, on their own, without our help.

The natural gifting for their work is similar to raising families. Neither Ryan nor I have done this. Anyone running such a fellowship has way more complex problems than we do. Our problems are mostly technical and prophetic. Our problems are not normally social, nor generational.

The Apostle Paul, himself, was also generally looking for people who could eventually lead local fellowships. It wasn't particularly Paul's permanent place.

What such fellowship leaders currently lack are 1) Access to the inspired texts and 2) Access to the exhibits that prove that text is inspired.

Those things we can eventually, easily, supply. We can also help get any such group started on their own journey by explaining trouble with the Bible.

Paleo.In

The link here is to our main Paleo.In website. This is our hub. This is normally where someone starts in order to understand our work.

This website was essentially, completely, rewritten this week. The changes were made in order to fix a bunch of problems that had become self evident in our conversation on our way home.

The first rule of thumb was that there can be nothing that would be frightening to new visitors. No sword fights. No theological debates. No picking fights with anyone who comes from some extant branch of Christianity.

There are hard truths in our work. Like the Bible is broken. We cannot avoid hard truths. But, there is no reason to start sword fights over topics that do not matter.

To completely reach this goal, Paleo.In lost all secondary pages except blog related pages. The blog history is still probably frightening to some. I will be more careful in future blog posts to not pick unnecessary fights. The blog might eventually need to move to a charts app. Old blogs may need to be archived. We will work out blog problems in the future.

Focus On Apps

The second rule of thumb was to focus on the apps that are available from Paleo.In. Ryan and I agreed to drop all of the mostly unused apps and to focus only on apps that make sense for use by members of Paleo based fellowships and leaders of those same fellowships.

This means dropping old apps like the "Bible In Genome." It also means dropping Greek specific apps. It also means combining all 3d work onto EzekielsBones.org.

As part of this we agreed to sort the apps with student focused apps at the top of the list. So a leader of a fellowship can tell someone to visit the website and load the "Essential Apps" and no more. These, of course, must come first.

After that initial set comes other apps and websites that are still important to us and to our work. The next important section deals with Bibles. After that comes the big time related websites. Finally the 3d and Paleo Bible work comes at the end.

Introduction and Writing Style

At some point in our meetings someone asked what we do. We had been strangely introduced as "Bible Translators." Though perhaps technically correct, it sounds strange since our work is more complex than the work translators normally carry out.

Out of my mouth came, "We are digitally remastering the Bible. They do this with old movies. Why not with an old book?"

This answer got smiles, and nods. My listeners immediately understood the scope of work. It drove interesting questions. So I am now trying that same pick up line as the top of the Paleo.In website.

Biographies

After that strange opening, I do give our biographies. To Ryan and I this is an unnatural place to start. Our cultural heritage is more like hermits in the rain forest of western Oregon. Nobody out in public just introduces themselves there. (Ok, maybe the "chainsaw wood carvers" introduce themselves, but before you even pull off the road, you have seen their latest Big Foot carving.)

But still, we need a personal introduction, as was done for us at dinner. We might as well introduce ourselves at the start of the story on Paleo.In. I have tried to be kind and brief for each of us.

Order Of Material

After that unnatural introduction, the front of Paleo.In now sorts our list of apps and websites into useful groups. Anyone reading along should be able to learn our history and work. I have woven that story into the introductions for the apps that express various aspects of the project.

Readers of this blog may want to read through that material. If I have overlooked something that you see as important, please let me know.

Blog

The blog and a few pinned blog links are still at the bottom.

Besides the blogs, blog index, blog sign up and feedback, there are NO additional pages on Paleo.In any more. None of the pages that were there seem to matter any more. We don't need to have any sword fights.

Beside the obvious problems with the Bible, we do not need to pick any other fights. Paleo.In is an imaginary layer 0, below the first layer in the 7 layers of interpretation.

Classroom

Note that I have not linked the old Classroom app. Videos there were recorded at the start of Covid in 2020. If we need, we can do something like that again, but this would ONLY be for introducing the exhibits and for understanding features inside the various apps.

We would NOT want to compete with leaders of fellowships who need to be our main audience. We would not normally want any sort of Bible Study like topics except when those deal with inspiration.

Match Dates

We remain in our current replay of the king with leprosy through about 2026-10-02. As I have explained in previous blogs, this is a time when the king had leprosy and lived in seclusion.

Parallel plagues related stories suggests to watch for nuclear related headlines, so any headlines out of Japan, where nukes were last used. For this week, at least, Japan appears quiet. They are not yet overtly selling bonds. The US Treasury is just loaning Japan money against their bonds. Tricky.

So far, in this time window, nobody is known to have used a nuke. But, there are a bunch of nuclear related headlines if you know where to look.

Global Nuclear Risks

The link here is to a long and detailed article on UNZ by Ron Unz, the editor in chief of that website.

His article was triggered by the same X post that I cited last week where we learned that Trump is considering nuking Iran. Ron Unz takes that post and fills in a river of important details. This was NOT the first time that Trump has considered using nukes against Iran since the start of the war on February 28, 2026.

But, it gets very, very much worse, as Unz explains. He cites a long list of important sources that suggests the USA is changing its nuclear doctrine in order to allow the use of nukes as first strike weapons. This is being done in part by a civilian, a hedge fund manager, probably Zionist, from New York, who has taken over daily rule of the Pentagon. Hegseth carries the official pen, but Hegseth is otherwise just a performer. This is why Hegseth cannot speak clearly to congress. Hegseth may have no idea what is going on.

On top of that, as Unz explains, the many well reported staff changes at the Pentagon are being carried out in order to remove any high ranking Pentagon official who would NOT follow orders if Trump ordered them to use nukes against anyone, Iran, Russia, or China. (I would add prophetically, they are removing military leaders who would refuse orders to nuke places like South Dakota.)

Even if there are no public uses of nuclear weapons by our next prophetic date, the plague of boils caused by ashes from a furnace is now being set in place. Anyone in the Pentagon who would stop the use of nukes is being removed now. This appears to be a key step for the world to burn down in World War III.

This is being done because the Zionists no longer think they can use conventional warfare, and banking, to finish conquering the world. We can now understand the problem for them that ultimately triggers that final war.

Watch Dates

Next known date is 2026-10-02. We will return to it later.

Shop Work

This week had essentially no normal shop work. Rewriting Paleo.In took most of my time. Ryan is working on updating the tag system in the BRB and related apps. We are also doing afternoon reads of New Testament passages to complete the work started at Tabernacles.

Headline Review

The following caught my attention this week.

Ratcliffe To Russia

This link is a followup to last week's headline of Ratcliffe to Russia. Many, as linked here, are suggesting Ratcliffe was summoned to Moscow. This matches Russia's advances around Kiev. The idea that Russia would conquer Ukraine is probably contributing to Zionists adjusting their systems so they can use nukes. Russia might be saying back, don't touch that bomb.

Russians On Nuke Fear

The link here is to another, long form, article on RT dealing with the eventual use of nuclear weapons. This is written by a Russian official. It was probably inspired by the same X post that inspired Ron Unz. Same general idea as Run Unz, but from the Russian side. Nobody seems to care about the hell fire that is nuclear weapons.

Nuclear Safeguards Gone

This link is to a Youtube video with more on the topic of the removal of nuclear safeguards. These changes allow western Zionists to finish conquering the world. They will mostly burn it down instead.

Iran Discussing US Nukes

This link cites Iranian sources warning Trump not to use nukes. As they suggest, this would not bring victory over Iran, but instead would start World War III.

Saudi's Nuke Iran

And, more. Saudi media is discussing nuking Tehran. Like US media, these are Zionist shills, explaining their plan. The Zionist/Masonic religion demands stating publicly, ahead of time, what they will do.

The 20 Gone So Far

This is a link to a Middle East Spectator post on Telegram with the pics of 20 top Pentagon officials that have been removed by Hegseth's handler. Presumably, these men were found out, and would not use nukes as a first strike weapon. These men are presumably lawful. Not at all useful to Zionists.

Century Long Oil Grab

This link is to a post on Telegram with brief details of how the Pentagon is grabbing Venezuela's oil. Once you know there is a hedge fund manager effectively privatizing the Pentagon this makes some sense.

Major refiners appear unwilling or unable to invest in the equipment needed to refine this very low grade oil. It is best used, nearly as is, for asphalt pavement.

SpaceX in LA

This is a link to a post on X with the map of the property SpaceX is acquiring for their new space port. A followup to a link in last week's blog.

Abraham Lincoln In Thailand

This link is to a post on telegram with photos of the Abraham Lincoln as it arrived in port in Thailand. The important detail is the surprising amount of rust as seen in the photos. Apparently, not even any of the 3 airplane lifts were still in working order. This is why the airplanes are on top. It is a tired old hulk.

Cybercab

This week, Tesla has started running their new Cybercab vehicles in their robotaxi services. This is an impressive technical advance. This link is to a Lord Bebo post on Telegram with a slightly edited Tesla commercial. I like the Biblical cite.

The only problem with this service is how it is tied to the customer's phone. This means it is tied to identity. Grok is now also zio-mad. Anyone publicly crossing zionists risks death by taxi in these contraptions. Best to stay away.

No link, but Dr-Know-It-All was using Tesla full self driving in his Tesla passenger car. (Same basic system as the taxi.) He received a ticket for doing 18 over the speed limit in a school zone. He got the ticket, not Tesla FSD.

There is a certain assumption that your AI driver is taking legal responsibility for driving you around. Not so. Another mad AI product. Best to stay away. Just wait until a taxi passenger gets the ticket for what looks to be illegal driving by these machines.

Lawyers will have fun with this. Most new industries take decades for case law to be established. That has not happened yet with FSD. One of the strange risks of using these products is to be tied up in court for years as their case moves to the US Supreme Court. No doubt, this will eventually happen to a few people.

Ukraine Collapse

This post is for the record to note we are in a season when Ukraine, as functioning society, appears to be collapsing. This particular post notes how Ukrainian military themselves may be attacking munitions factories. This strange point is in order to free employees for conscription into the army. Strange times. Modern Nazi logic is strange. Ukraine may be on the verge of a civil war.

More Later,

Phil