Paleo.In

Ezra

Phil Stone — Fri, 11 Sep 2026 20:53:55 GMT

This blog looks at Ezra's god scam. Before that technical changes in the BRB. Also, names updates to the Paleo Bible. Finally, a headline review, with what might be our expected use of a nuke.

BRB

The main technical change in the BRB app this week is the removal of the "Notes Mode" setting and content. Our goal for all of our apps is to keep our content out of the running flow of Bible texts. Asides will be used for such notes in the future. This change fixes presentation problems on small screens. Notes will eventually return as asides.

Since Tabernacles, Ryan has been continuing to update the BRB text with our latest understanding on the textual problems between Joshua and the various gods. We will look at one such example from Ezra below.

This week Ryan got a chance to finally start looking at this problem in the New Testament. With this week's update he is introducing an elegant fix to a strange problem. But this change is a little jarring. Let me explain.

Recovering Joshua

Perhaps the best way to think about the "divine name" problem is that the editors, so the 6 villains, were hiding references to Joshua. They were ultimately promoting their gods as a replacement for Joshua. This replacement starts with Solomon who puts in the Yahweh term instead of Joshua. Solomon built a temple to Yahweh. The term is still used by Jews and Zionist Christians. Sometimes the term in English is Jehovah.

By the time of Ezra, the ruling king is Persian. That kingdom has a "god of the skies." Ezra has power over the manuscript. He has a commission from a Persian king. So he ultimately plays manuscript games to feather and adjust the text so it conforms better to his boss, the king who pays Ezra's wages. This explains the diversity of divine names in the Old Testament.

So far, what I have just stated is review. What about the New Testament? What was Ananias doing? Did Ananias also have a god?

As soon as Ananias starts tampering the New Testament he is following in the footsteps of Solomon and Ezra. So his work is similar. Like Solomon and Ezra, Ananias is introducing a new god to the text. Most of Ananias' work is more subtle. Especially in the Gospels, his favorite trick was to copy around, and tweak, the otherwise inspired stories, similar to the way Chronicles copies Kings.

So after Ananias' work, we mostly end up with duplicate copies of events in Joshua's life. Some of those copies are inspired, some are not.

Markup

So Ryan has been working out changes in the BRB markup to cope with these issues. So far, this work has dealt with the edits of Solomon and Ezra. Dark green voice marks text by Joshua. Light green is attributed in some way to a god created by an editor.

The Filter related tags ride on top of this, but carry a different purpose. Filter tags mark text NOT in the Testimony. Filter tags also mark the likely villainous author.

Finally, there is markup that shows the likely chain of changes to the divine name. In particular how to get back to Joshua when Joshua is the likely inspired name.

Of course this is currently speculative. But this markup will get adjusted to conform to the audit. So specific examples will stop changing as the speculative nature of our work comes to a close.

New Testament

So Ryan has been looking at applying this same new markup to the problems with the New Testament text.

Most of this work is looking at duplicate passages. Those are the most common form of trouble in the Gospels. So when he selects the duplicate passage as being likely from Ananias, several tags start to apply.

The first is a Filter tag for Ananias. This marks that Ananias created this passage. The passage is thus not in the Testimony.

The dark green markup that was used for Joshua's voice, now changes to light green. This is exactly consistent with the recent Old Testament work. Now, in the New Testament, light green marks the voice of a god created by Ananias.

This is disorienting because we are used to having Joshua speak everything that is in his name in the New Testament. Though strange, this is still technically correct. Again, remember, this is currently speculative, but will be confirmed by audit.

So what happens to the name Joshua?

We spell this word the same as Joshua son of Nun. It is a reasonable English for the Aramaic, so Paleo spelling.

But what if the name Joshua ends up used in a light green, so Ananias, duplicate passage?

Or what if the name Joshua is used when describing some action that is the creation of Ananias?

Ultimately, this question is the New Testament version of the same problem going on with especially Solomon and Ezra's Old Testament edits. There is an implicit change in name. Ananias is not reporting on anything that the real Joshua actually said or did. It is thus incorrect to use Joshua in these Filter Ananias' passages.

So what divine name should be used for Ananias' New Testament edits?

Ryan had a flash of inspiration for what to do here. In these New Testament passages which are NOT headed for Testimony, the BRB now uses the name "Jesus." This is the Hellenized form of the name Joshua. There is a certain symbolic justice in selecting this name for use in non-inspired text.

For readers here who are still with me, and have not fallen out of your chair, this new name convention goes live when this blog goes out.

We are not yet all the way through our Tabernacles related New Testament reading. Ryan wanted the markup to catch up before we finish. More in future weeks.

Paleo Bible

Our general work load from Tabernacles has finally returned to something more normal. It has been about a month since I was able to really focus on the names lexicon problem with the Paleo Bible. I was finally able to return to this work this week. The Paleo Bible app now has the first installment of names loaded into the text. The link is given above.

This week all names have been loaded from Genesis to about Numbers 31. To see this in action you can look at Genesis 5 or 11 which are genealogies. Also Genesis 25, 36 and Numbers 26 have patches of names. Parts of Numbers 26 are almost completely filled in by the lexicon.

There are a few very high occurrence names that have also been added to the lexicon, but out of order. Joshua, Moses, David and Solomon are examples of the high occurrence names loaded out of order.

In terms of lexicon coverage, the lexicon now has 872 roots. It covers 10,956 different inbound forms for those roots. There remains 40,006 unique, but unknown, words in the inbound text.

In terms of manuscript coverage there are currently 692,427 inbound words in the manuscript. 534,312 of those words, so 77.17 percent, are found in the lexicon. 158,115 words, so about 22.83 percent, of the inbound manuscript have no lexicon entries.

These numbers shift around in unexpected ways because the lexicon itself identifies word breaks. So the total manuscript words climbs as the lexicon gets filled in.

Because the audit problem is so complex, it is important to keep the steps organized. Getting the lexicon and names annex filled is the current step. The overall goal here is to get an English word for all words in the running text. Once that is done, the recovery work can move on to other problems.

All of the names work is sorted by first occurrence. This provides a check on problems of missing or extra names when comparing texts. There are a few of those, examples follow. So names are getting loaded into the Paleo Bible text in their manuscript order. Names missing or out of order are at least being understood as to why they are missing or extra.

Lexicon Grouping

The most common problem I am currently dealing with is related to how words in the lexicon group together. Eventually, each lexicon entry will show a family of closely related words. Given the overall stats shared above, each lexicon entry will show off about 10 different forms. Of course, some are much more complex, and some are simple.

Names are headed for a names annex to a complete lexicon. That lexicon will also be sorted by the spelling of names related root words. Names have roots and suffixes like other regular words.

Perhaps the most common names related suffix is Yo-Wa. This ending turns a place name into the "ites" that live there.

So in the final lexicon, the root and this form need to merge. Sometimes these groups are already formed. Sometimes not. Once all names are loaded, a full alphabetization of all name related roots should provide a final review of what names belong in what lexicon entries.

Complicating this problem are frequent spelling variations on names. Added vowels, inconsistently applied, are everywhere. There are also common consonant transformations. Du and Re are often irregular.

These irregularly spelled roots should still be pulled together into single lexicon entries when the English is the same. This is done under the assumption that audit will remove the added vowels and fix spelling variations.

It is theoretically possible that what we know of as single English names are actually hiding different names. It is also possible that some names have more than 1 inspired spelling. This might be needed for ciphers. These are examples of issues that still need to be worked out.

Different Stories

Turns out, at times, the Aramaic just does not tell the same story. So at times there are discrepancies in the names lists. At times the Aramaic is not using a name at all, but regular vocabulary. This pattern is pretty common, which I did not expect.

If a story in Aramaic is using regular vocabulary, with the other parallel languages using names, we are probably seeing a sign of inspiration for the Aramaic version. This is a topic that will get more attention once we find audit passing passages that function this way.

It is also possible that someone in the translation chain out to English may have replaced a technical vocabulary word with a name in order to hide something frightening to Zionists. I have now looked at enough names to suspect there are games afoot in the English translation chain.

Translation vs. Transliteration

In most cases, when translating between languages, words which are used as names are transliterated. Transliteration is the consistent use of some system of letter substitution going on when names are moved between different languages.

For example, the conventional English version of some name will generally match what is going on in Paleo. I used Philip as an example in a previous blog. The subtle differences in that example become humorous, they are not serious.

The same goes on across ancient languages. Since Hebrew and Aramaic are both Semitic languages, the Paleo alphabet forms of names used in both of these languages is nearly always the same. Abraham, for example, is Wa-Ba-Re-Fe-Mo. This Paleo spelling is the same when coming from both Hebrew or Aramaic.

So when we see a word which is a name in one language, but then translated as a technical vocabulary word in the other, we know a game is afoot. As I crawl through the list of names, which I have intentionally sourced in a modern English text, I can see modern games afoot in this space. Zionists are still hiding stuff from English readers. There must be frightening topics for modern Zionists which are now hidden from readers in English texts.

Let me give a soft example that most readers here might recognize. This one is not particularly scary.

Nephilim vs. Giants

My first main English translation of the Bible was the NIV. This is the text that I had read through about 19 times before getting into our current work. In the NIV, in the time before Noah, there were Nephilim in the land.

In other versions of the text, say the KJV, there were giants in the land. Since I knew only Nephilim, anyone preaching about giants in the land was strange. Steve Quayle, for example, has an extensive video collection of hunting for skeletons of giants. He links his giants to that pre-flood story. Of course, for years, he looked to be using some secret knowledge to think his giants work was from the Bible. Actually, his work was just based on KJV English.

The Aramaic, so Paleo, for those Nephilim, Giants, is Ge-Ne-Ba-Re-Wa. This is NOT a transliteration of Nephilim. So there is a Zionist game afoot here somewhere. Why would the KJV era translators treat this as a technical word, but modern translators need to change this to a name?

I cannot say for sure what this word means. We need to be through audit. We need all inspired occurrences. We need to see how else it is used. But, the root is known. Ge-Ne-Ba is "nab" in English. It is one of the commandments. Don't gather seed in another's tent. Don't take something not yours.

If we add a Re, so head, so authority, this forms something like what gangsters, or central bankers, do as a group. The Wa ending is just "the." That those criminals saw themselves in this story may be what was so frightening that it would be hidden with a name.

Other Strange Names

This pattern is showing up with more mundane examples. In English we have sub-cultures that name things using common words. Summer camps for children are this way. "Purdy Creek," so "Pretty Creek" is an example. A common practice with railroad maintenance workers is name features of their rights-of-way this way. "Dead Man's Curve" or "Petticoat Junction" are a couple examples of this sort of naming convention.

It appears that this style of name creation was also going on in some of the accounts we read about in scripture. It flashed by fast this week, so I cannot give a cite, but the place name "mound of the testimony" is an example.

This looks like a very common pattern with Aramaic alone. This is something that we need to better study. It is new to us. So, when a name in Paleo is not transliterating into English, I am generally leaving those names out of the names annex. These words will be picked up as technical terms and get translated into English in the normal way. This process will leave behind the details that are needed to study this problem.

LORD, Lord, lord

I would guess that most readers of this blog grew up in a church tradition that used a text ultimately based on the KJV. Modern examples include the NIV, ESV and so on.

Those textual traditions cover over a series of pretty serious original manuscript problems using various forms of the world "Lord." Typically, this word is capitalized in 3 different ways.

There is only 1 way to speak this word. So in the minds of most church goers, these words are essentially all the same. They are not. These are clues into a crime scene investigation. It allows the translators to feign ignorance of their crime. They do use different spelled words for different underlying terms. But, they are covering up a mess and playing mind games in the heads of their Christian readers.

Greek, Hebrew and Aramaic

Making this crime scene even worse are the variations between the 3 different manuscript traditions as passed by history. Constantine's Christianity from 313 AD was based on Greek. Christianity, as we know it now, starts in Greek. In the Orthodox branches of Christianity, it remains mostly in Greek.

By around 400 AD, the Latin western church received a Latin OT based in Hebrew. Zionism was taking over. Jewish bankers were now ruling the church. The church was the front for the Jewish banking cartel that still rules most of the world.

Money and politics drove the west. That unholy alliance drove theology.

By around 1600 AD, the English wanted more of a cut. Usury was legalized, and an authorized text of the Bible appeared in English. It was personally approved by the king. His PR team explained he was an ancient language scholar. LORD, Lord and lord were still perfectly fine. Nobody wanted this secret to leak out. Anyone in ministry could wave away any questions about what that capitalization was hiding.

Lurking behind this entire western manuscript stack was the Assyrian Church of the East. They carried around Aramaic versions of both Testaments. This church tradition remains the ongoing victim of various genocides. The Armenian genocide was the largest and most well known. Zionists and their friends have been removing Christians across West Asia for the century since Armenia. Those Christians can dispute much of western Christian theology. Though they still do not have a clear view to the problem. They are just a serious threat.

Breaking Through

So over Tabernacles, Ryan and I first saw through this entire stack of manuscript related troubles. Joshua, so Jesus, is the only supernatural agent in the inspired text. He was the agent in the Garden of Eden. He has been active in the affairs of people ever since. He tends to care about people, especially families, of faith. He is actively raising souls to make them able to live forever. The first major harvest of souls appears to have been at the time of Moses. There was another such harvest late in the first century. Joshua willing, there will be another in our generation too.

The claimants to Joshua' position are called "gods." Gods are imaginary. They are created in the imaginations of men. Not just any men, but men who have carried political power for most of history. They invented various gods down through history. Their primary purpose is to give kings an apparent right to rule.

Joshua himself is involved in this process too. But not as a sign of favor, but as a sign of ignorance and rebellion. This is the point of Samuel's speech involving the problem of asking for a king. Gods, as an idea, spring up around kings since those kings want some apparent right to rule.

So fights between kings becomes fights between gods. We might say this slightly differently. Kings frame their own fights as fights between their fictional gods. The victorious king gets to promote his fictional god as the god that gave him the victory.

This general view of the world of living under gods, and not Joshua, is the context for various stories in the text. The Book of Daniel explains a dream where we learn of a series of successive kingdoms that will follow Nebuchadnezzar's kingdom. They are all ultimately heirs of Nebuchadnezzar's Babel.

That dream ends with a "10 toed" kingdom that is most likely the European Union and its children, the nations using Anglo bankers. The effective prophetic seat of the government for that kingdom is London. This is why the king recently visited his subjects in the US Congress. The reserve currency for that kingdom is clearly the USD, and that is also based in the USA.

Watching out for gods, so pretenders to Joshua's standing authority, is now becoming something of a spectator sport. We can see it in world headlines. We can also see it in parts of the text. Any use of LORD, Lord or lord in the text is going to be trouble. It is going to mark some sort of battle of the gods on the way to the world we know now.

One of those strange stories is in the Book of Ezra. In this blog I want to introduce you to the problems of Ezra.

Book of Ezra (KJV)

The link here is to the KJV version of the Book of Ezra in our Bible Reader app. This app is linked off Paleo.In. That app contains a series of versions that help to see the various forms the Bible has taken across time.

The KJV is interesting because it is the reference text that nearly all other English language translations have conformed to for the past 400+ years. The Bible purchasing public always wants something they know. There has never been a successful gap since the KJV where some non-conforming translation could materially diverge and still remain commercially viable. The ASV and RSV tried but failed.

Purpose

The Book of Ezra provides the origin story for the temple that was the stage prop for events during Passion Week in the New Testament. As readers of the New Testament, we need to know where that place came from. Ezra explains.

A secondary purpose of this book is to provide the commissioning letter for Ezra. This man is one of the 6 villainous editors. In particular, Ezra was commissioned to setup the distributed synagogue system that runs far away from the temple itself. Christians also know this as the local church system.

The Book of Ezra explains Ezra's personal ties to government funding, both for the building project as well as providing pay for those who work there. Similar ties to the Church have existed across most of European history. You can still easily see ties between the government and church in Russia.

American experience is slightly different. Generally speaking the government has stayed away from close ties to church. The "separation of church and state" has been a simple principle, easy for anyone to understand.

In practice, the US Government has been mostly run by Jews or their gentile cousins Freemasons. Keeping government funds out of church was a way to minimize the influence of Christians over the state. From the side of Freemasons, keeping out the moral and the people of faith was a useful thing. This is ultimately the source of the "Epstein class" rule of Congress. This is also why no amount of voting will alone ever fix problems in the government.

In any case, having the government be the ultimate backstop for most of Christianity has probably provided for the survival of the New Testament to our day. The king defended the KJV text by the force of arms. Ezra starts that process.

Ezra (ASV)

So until this past Tabernacles we have not had a sufficient mental framework for understanding the strange problems of the "divine names."

Some English language translations have attempted to nudge their readers beyond the LORD, Lord, lord family of problems. Perhaps the best known was the 1901 ASV. The link here is to the Book of Ezra in the ASV in our Bible Reader app.

If you look at that text, even verse 1 has a reference to "Jehovah." This is a hint at the "Yahweh" term found in the Hebrew at this location. This ASV was attempting to remove the LORD, Lord, lord triplet and expose at least some English vocabulary to allow readers to see 1 layer down.

The use of Jehovah, a stand in for Yahweh, is probably the most important reason why the ASV was not commercially successful. It was exposing a fundamental rift between the Christian New Testament and the Zionist Old Testament.

Ezra (BRB)

So the link here goes down 1 more layer. This time to the Ezra in the BRB. It has been checked against the Aramaic. Our BRB text treats Mo-Re-Yo-Wa, as the English word "Master." Alternative treatment is possible, but it would be even more strange to English readers.

Our theory of inspiration goes something like this. The inspired form of this book began in Paleo. It was transliterated to Aramaic. So far, so good. Aramaic readers could now read Paleo texts.

Scribes were later forced to change public Aramaic texts in order to conform it to edits going on in Hebrew. Some generation of those scribes changed out Solomon's Yahweh for Master. This would be following the public conventions on acceptable divine names. Some scribes probably knew the work of the editors and did not want to follow precisely along.

But, there are clues in Ezra that allows a reasonable stab at what the various god names might have been in the original text. Ryan has gone and made an estimation of that set of names. It tells an interesting story.

The book begins with an inspired introduction. It explains how Ezra's temple to Yahweh in Jerusalem was built as the response of a prophetic word given through Jeremiah. This was the end of a 70 year interval which was also tracked in Daniel.

This is a very strange introduction. Why would Joshua grant the construction of such a temple?

Joshua is in control of the world. He remains in control, even over evil men. They are following Joshua's own general plan for history. Evil men cannot escape that plan, no matter how much they may want to escape the plan.

The story then shifts down to the detailed story of the reconstruction of the temple to Yahweh that was done in Ezra's day.

There are a series of letters recorded in the Book of Ezra that deal with the details. It ultimately ends with the commissioning letter of Ezra himself. Ezra is the 5th villainous editor, the last in the Old Testament.

God vs. Elohim

If you read through Ezra you will find divine name transformation details provided in square brackets. An example is in Ezra 1:2. Let me quote it in full. "Cyrus, king of Persia, says: All the kingdoms of the land the Master [Yahweh], the God [Elohim * God] of the skies, has given me.

In Aramaic, we have one more odd complexity. Master, in Aramaic, is usually covering for the name Yahweh in Hebrew. So you can see the Master term followed by [Yahweh] in the BRB. Ryan is suggesting the audit will pass with Yahweh at that location, not Master.

Then there is the term "God." In brackets Ryan indicates [Elohim * God] which means Hebrew sees this as "Elohim" the name of a specific god. But in English it should be considered the generic "god" term.

There are people who name their pet cat "Cat" or their pet dog "Dog." This is fun, but confusing to anyone not in the know. (A dog named this way will strangely answer to anyone using the generic, probably not fair to the dog.)

In any case, something like this appears to be going on with some uses of the term "god." At times the term appears to be used as a specific god's name, Elohim, and at times the term used as a generic god term.

This is probably a natural outworking of a battle of the gods. At some point some powerful group used their name for god as the generic term for the category itself. That group was "Elite." They named themselves as a group after their god, El or Elohim.

Remember, this is all imaginary. It is the result of the battle between kings who were using false gods as giving them their right to rule.

This is why Joshua is not a god at all.

Which God?

But with this setup, you can now read through the story of Ezra and see the development of an interesting plot.

The entire temple building project in Jerusalem is commissioned by a Persian king. That Persian king followed the "god of the skies." The skies are over all. So from the Persian king's perspective all other gods are below the skies. So the god in Jerusalem is a lesser god. The group in Jerusalem was only following "Yahweh God."

This becomes a major plot complication. The Jews in Jerusalem are out to build a house to their god. They were fooling the king in Persia who has commissioned and provisioned the temple under different terms.

The Book of Ezra contains letters sent back and forth that started and stopped the building project. The battle is theological. Which god rules?

The Jewish answer appears to be the adoption of the generic term "god" as the "1 true god." Thus they retake theological control over Persia by slight of hand and by defining "Elohim" as the singular god.

The Book of Ezra seems to be the place where the inspired text is attempting to show how these ideas came to be.

Christians fall prey to the same linguistic slight of hand. The 1 true god ends up as the "father god." So there is a developmental chain out from Jehovah/Yahweh to Elohim to the fully generic god. Jesus ends up as the son of that father god.

This is the mess we all grew up in.

Interested readers can pick through the Book of Ezra's various letters in order to get some idea as to how the Jews absorbed the "god of the skies" back under themselves. This is generally the same theological process that was used by Ananias when editing the New Testament.

Headlines

Interesting headlines this week came out of Yemen, Iran and Russia. The war situation in Yemen appears to be the current best fit for our ongoing watch date.

We are currently in the replay of the reign of Azariah/Uzziah. Both names are used for him. It ends 2026-10-02. He had leprosy and lived in seclusion. His story maps the plague of boils that start with a fire from a furnace.

We have been tracking references to use of nuclear weapons because Japan was the last use of such weapons. Nuclear fallout creates leprosy/boils in the victims.

This week the war situation in Yemen has shifted to Ansar Allah's favor. They have mostly driven out Saudi mercenaries from much of western Yemen. Ansar Allah has mostly regained the coastal cities along the Red Sea and will be able to better enforce a blockade against Saudi oil transiting that passage.

Ansar Allah has also been very successful at targeting Aramco oil facilities across Saudi Arabia. Some of the fires have been historically massive. So the fire from a furnace into the air, for the expected plague, is matching this war very well. Perhaps better than anything seen with Iran.

There was a headline a few months ago where Trump agreed to supply the Saudi's with nuclear technology, so there is a match to nukes in Saudi Arabia. This is tying the Japan/Nuke part of the story to Saudi Arabia.

Ansar Allah has been under blockade from Saudi Arabia for about 12 years. So the king in seclusion is also a match.

This story ends on 2026-10-02, so there are still a few more weeks before this is over. Continue to watch this venue. The Saudis are Zionists, a fancy name for Pharaoh. This identification is NOT like Iran. This detail may matter to the general flow of these stories. Pakistan has a new defense pact with Saudi Arabia. Unclear if this would be brought into play.

Also of note, on the Zionist side of this war, the Israelis may have used a nuke in Lebanon in this week. The link for that is at the bottom of the blog.

Watch Dates

There are no other known dates until 2026-10-02 when we watch the end of the current king's reign. Jotham begins on 2026-10-03.

Shop Work

Shop work this week has been loading names into the lexicon for the Paleo Bible text.

Headline Review

The following caught my attention this week.

Trump's Men to Putin

The link here is to a PressTV post on Telegram with a pic of Trump's team arriving in Moscow to meet Putin. They would spend several hours with Putin and then travel to Kiev.

$100B Bribe

There was virtually no western media coverage of what was discussed when Trump's men met Putin. The link here is to John Helmer on with Nima to discuss what was known about the deal from Russian sources in Moscow.

Key points: Trump offered Russian oligarchs a very complex $100B bribe to stop the war in Ukraine. This would be giving the Russians back a little of their current frozen assets. The deal is structured in such a way to give the Trump family a massive financial windfall. This is why the Trump family are doing this and not normal diplomats.

My opinion: Though it would be called a peace agreement, in reality this would be a chance for the west to rearm and restart the war a few years from now. The Russians would be utterly foolish to accept. BUT, the timeline might want a break until prophetic dates in 2028 or 2029 or beyond.

Iran Targeting US Carrier

September 4, 2026, the IRGC targeted a US Aircraft Carrier with new long range missiles. Different accounts describe either a hit or at least how the US side needed to flee the region.

Iran is at least demonstrating they have air superiority, enough to prevent the US from operating near Iran.

Ukraine Map?

The New York Times, that great bastion of absolute truth, has published a map of what Putin will demand of the west to end the war in Ukraine. Mostly nonsense. But it does show what others have discussed about what Russia might want. Note how Kiev ends up in the center of a runt Ukraine. This city is probably to be fought over until the world burns down.

Japanese Fighting Words

The Japanese don't like Russian boundary artwork. This post by the Japanese Prime Minister has details. Japan looks to be readying the basis for some future war against Russia. Japan does not see itself as defeated, instead Japan is just waiting for history to allow the war with Russia to continue.

AFD Victory

The link here is to one of many posts on Telegram by Lord Bebo dealing with the recent election in Germany. This post has a graphic showing mail-in ballots as a percentage by each party. Mail-in ballots are going to be the German equivalent of ballot stuffing in the USA. You can see every party except AFD had more mail-in ballots than real voters. Zionists rule Europe just like the USA.

Saudi Nukes

Part of the prophetic story of Saudi involves their use of nuclear tech. This link details their setup to the IAEA in order to get that started. More of the prophetic matches for this month.

Fire From Furnace

For the record, a pic of fire in Saudi Arabia from Ansar Allah missiles. An example of more of the prophetic matches for what looks like our current set of headline matches.

Japanese Bond Sales

This is a link to a Youtube video detailing September 8, 2026, sales by Japan of $88B in US Bonds. Japan is the most likely country to cause a contagion that might spread through US Bond markets. This appears to have been an outright sale, and not just putting bonds on deposit with the US Treasury.

Netanyahu Knew October 7

Everyone suspected that Netanyahu knew about the October 7, 2023, attacks on Israel from Gaza. Now a book is out with details. The link here to a TASS post on Telegram provides some details that the UAE knew about and warned Netanyahu about 10 days ahead. It also cites the book where this is now published.

Rust on USS Abraham Lincoln

This is a followup. What originally looked like rust on the USS Abraham Lincoln was a heavy build up of algae. It was cleaned off by Thailand based port services. This post has some video from the local cleaning crew.

M4.1 Quake in Lebanon

The link here is to a brief Youtube video with a clip of an Israeli explosion in Lebanon. It was reported to have happened September 10, 2026. But, this happened at night, so the day break is disputable for charting.

1,100 tons of explosives were said to have been used. The shock measured as a 4.1 M earthquake. Hal Turner was the first I saw to report this. There are many other reports across the Internet.

No one is reporting the obvious. Israel used at least 1 nuke. This was the TNT equivalent of 1,100 tons of explosives. Israel did not use 500+ truck loads of bombs to create a quake of this size.

Israel looks to be using Lebanon to threaten nukes against Iran.

This is our first likely documented use of nukes in this prophetic window. We still have until October 2 for more.

More Later,

Phil

Paleo.In Rebuild

Phil Stone — Fri, 04 Sep 2026 20:22:24 GMT

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.

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

Micah

Phil Stone — Fri, 28 Aug 2026 20:00:49 GMT

This blog looks again at the story of Micah. Before that, an update on the Divine Name related edits that began at Tabernacles. Also, there is a sketch about a theory for changes in the spellings of Paleo names. Then notes on Ratcliffe's trip to Moscow, our expected headline this week. Then finally, a general headline review.

Story Grid

Ryan continues to make an editing pass across the OT. He is cleaning up references to Joshua. This pass is making OT based material in the TT app read more like the New Testament. Individual parties in the OT now look to interact with Joshua in ways that are similar to what we see in the NT.

The link here is to the Story Grid app. With this week's deploy, the updates are down through story 399, though there are patchy spots that need more attention earlier in the grid. This update is also found in the other apps, so the TT and SR.

Plot Changes

These updates reveal a plot across this material related to how well the public knows Joshua. Awareness peaks at the crossing of the Jordan. It collapses after Samuel, especially once we reach the first editor, Solomon.

Once we get beyond Solomon and his construction of the Temple to Yahweh, we now find stories where Joshua is known to individuals, but not as acknowledged publicly. So following Joshua becomes more like an underground faith, not a public faith.

Until the Assyrian deportation, the keepers of that faith appear to be a more or less well known tradition of prophets. That community of prophets appears to be caring for a larger community of faith. There is a reference in 1 Kings 19:18 where Elijah is told there is a group of 7,000 who have not bowed to "Baal." Presumably this is the community of faith that Joshua was caring for, and why he was preventing the Assyrian Deportation.

This is cited in Romans 11:4. In that NT cite we see that early NT era believers were also a small remnant. So these 2 different eras in history, very roughly about 1000 years apart, were functioning similarly.

Presumably the NT era community survived until Ananias' edits took hold. Really until that community became walk offs. The OT era faith community had presumably mostly become walk offs by the time of the Assyrian deportation.

So it is in this world that we read about the story of Micah. This prophet is one of the prophets that appear to hold together that ancient community of faith. He is called to an audience with the kings of Jerusalem and Samaria who are discussing going to war.

Micah Called

The link here is to Book 15, story 157 in the TT app. This app is linked off of Paleo.In. As the app is currently under development, this link is not permanent. It is fine this week. Future readers of this blog should search for "Micah" in the app in order to find this story.

In this story, Jehoshaphat, the king at Jerusalem, has gone to visit Ahab in Samaria. These 2 kingdoms were in a permanent state of attempting to recreate the unified kingdom. They would never be successful. The split in the kingdom itself was a consequence of Solomon and his temple. Joshua enforced the split for as long as Samaria remained.

In this story Ahab proposes going to war with Ramoth Gilead. Ramoth, by the way, in Paleo, is pronounced like the English word "Remote." It probably has the same meaning. This name implies a distant place, so at some edge of the territory. There is a natural implication that getting there is not as easy as some nearby location. This will not be a police operation, but a military operation.

Ahab has married Jezebel, so Ahab is farther from the historical faith than Jehoshaphat. Jehoshaphat wants Joshua's true word on the wisdom of going to war. He asks Ahab if there are any prophets around. There is. But Ahab does not like Micah because he always prophecies something bad. No matter, Micah is called.

Remnant Faith

So at this point we can see how a remnant with faith functions in an otherwise faithless kingdom. Even the Jerusalem king, an heir of Solomon, still knows of Joshua. He still knows Joshua speaks through prophets.

This implies, by the way, that this king also knows the Yahweh god at the temple in Jerusalem is just theater. This also implies the king has some sort of stage presence when it comes to activities around the Jerusalem temple. But he also knows how to get real answers from Joshua when it matters.

This story may be giving us some insight into the Apostle Paul. Paul was out of Benjamin. He was well versed in the Yahweh false religion. He encounters Joshua on the road to Damascus. At that point Paul also starts to live his life knowing the difference between these 2 systems. This may be why Paul was such an effective evangelist. This may also be why he was so hated at Jerusalem.

For us today, we can imagine the same problem. Our edited New Testament lets us know that Joshua exists. But Joshua's purposes on earth and his patterns of life are hidden. Fixing the edits will create a similar distinction. Some will know Joshua correctly, like Micah, and some will not, like Ahab. Some will be in the middle, knowing of Joshua, like Jehoshaphat.

So Micah knows Joshua. Micah is known for being able to speak on Joshua's behalf. Micah is brought to the king's party. Micah then runs into yet another problem.

False Prophets

As the story unfolds we learn there are 400 local prophets who tell the kings that they should go to battle, and that those kings will be victorious.

Micah is told that he needs to prophecy the same way. He is told to tell the king that he will be victorious.

Micah, of course, cannot just go along with the crowd. 1 Kings 22:14 is the original cite. Whatever Joshua says, that is what Micah will speak. Nothing else. But, in this case, Micah, in an apparently mocking tone, goes along with the 400. Those 400 will not know Joshua. They do not know that Joshua speaks. This is why they would tell Micah what to say.

The king Jehoshaphat knows Micah is mocking. The king asks again. Micah then gives Joshua's word, that every man should return to his own house in peace.

This is very typical of the way Joshua speaks. The answer is not about the same subject. They had asked about victory. The problem is the assembly itself. The visiting king needs to go home. The 400 prophets need to go home. The whole place needs to disband.

Many, many times, I have seen Joshua answer questions in a similar structure. The question itself is far away from the real issue. Everything about the context where the question is being asked is trouble.

Joshua's answers to prayer often reset the context around problems rather than solving the problem at hand.

Bigger Plans, Deeper Problem

Micah then goes on, and explains how the entire assembly of 400 false prophets is actually doing Joshua's bidding. They are Joshua's plan for how Ahab will go to his death.

This is something like a text book example of how Joshua uses false religion. Even though these false prophets are false, they are still unable to escape the problem that they are simply carrying out a task that has been ordained for them.

This is another layer of insight. Those prophets think they are doing the right thing. They are practicing the "state religion" of Samaria. But they are following a lie. In the end, their lie will still achieve the goal Joshua had in getting rid of Ahab.

The same is actually true of Jerusalem itself. The difference, at least in this context, is that Jehoshaphat knows the state religion at Jerusalem is false. Jehoshaphat can at least reach a true prophet when he has need.

It does not really matter to Joshua that the culture at large does not really know him. Joshua interacts with his remnant. There is always some set of souls, say 7000, that he is currently bringing to full spiritual development. The rest is just the stage where that activity happens.

How About Now?

These same patterns go on now too. What is different now is that there are no true prophets. The text is closed. There are only limited prophetic gifts. There are a few people who operate in ways similar to Micah. But, unlike Micah, nobody these days has access to inspired text. All of us are in some sort of soul holding pattern. This was also true leading up to the New Testament era.

Other patterns of our day are quite similar to the patterns in Micah's day. There are many utterly false prophets who follow lies. There are also fictional systems of belief that are all across the globe.

Joshua, though, is also very real. He alone can answer prayer. He can send his angels. He can step in and rescue. He is still following a long term plan for history. He he still developing souls. We can also seek him out and ask him questions.

Hopefully, here soon, the text will be opened and we can get out of a 1900 year long soul holding pattern.

Names Work

This week I have continued to work on the names annex to the Paleo Lexicon. This week's work was mostly verification of entries from the previous few weeks. Cleaning data as early as possible in long pipelines makes later stages easier.

The main focus this week has been to gather words into what becomes lexicon entries based on roots. Roots don't come to us clean. Different places in the text have different added vowels for the same words. So names found in different places, with different spellings, will still belong in the same lexicon entry. Like a puzzle, they need to be combined.

For some words the number of spelling variations is excessive. Nobody seems to have agreed on how to spell "Israel" for example. The word itself may not be inspired at all, so perhaps every editor had a different idea on how to spell that word.

In any case, here in this blog, I want to start sketching out a possible theoretical framework for how and when some of these names were changed. Especially interesting to me are NT names.

For very early names, Enoch, Noah and so on, we only know those names by the spelling found in ancient texts. For New Testament names there are parallel witnesses to those names. So New Testament names can be used to understand certain interesting features in the Paleo language.

Starting Point

The New Testament was likely written by a group of authors sometime before, say, the year 50 AD. We don't (yet) exactly know when Paul arrived in Rome. We suspect his court case before Caesar contributed to the Roman destruction of Jerusalem in 70 AD. So the dating of the tail of Paul's arrival in Rome is ultimately what dates the last bit of inspired writing.

Original readers of the inspired NT will have been using Paleo. This is true because the ciphered documents are in this language. All of the exhibits are built to support this language.

From this base document for the NT we end up with the extant Aramaic texts that are passed down through history.

Our Aramaic professor on Youtube does not think those documents were inspired because there are "Greekisms" in the Aramaic. He dates the preparation of the current Aramaic New Testament as having happened out in the 100s. He places it perhaps up in what is now Turkey. So a century after they were originally written, and far away.

So let me propose a theory for how the texts moved from inspired Paleo to the extant Aramaic. This theory involves various steps.

Step 1: Authorship

Original authors are going to prepare audited Paleo texts. Once known to pass audit they will have been ciphered. Very early faith communities would know these documents. They are scripture. They add to the inspired version of the OT that had been recovered by Joshua and his early disciples.

The Megiddo Mosaic floor is an example of a place likely from one of those early faith communities. They will have possessed the entire inspired library. This includes base texts and ciphers.

Step 2: Editing

Within Ananias' lifetime, so likely before 70 AD, he will have taken the original NT texts and edited them to something approaching the current modern form. He probably did this in Greek, with a Greek translation.

Ananias' purpose would have been to prevent the Paleo faith community from reaching the Greeks. This is called "front running." Zionists do this all the time, even now. This is why they so often want to control media.

This work would provided a language and conceptual barrier that would stop missions work by people like Paul. This would produce an artificial Greek faith, outside of the Hebrew communities located in and around Jerusalem. So Ananias was protecting his priestly power by deflecting Christianity into the Greek speaking world. He was also creating an appendage to the edited Old Testament. His edits were feathering with the Hebrew OT.

Step 3: Aramaic

The basic Paleo language system appears to be the same as Aramaic. Letter forms are basically the only difference. So a transcription to Aramaic from Paleo is an obvious first step. This, of course, breaks from the exhibits. But it does let someone who can only read Aramaic then read the NT text. So this would not be done by the early faith community. But it would make sense for someone to carry out. Local scroll shops, for example, could have done this.

This seems to have been an important step. This is especially so if recovery back to paleo is ever going to be possible. Looser translations do not look recoverable. The ability to recover the text is part of the promises about the text. So a transcription must have happened early on.

Step 4: Uplift

So at some point later, say in the 100s, the Greek NT texts, which are far longer than the transcribed Aramaic, will need to be used to uplift the original Aramaic work to match the Greek based editing. The Aramaic Christian church is going to mostly match the Greek Christian church because the basic texts become the same canon, just in different languages.

The expected uplift pattern would be to take the extant, but short, Aramaic NT and expand it to contain all of Ananias' Greek edits. This appears to be the work that is known to have happened in the 100s. This step would explain the "Greekisms" found in the text. When done as an uplift to an earlier Aramaic text, it would still allow recovery through use of the audit.

Linguistic Limitation

The Paleo language system does not need nor use written vowels. The vowels themselves come from the top side of the silver set of 3d models.

As I study spelled names, especially NT names, I can see heavy and irregular use of added vowels. Why would this be so?

The Paleo writing system appears to be using implied vowels so that the letter string can go through ciphers. Each Paleo letter looks more like a small syllable rather than a simple letter. Ethiopian languages still work this way. Those syllables are what get ciphered.

The Paleo language pays a price for this design choice. The Paleo language cannot express every combination of consonant and vowel. Indeed, the language is limited to only 6 pronounced vowels. Each consonant only has 1 vowel. Most humans can detect as many as 16 vowels, but they need to be trained beyond about 8 vowels. The human vocal track has certain primary vowels which is were we find the inspired vowels.

Earlier this year we looked closely at the Ethiopian Bible. Turns out, the Ethiopian languages solved this same problem of breaking fixed consonant/vowel pairing by adding shapes, so syllables, to their alphabet.

Essentially all other phonetic languages use special letters to mark vowels. When there are not enough letters, they often add accent marks to their basic vowels. English is one of the very few languages without marks on vowels.

So by design, each Paleo letter is limited to only 1 trailing vowel sound. When those trailing vowels sounds are not vocalized, the listener knows this is a word break.

Adapting Paleo

The people and places described in the New Testament narrative had actual Latin, Greek, Hebrew and perhaps Aramaic names. Those language systems are more expressive than Paleo. In those languages, vowels are combined with consonants more or less at will.

So the inspired authors would have been generating short form, Paleo, names for the characters that they were writing about. They had no choice. This was a design limit of inspired writing. It is the setup needed for writing stories that can go through ciphers.

So in the 100s, when Aramaic with implied vowels is forced to adjust to Greek names, the scribes doing this work need to break standard Paleo. This breakage hides any ability to cipher. But ciphers do not matter at this point. They are including non-inspired text to conform to Ananias' edited text. The entire exhibit system was lost as well. They are creating church as we know it for an Aramaic audience.

Scribes working the "uplift" stage can then use added vowels to more accurately reflect the sound systems used for original names. The short forms used by inspired writers gets lost.

I have seen this breakage of standard Paleo names across the entire names lexicon, but especially with New Testament names. It is best to show this problem using an example.

Name: Philip

Let me use Philip for this example. The absolute shortest possible Paleo version of this name is Fe-Lu-Pe. It could be Pe-Lu-Pe if the Ph, so f, sound does not need to match in the Paleo form.

But, the Aramaic version of the Greek version of this name is "Pe-Yo-Lu-Yo-Pe-Ve-Sa." Instead of the natural 3 letter minimum, we find 7 letters in Aramaic text passed by history. So this is the spelling that shows up in the names Lexicon for Philip in the NT.

Every other letter, so 3 of those 7 letters, are functioning as an added vowel. There is also a final Paleo Sa letter which does not currently get pronounced. That final Sa does not transmit into English translations of the NT. We know this character as Philip not as Philipus.

I don't yet have the NT text through audit. But, if Paleo names across the OT and NT are similar, then names like Philip should reduce to 3 or perhaps 4 letters, Someone probably added 3 or 4 letters to this name.

They were adding vowels because they were using Aramaic letters to override whatever they knew as the default vowel sounds for this name. The 3 letter version of Fe-Lu-Pe is pronounced "Feeloop." These vowels are not the same as we know for Philip. This is an example of what inspired writers were doing to all names. This limited power of the Paleo vowel sound system is what the scribes doing the uplift were fighting.

They probably added 2 copies of Yo to the basic name. Yo, by the way, seems to very commonly be used to mark an "i" in names. "Ve" is commonly used to mark a "u." The "Sa" ending is applied inconsistently. Some NT names use this as a suffix, some don't. So the paleo version, with 7 letters, so Yo as i, comes to English as "Pilipus." By convention, outside of the spelling, the first Pe is the f sound. The second Pe is the p sound.

This suggests, that the ancient pronunciation on Philip was probably "Pilip." The Ph shift presumably came later than first century.

When the Aramaic texts were uplifted to match Ananias' edited Greek, these sorts of things were going on at a linguistic level. Unnatural vowel usage appears to be the final result. Nearly every name that was not already in the OT has this going on.

The OT names are not that unnatural to us because we only know the names as given in the text. We don't know what the street pronunciation was for names like Jacob, Noah or Enoch. The NT is unique in this problem.

Linguistic Clues

This is the work that was probably going on in the 100s. This is what creates the "Greekisms" that modern professors of Aramaic can call out. Most Greek names, when viewed in Aramaic, look like loan words that have been respelled in order to capture specific vowel sounds. These become at least 1 class of Greekisms. I can see that pattern myself. I can see that same pattern everywhere across the NT names lexicon.

Work Plan

Almost every name across the entire text appears to have added vowels. I can identify this pattern by counting pronounced syllables in English versions of names.

So the work item that naturally springs from this is to run the audit against all names. The general odds of passing audit get better as the length of the name goes down. Pe-Lu-Pe stands much better odds at passing audit than does "Pe-Yo-Lu-Yo-Pe-Ve-Sa."

The next step is to attempt to audit otherwise short sentences that also include names. These combinations should shake out added vowels across the lexicon itself.

This is the work item ahead, hopefully soon. More later.

Match Dates

We were watching this past Wednesday, so 2026-08-26, for something related to a prophetic replay of the coronation of a new king in Samaria. This was a northern king, so what is now Europe and the USA.

The main headline for this date appears to be US CIA director Ratcliffe making a strange trip to Moscow on Tuesday, the day before. Think of Ratcliffe as a new king, suddenly making an appearance on the scene, so matching the expected story.

Ratcliffe is thought to be the actual man in charge of the war in Ukraine against Russia. He is most likely still working for others, say Zionist bankers, but anyone higher than him will be outside of standard government. The CIA itself is part of the shadow government that runs the USA. It is also the biggest state sponsor of terrorism in the world.

Earlier diplomatic trips have involved meetings with Russians. Perhaps the most well known was the trip to Alaska where Trump met with Putin. Most reporting from nearly all such diplomatic contacts have involved the west wanting a cease fire in Ukraine so that the west could rearm Ukraine in order to continue the Ukraine war with Russia after rearming.

It has taken awhile, but Russia are now wise to that ruse. Russia will not stop their side of the war until Ukraine either surrenders or falls to the Russian army. The Russian military is on the advantage.

Ukraine is not expected to have winter heating in most apartment blocks, nor electricity, this coming winter. War may become nearly impossible to fight on the Ukrainian side as soon as it gets cold.

Adding a little complexity, Putin is up for reelection in September, so he is being unusually careful with how he deals with the Ukraine war in order to not upset that vote. He appears to be avoiding sound bites that could be picked up in the election coverage.

Showmanship

Ratcliffe is interesting because he has not been overtly involved. So this is a new king. A peculiar feature of this trip was the use of a C-17 military transport. This generated interesting social media videos. This large plane also carried the vehicles for a motorcade that drove into Moscow. This is also more public performance. There was video of American license plates on those vehicles.

Ratcliffe clearly wanted to be seen. He wanted the world to know he was there.

The Ukrainians had stopped attacks on Russia for 3 days in order to allow this trip. (So through the prophetic date, more confirmation of the prophetic match.) Normal diplomatic missions, say earlier trips with Kushner and Witkoff, would use a corporate jet. Not here. Ratcliffe was most likely putting on a show for his banking bosses.

Subject?

Commentary on the trip suggested that Ratcliffe was probably again trying to threaten the Russians into a cease fire of some sort. Depending on the source, there is dispute if Ratcliffe met Putin or not. Russian media said no. Some alternative media says yes, but that Putin only gave a 1 sentence answer, no.

Other commentary indicated Ratcliffe was threatening Russia to cut ties to Iran. As the Ukraine war and the Iran war are 2 fronts on the same war to conquer the world, this was probably also discussed. But this may be deflection. Russia does not appear to be key in Iran. China is more central to supporting Iran than Russia.

Follow Up

There were also reports that Ratcliffe returned to DC after his visit to Moscow. He is said to have spent 3 hours at the White House, briefing other officials over how the trip had gone. If Ratcliffe is really the man running the war, he may have been giving directions to the US side over what happens next.

Ukraine has serious reasons to be worried over winter. There are now more stirrings across Europe over the need to get involved in Ukraine. The UK just relaxed their 3 percent ceiling on defense spending in order to fund their own war against Russia. The UK, prophetic Babel, should take the brunt of the war once Ukraine falls.

Watch Dates

We are now clear of known prophetic dates through 2026-10-02, which will be the end of Jotham's reign. Until then, we look for a king living in seclusion, and any possible headlines related to nuclear related weapons and related threats.

Perhaps Ratcliffe was threatening Russia with a nuclear strike? Or clandestine use of small nukes? If so, we won't know those details until the war is over.

Shop Work

We had a short regular work week this week. I have been working on more code related sanity checks in the Names Lexicon. Seems like every time I touch the files, I find more problems. No updates to the Paleo Bible this week.

Headline Review

The following caught my attention this week.

Star Base Louisiana

Full News Conference

The top link here is to a 13 minute video by Ellie in Space on Youtube. She reports on SpaceX's recent announcement of opening up a huge new space port on the gulf coast. In a previous blog, I linked a video about how this might happen. Now it is official.

The bottom link is the full 38 minute news conference where this project was formally announced. It includes the various speeches by the VIPs.

The top video is Ellie In Space's 18 minute report on the same event.

Immediate work is on remediation of trouble with eroding shorelines. 12 launch pads are planned for 125,000 acres. This is expected to become the largest space port in the world, with a planned capacity of 30 launches per day. The facility is expected to employ around 10,000 people. It is expected to cost $100B.

The second video includes Gwenn Shotwell's full speech for SpaceX. It also includes a couple minutes at the end dealing with what the state did to make this possible. Impressive.

This is the "Dot" location on the national USA Qu Map. Enoch, who was taken to heaven, is the angel who goes with this location. This is a major addition to the general Qu Map for the USA. Earlier examples at this same Qu Map location include fabrication of solid rocket boosters for NASA. This new project is just another step on a space related continuum for this location.

Ratcliffe to Moscow

Duran Commentary

Natural News Long Article

The top link is one of the early posts that marked Ratcliffe's trip to Moscow. The 2nd link is Duran commentary on Youtube with what was likely going on. The 3rd link is to a long form article on Natural News dealing with the same trip. The Duran video is the best. It provides reasonable commentary on what may have been going on. (I am, of course, more conspiratorial, since the villains always want to hide.)

Japanese Nuclear Weapons

The link here is to a post on Telegram citing a Russian official that suggests they expect Japan to have nuclear weapons within perhaps a year.

This is in the theme for the prophetic stories active through 2026-10-02. Work towards Japanese nukes would make sense given the history of Japan and the prophetic stories going on now.

Koreans Worried Too

The link here is to a brief post on Telegram by Tass suggesting the Koreans are also worried about Japanese remilitarization.

Operation Outcast

This link is to a Sonar21 long form article detailing the announcement on Monday, August 24, 2026, that the USA was going to sanction parties involved in trade with Iran. Because Iran is mostly self sufficient, external pressure has little leverage. Internal self sufficiency also means Iran's purchasing power parity is not that bad. This new set of sanctions is not expected to fundamentally alter life in Iran.

This particular headline is an alternative fulfillment for the date this week.

No Strikes, Mon, Tue, Wed

This link is to a post on X with the details of no strikes on Russia by Ukraine for Ratcliffe to travel to Moscow. This stretches the window for at trip onto our expected watch date of Wednesday.

Lake America

Trump signed an executive order changing the name of Lake Ontario in USGS government documents to be Lake America. This is a game called "Name it and Claim it" also known as "Blab it and grab it." These are power plays of gangsters. Presumably the next president, if there ever is one, will undo these things. Trump appears to be mentally ill. He is also suggesting the renaming of the oceans as well. Presumably the Pacific becomes the "West America Ocean" and the Atlantic becomes the "East America Ocean."

Washington: No MoU

This link is to a TASS post on Telegram. It notes that "Washington" is no longer interested in the MoU. Trump signed it, just like he will rename the Pacific, by stroke of the pen. So now he changes his mind? Trump appears to be a looser in more ways that 1. How can anyone trust anything he ever signs?

Not Only Ratcliffe

This link to a post on Telegram is a reminder that there was also a Vatican official in Moscow the same day as Ratcliffe. Unclear if connected. This post cites Lavrov. No publicly released clue from the Russian side about why these were in Moscow.

Starship Rescue

The link here is to a Youtube video from the "Whats going on with shipping" channel. It deals with getting SpaceX starship 40 out of the ocean and onto a larger ship for the trip back to Texas. There are times when SpaceX does stuff that is just inspiring.

More Later,

Phil

Balaam

Phil Stone — Fri, 21 Aug 2026 20:34:54 GMT

This blog looks at the story of Balaam given recent changes in our understanding of OT divine name references. Also, this week, has a flurry of technical updates to our apps. Then watch dates and a headline review.

Divine Name

Last week's blog went through our discovery process related to the name Joshua as used in the Old Testament. I highlighted the story of Daniel in the Lion's Den. In that story we learn that Joshua is not a god nor is he a man.

Texts as passed by history have been tampered. So this point made in Daniel is a relatively rare contradiction against most other references to god in the OT.

References to Joshua appear to have first been scrubbed by Solomon, who would have replaced Joshua with Yahweh. Many of those Yahweh references appear to have been moderated and/or scrubbed again by Ezra.

There seems to have been a fight between editors over which god they wanted to win. So unpacking and fixing the text is not easy. It is a layered problem.

Ryan is making a pass across the OT text to make a guess as to the likely original inspired divine names. He is following screen shots from Tabernacles. The audit work will make a second pass across this same problem, probably later this year.

What is emerging from this study is a version of the OT that is similar to the feel of the NT. Joshua becomes the agent and driving force for most of the events across that early part of the canon.

Salvation Stories

We also start to find the equivalent of salvation stories, like we see in the NT. Ultimately the entire book appears to be about the process of coming to faith in Joshua. This happens initially with famous families, especially around Abraham. Then it begins to increase in numbers.

The story of Balaam is a particularly interesting early example. The reason this story is interesting is because he is outside of the family of Jacob. So the story of Balaam shows off a missionary aspect to the OT that is lost under the hand of the editors.

Balaam

The link here is to the start of the story of Balaam in the TT. Note this is an unstable link. Readers of this blog in the future may find this link does not work. The story placements are not yet finished in the TT. This is why I don't normally link into the TT app itself. For future readers, use the TT search function for the term "Balaam."

The context of this story is that the heirs of Jacob are now assembling on the eastern shore of the Jordan river. This is in preparation for crossing the Jordan into the land promised to Abraham. Within the historical narrative of the text, this is the time of "peak faith."

Joshua is interacting with and geographically moving the largest numbers of believers found anywhere else in the text. Moving this same general community to Rome at the Assyrian Deportation probably involves higher numbers. But those numbers are only a guess. Rome was not settled by a faith community as we see here.

The census counts from that era suggests over 600,000 male heads of households. So a general population pushing perhaps 2,000,000. Many of these people will become "walk offs." It is possible the Revelation count of 144,000 applies to this same generation.

This is the first major group who will return to Eden. Before this point there has only been a few who left earth alive. We don't know numbers for New Testament believers, but if there is a larger number, then only the New Testament would match this time.

Balaam

So within this context we find the story of Balaam. Balaam is an "interpreter of dreams." This profession is probably something like the "Wizard of Oz" in the 1936 version of the movie by the same name. Balaam has a fee to put on a show where he curses the enemies of kings. His actual ability is probably mostly in his theatrical abilities. He puts on a good show.

In this particular case, Balak, king of the Moabites, wants Balaam to curse the heirs of Jacob. He sends for Balaam. Eventually Balaam is going to put on his normal performance. He will do this 3 times.

In those 3 times we watch as Balaam has an encounter with an angel of Joshua as well as several prophetic words from Joshua. Note we have started using "angel" in the TT text again. This term implies a heavenly messenger. Use of the term suggests we are seeing a cameo of some earlier walk-off. At this point in history there are not very many choices. Enoch, Noah and then Abraham and his close family members are the only known possibilities.

By the 3rd time Balaam puts on his show, he gives up the theater and just speaks prophetically about the future of many of those people. His 3rd round is showing us when Balaam has come to faith.

Note that getting attention from an angel is usually because the person being visited has come to the point where they are ready for a faith walk. Angels don't usually spend time with anyone who does not matter. They want to include Balaam as part of that generation's harvest of earth.

Balaam's Use of Terms

At the start of this story Balaam is likely using the generic term "god." Ryan is making a well educated guess as to what the audit will likely show. Remember, by definition, god is an "imaginary shepherd." This term implies no actual agency. Perhaps the only spiritual beings outside of Joshua's normal cohort are the souls of dead people. We would call them ghosts. The text might call ghosts "spirits" or "demons." None of those terms are active in this story.

The first night out, Joshua speaks to Balaam and warns him not to curse the people who are blessed. This is an example of a very common pattern. Joshua speaks to someone even though that person does not know Joshua. This is a key point. Joshua reveals himself to people who do not know him. Those people must figure out who is speaking. Balaam is a textbook example. Balaam will still use the term "god" even after Joshua has spoken the first time.

Part of the process of coming to faith is to come into agreement with the things Joshua is doing in the world. Balaam starts out just putting on a show for the king who has hired him. This is the context used to correct Balaam's understanding of what is going on around him.

By coming into agreement with what Joshua is doing, Balaam is coming to faith.

Balaam's Donkey

Ryan has restored into the TT the story of Balaam's donkey. There are no particular filter rules that would automatically rule out this story. A talking donkey, though strange, does not fail by any known filter rule. Nowhere does the text say animals cannot talk. Anyone who has had even a pet cat knows that animals understand their world and can communicate.

In this story we see an angel of Joshua interacting with Balaam. First via the donkey, and then directly and in person.

In a normal read of this story, the main lesson appears to be that curses have power, and the angel is stopping the curses. An alternative here is that Balaam is ready to come to faith in Joshua. So the angel of Joshua is engaging Balaam for faith based reasons.

Evidence for this latter understanding is that Balaam is the likely witness to the story itself. He is likely going to join the community of Jacob. This is how his story is added to the canon of scripture. He is the only actual witness. Balaam is thus likely to become a walk-off, just like so many others in that generation.

So what we are reading in the story of Balaam's donkey is the salvation story for Balaam himself. This is his testimony. His behavior towards Balak and his prophetic words over the heirs of Jacob change dramatically after Balaam's conversion. Paul's encounter with Joshua on the road to Damascus is similarly structured.

After the encounter with the angel of Joshua, Balaam likely starts using the correct term, Joshua. He is no longer using a generic term like god.

Balaam still puts on his usual show, wanting 7 altars and related sacrifices. This is his second performance and he is still operating under the patterns of his old practice.

This is an example of the route to faith. Many people seem to go through this. There is a focus on the rituals learned before faith. Those rituals eventually drop. All that remains after that process is just a walk with Joshua.

You can see this in the Balaam story where he is taken to mount Peor. This is the final time he is called to curse. At this point he has no need for a ritual. Why? Because ritual has no power.

This final time is when Balaam knows this people is blessed. All he can speak is a blessing. Balaam has come into agreement with Joshua's plan for that generation.

Purpose of Editors

The process of coming into agreement with Joshua's general plans is important. It is closely tied to the process of coming to faith.

When we understand this problem, we can then see why editing the text was such an important target for those who are against Joshua and his ways in the world.

Even back in the Garden of Eden, the question posed was "What did Joshua really say?"

So by editing the text, the basic frame for coming to faith was broken. With edited text, it is not strictly possible to come to a "walk off" level of faith. Even watching, and trying to understand, modern headlines surrounding Israel is caught up in the process of editing the text.

Is Joshua going to set up a world capital there? Or is he going to use a right of revenge to avenge the crucifixion? Answering this depends on what tampering was done to the text. There is no good way to pick sides, so no good way to achieve walk off faith.

Balaam is just a first example. There are many other now interesting stories in the OT material. We will return to more in future blogs.

Diary Work

In previous blogs I explained how the Story Grid app got updates to the aside library in our build environment. That work spilled over in to my personal diary app. By the time we were at the campground for Tabernacles I was seeing bugs in my diary related to those changes.

Once we were back home, and rested, I realized I needed to just go fix the diary. We are trying to operate under a "quick iteration" strategy we learned from Elon Musk. I really needed to just stop other work and fundamentally fix my diary. So, I set out to fix everything that bugs me with my current diary keeping system.

File Formats

I have been keeping an electronic, written, diary for about 24 years. This week was the first time I needed to fundamentally change file formats. This is tricky because there are now 4,457 different diary entries.

Those files cover many things. Like any normal diary, I keep records of travel and dreams. But I also include both personal and group lots. This is my main tool for understanding how Joshua interacts prophetically with people.

In surveying those files, I found there are 22,906 cited individual lots entries. We have been doing lots for a long time, and in that process we have learned a lot. (Philologists have puny humor.)

Some of this file format conversion was done by code. Some was done by use of "regex" tools in a text editor. Ryan is proficient with advanced regex tools because of his handling of Bible texts. He helped with some of this conversion.

Code Into the Diary

This update also meant shifting code around. There is a git repo for diary entries and another for the app. The diary entries repo never had running code. Now that project has some build time code.

This new code cleanly generates future watch dates and it validates things like Bible cites. For big sets of files like this, having code check files for correctness is nice. But adding such checks usually creates a long list of items that need to be corrected. 24 years without validation meant there was a mighty list of corrections what were needed across many entries.

Some issues were caused by how we used Book Order Bibles for lots in the early years. Those did not have normal Bible cites. In the early years, we also did not know what really mattered for future reference, so diary entries that involved lots were more complex than currently. All of those strange lots related Bible cites were corrected this week into standard cite formats.

Calculated Watch Dates

I have recently started using special markup to call out future watch dates. I originally did this calculation by hand. That markup needed code to make it run. This week I rewrote that personal watch date calculation code because I now understand the problem better. By changing the main file formats, the new code has much less file format conversion. Generated files are now built using templates, which is much easier.

What I am learning through this work is that Joshua speaks through personal lots about future dates that will be interesting. Most commonly, those future personal watch dates mark the topics that will show up in lots on those future dates. This is profound. Joshua actively cares about personal soul development. The story of Balaam becomes a common pattern. Joshua interacts with us in stages across our life. If you let him, he will speak to you about what he is doing with you, and what he will do with you. He has a plan.

Personal travel lots, say lots at the beach, will tend to fulfill with more personal travel lots, say lots at a campground. Joshua orders our steps. He knows our future schedule. He is willing and able to reveal that schedule. All it takes is the right tooling to see it.

Archive Data Problems

Diary data is considered "archival." This means that the data in a diary is valid for many years. In my case, 24 years already. I cannot see how this could be done as a service. The life expectancy of all businesses is under 7 years on average. So this work is not something I would currently see as something I could make available to others, at least not to anyone not able to maintain the system themselves.

More Tech Updates

As I was working on the code that calculates future watch dates I found myself using the same file name patterns as we use across our apps. Anyone who has built websites knows the use of index.html files for pages in those sites. We also use article.html for articles in web apps.

The diary's common file name was switched from article.html to aside.html because diary entries are now displayed as asides. For the diary itself this was a simple conversion from article to aside. But, this triggered a round of work in our basic libraries to make asides into a more formal, first class, element.

So this week we went through and revised all of our apps that use asides of various types. All of them now use aside.html as the basic file name whenever an aside is being used. This cleans up a considerable number of places where aside file names were irregular in our apps and code.

Besides the Story Grid stories, we are now ready for much more use of asides across our apps. The lexicon in the Paleo Bible app will soon be running with asides as well.

Style System Updates

This week Ryan has also gone through a scrub on the style sheet system used across our apps. This is something he wanted to do for some time. It made much sense to combine this with the changes made to asides.

Most apps in our family of apps have been updated this week with these changes. Please use the contact form to report any bugs that might have been introduced this week. We do not intend to introduce bugs, but bugs happen.

Names Lexicon

I have finally been able to resume lexicon work. I remain focused on the names annex to the lexicon for the Paleo Bible. I am in a round that is identifying the roots and prefixes for all the names used across the manuscript.

As part of this work I am concerned about keeping the files clean of copyright infringement. So part of this work is being done outside of the Paleo Bible app itself. This allows some scaffolding code for building the lexicon that uses otherwise copyrighted names.

There is a step coming up soon, probably next week, where the current work will get injected into the main Paleo Bible project. That step will only include material that I have actually created, so typed, myself. The scaffolding that ties back to other, copyrighted, text will be left behind.

For the purposes of English, at this round, I have invented a notation that explains how to pronounce paleo names given paleo spelling. But, it minds the conventional syllables found in English language names.

This undoes the shibboleths created across history and it compensates for irregularly added vowels. The net effect of this notation is to show the likely inspired pronunciation for all names found in the text.

That notation is not absolutely fixed, and will be updated as names go through audit.

By the time this blog goes out on Friday afternoon, I should mostly be done with that work across all known names. This probably hits the live Paleo Bible app by next week. We'll see.

Major Events This Week

There have been 2 areas of interest in headlines this week. The first involves oil market pricing. The second involves trouble with the US Federal bond market. Both of these appear to be impacts of Trump's failed war against Iran that started February 28, 2026. If we have correctly identified Iran, that country should ultimately win against the west. But it should take a few more years to play out.

Iran's current strategy, of keeping Hormuz mostly closed, is asymmetric warfare against the funding engine of western hegemony. That strategy takes time, but it is working, as headlines this week indicate.

Oil

For several months there has been pretty regular "2:00 AM" slams in the oil futures market that have been holding down the price of oil. Trump's own rhetoric against Iran was timed for weekends when markets were closed. It was clear the US Federal Government was managing oil markets to minimize the natural price effects of Trump's war with Iran.

The problem with manipulating down the price of oil is that it does not shed demand. So those areas of the economy where oil is valuable and important do not get the now limited oil instead of areas in the economy where oil is discretionary.

This is a fancy way of saying that the US Government is artificially creating an oil shock. The question has been when does that hit? Early estimates were suggesting this would start this past July. Those early estimates did not properly cope with government intervention.

What became apparent this week is that the market based price discovery has naturally shifted to the markets for refined product. "Crack Spread" is a measure of this. This past week, this number reached an all time record high of $102 per barrel for diesel.

So there really has been a price based demand shedding process. But that process has not been in the prices paid to producing countries, but instead to refiners.

This is curious because it changes who gets the profits from scarce oil. Instead of profits to the drillers, so the GCC countries, this shifts profits to domestic refiners.

The US Federal Government appears adept at shifting revenue to itself and to certain tax paying domestic parties. At the same time, this is shedding demand, which is good. It is shifting crisis level shortages into this coming fall.

If Iran can keep Hormuz closed, the stored reserves in the western world will eventually be used up. Though there is a race to see if the west can spin up other sources of supply. Venezuelan oil is said to now be flowing to the USA. There have also been reports of Trump affiliated drillers exploring in Greenland. The race is on to replace Hormuz if that is at all physically possible. The prophetic stories over Iran suggest this is only marginal and will not ultimately matter.

At some point western economies should suffer more severely than has been seen so far. NATO damage to Russia has caused Russia to stop exporting diesel. Europe is expecting worse trouble than North America.

Weaker economies, like Japan, will have more trouble. Oil shocks will be more severe in weak economies or where oil is a pricey import.

US Treasuries

This week the total US Government outstanding debt crossed the $40T mark. That number is mostly symbolic. But, the rate of increase is increasing. By the end of 2026 it will probably pass $41T and may pass $42T. This number looks to be starting to turn a knee. It will increase faster and faster each month until the USD is worthless.

This much debt is causing trouble in the bond markets. The US Treasury failed to sell long dated bonds. So instead the US Treasury is selling short term debt in order to refinance long term debt.

This is a bet that pays off should interest rates fall in the future. Interest rates are in part a measure of confidence in the issuing government. Loosing a war against Iran is a way for the US government to loose confidence. The bet being played now with short term bonds is likely to fail.

Trump is now basically on a continuous campaign trail in order to boost confidence in the government itself. His personal brand has failed. So only a change in the office might restore faith in the government.

Japan

The Japanese government holds $4T in US government bonds. This is about 1/10th of the outstanding issuance. Many others have borrowed cheap Japanese currency in order to buy US Treasuries. So trouble with Japan's government finances and currency is a big risk to USA hegemony around the world.

Japan's key role in financing the US government appears to be the result of the Japanese loss of World War II. China was also used for this purpose. Nixon's trip to China was in part to setup China as a buyer of US Treasuries. But China has a stronger economy and has shed treasuries as a component of their central bank assets. This leaves Japan standing alone.

Japan has been the subject of financial related prophetic words for decades. The key idea is that collapse of US economy will be foreshadowed by a collapse of the Japanese currency. That collapse has been underway for a few months. Intervention to prevent collapse was attempted again about 2 weeks ago. It worked for about 2 weeks.

We seem to be on the leading edge of the fulfillment for those prophetic words. Japan remains in play through early October, 2026, because of the current king's reign. Let me explain.

Watch: Uzziah/Azariah

We are currently in the replay of the reign of Uzziah, also known as Azariah. This began on 2026-08-12. It runs through 2026-10-02.

At some point during his reign, this particular king was struck with leprosy and had to live in a house in seclusion until the day of his death.

This leprosy is known as the plague of boils from the Plagues series. In that plagues story, something like ashes from a furnace are cast into the air. They become fine dust which breaks out as boils.

Note that the type of ashes that break out as boils are the ashes from nuclear fires. This happened in Japan at the end of World War II. Current financial troubles in Japan that are transmitting into the US Bond market may be the main headline for this king's reign. This would then become the headline match for this plague. A financial fulfillment would be better than the actual use of nuclear weapons.

Real Nukes?

But, also worthy of note, is a nuclear weapons headline. On 2026-08-17, so 5 days into this prophetic king's reign, Marjorie Taylor Greene posted on X that there had been discussions, apparently in the previous week, in the White House, about using nuclear weapons against Iran.

So her X post is pushing actual discussions about nuclear weapons back to the start of the reign of Azariah. This would be the missing headline for that date.

Should Trump follow through on this, we might expect such weapons to be used before the end of this king's reign on 2026-10-02. Should he use such weapons, the prophetic story suggests Trump might not ever be able to go out in public again. Best case, he would be forever booed off any public stage.

When Ryan and I ran the plagues against the kings, we had a secondary date of 2026-09-22, which provides an alternative date about 10 days before the end of this reign.

Northern King

There is a note in my records that Jehoahaz, a northern king, will start a replay in this time. The math for this date lands on 2026-08-26. I was not tracking northern king dates in July of 2002 when this would have replayed previously. So unclear if this should trigger a headline or not.

So we have a speculative watch date for the Wednesday after this blog goes out.

Peeking ahead, the Assyrian Deportation replays 2026-11-09. This is where we would look for the most severe headlines later this year.

Headline Review

The following caught my attention this week.

Meeting In Egypt

This link is dated to Aug. 17, 2026. Kushner was visiting Netanyahu in Egypt for a meeting with Hamas. Netanyahu is said to have founded Hamas. Now he is dismantling it as part of the conquest of Gaza. Trump's handler was in the room for this meeting.

Trump On Nuking Iran

This link is to the original X post that leaks discussions where Trump wants to nuke Iran.

$40T Graphic

This link has a nice graphic of outstanding treasuries passing the $40T mark. You can see the shape of the curve bending up. This curve's shape is the most important part of this headline.

Economic War With Iran

This post has a copy of Trump's social media post where he says he is shifting to economic war with Iran. In decades past, the USD was the world's reserve currency. No more. So this war will be hard to fight with an ever weakening hand.

Economy Collapsing

A link to a post on X with a short summary of the trouble that the US Treasury is facing. Current actions are setting the stage for much worse later.

Japan Currency Bailout

This link is to a Patrick Boyle Youtube video with details on the recent Japanese currency bailout.

Catholic Banking History

Glenn Diesen had professor Hudson on as a guest to discuss financial issues related to the wars. Hudson started by surveying the content from an upcoming book on the early history of European central banking.

This is a bombshell video because it ties the banking cartel of Europe to the history of the Catholic Church. This level of detail and how it stretches way back across history was very much news to me.

This explains why western Christianity is so tied to Zionism. Zionists were bankrolling the Catholic Church as well as nearly every government in Europe. This went on for most of the history of the Catholic Church after the split from Orthodoxy.

Jerome's switch of the Latin OT to Hebrew can now be seen in the context of the Jews taking over western Christianity. This is much more circumstantial evidence that the manuscript change behind the western edition of the OT was deliberate.

Hudson's upcoming book should be interesting.

Israelism instead of Christianity

The link here is to another recent article on this same point. This one by Ron Unz. He contrasts how Russia is Christian while the USA is not.

This is odd, since only 85 percent of Russians are of Christian heritage while 95 percent of Americans are of Christian heritage. Again, this is the result of Jewish forces working against the natural Christian culture.

Bond Intervention

The link here is to more background information on US intervention in the bond market. This is a Monetary Matters Network video on Youtube. These young guys don't get evil. But, they do get the narrowing window for US Treasury intervention. They also see gold eventually regaining its rightful place as a reserve asset.

More Later,

Phil

Lion's Den

Phil Stone — Fri, 14 Aug 2026 21:11:41 GMT

This blog is a trip report for our recent Tabernacles Week. The highlight was understanding what really saved Daniel from the Lion's Den. Also, app updates and a headline review.

Schedule

This year's annual holiday for Tabernacles started at sunset on the afternoon of Tuesday, August 4, 2026, and ran through sunset on Tuesday, August 11, 2026.

We had reservations at a campground on the shore of Mineral Lake, in Washington State. This is near the west entrance to Mount Rainier National Park. We chose this particular area because 20 years ago we had an encounter with a UFO in that same general location. Some long time readers here have seen photos and heard that story.

In any case, when we went to look for a campsite, there were not many that had availability for a tent site for the whole scheduled week. The only one we could find in the area that was still available for all of our scheduled dates was the "Lion's Den" campground at Mineral Lake. Since Mount Rainier is a very popular tourist destination, I would guess we needed to make reservations in January if we wanted better selection for campgrounds. The Lion' Club owns this particular campground. It is a low budget place. We were told most campers are there in order to go fishing in the lake.

The town itself was once a lumber camp. What is now the campground was once a lumber mill. There is a steam train that runs from Elbe, WA, to a spot very near the campground. We could easily hear the whistle. The steam shop for that train is also pretty close to the campground.

The campground has almost no trees, so there is a very nice view of the lake itself. Last week I posted on Telegram a photo taken from our campsite, for readers here who may want to see what it looks like.

The Plan

Our plan was to read through the current draft of The Testimony. That text has grown some so the reading schedule was a little aggressive. But there is not much else to do for the week, and we are into the text. We figured if we ran long, we would just finish up back at home in the shop. So it was a reasonable plan.

We got checked in on time that Tuesday afternoon. Our campsite was equipped with water and electricity. We were up from the lake and mostly alone, which sometimes matters for lots sessions. The toilets, modern concrete pit toilets, were about a football field hike from our campsite.

By Wednesday morning our tent and canopy were setup, we were settled in and our read through The Testimony began.

Major Discovery

In less than 1/2 hour into that morning's read, the major discovery of the week had happened. Let me explain the theoretical problem, and what turns out to be the actual solution.

Divine Name

Our biggest outstanding technical issue is how to deal with the issue of the Divine Name across the text of the Old Testament. In the New Testament that name is less trouble. In traditional Bible's "Jesus" is that name. We translate that name as Joshua, because the Aramaic spelling for Jesus is the same as the Aramaic spelling for Joshua son of Nun.

The Old Testament is much more difficult. The BRB has some notations which show where Ryan is making divine name substitutions. So he has been indicating were the name "Joshua" was likely originally found in the running text of the Old Testament. In the TT, the substitution is fully made, and Joshua shows up there as the Old Testament Divine Name.

Our discovery this Tabernacles week was a major advance on our understanding of that name. But, let me explain our understanding so far.

Names, of course, almost always transliterate between languages. Because Hebrew and Aramaic languages are so similar, names are also very similar. Indeed, names are nearly always spelled the same in both languages.

Curiously, and importantly, the Hebrew and Aramaic texts passed by history do NOT follow any of the normal transliteration patterns for the Divine Name. This is strange because normally both of those texts track names nearly perfectly.

That those texts would disagree on the divine name spelling is a major clue that there is foul play afoot. Yahweh in the Hebrew is something like Master in Aramaic. Master, itself, transliterates to "Maria" which is even more strange since it is nearly a known New Testament name.

That strange Hebrew/Aramaic word pair mismatch is where we substitute Joshua. We expect Joshua to be the term that eventually passes audit. That substitution already passes audit in the commandments and on the Shepherd's Staff exhibit.

Remember, outside of names, all other words are translated based on meaning. Titles go through a translation process whereas names do not. In the base text that we start from, the Divine Name, so by substitution, Joshua, is often followed by some sort of titling. "Joshua of Hosts" is an example. The most common title is god, as in "Joshua God."

What About God?

In English the term "God" is a technical term. It is NOT a name, so it goes through translation. The underlying Paleo root for this term is "Wa-Lu." This root is spelled the same in Hebrew and Aramaic, accepting different suffixes. So is it a technical term, as in English, or is it also name?

As we started into our read, from the very first few paragraphs, something dawned on me. Since that God term is spelled the same between Hebrew and Aramaic, it is behaving like a name, NOT a technical term. Certainly not like God is a technical term in English. Maybe this term should be added into the names annex for the Paleo Lexicon?

"Wa-Lu" is the root. "Wa-Lu-Fe" is much more common. "Elohim" is the normal English transliteration, with a conventional Hebrew final letter of Mo. So there is plenty of evidence that at least at times this IS treated as a name.

Considering this term as a name would then mean phrases like "Yahweh Elohim" becomes either "Joshua God" or even stranger, "Joshua Elohim."

Alf

Note that "Alf" is another, more strict, possible transliteration of "Wa-Lu-Fe." "Alf" was used as the name for a space alien character in a TV sitcom many, many years ago. Old time readers here might remember that character.

Since double names are a marker for editors, maybe the divine name Joshua is being followed by an imaginary, made up, name.

"Imaginary Alf" is what I voiced when I first started discussing this possibility with Ryan.

What I was proposing was that it is improper to add the name Alf to the name Joshua. I was beginning to think that an editor, like Solomon, probably did this at some time in history.

If this initial hunch was correct, it should be possible to read through the historical narrative of the Old Testament and it should be possible to only read "Joshua," without the term "Alf" and the story should otherwise make sense.

We started reading the text this way and it really started to pop. Joshua is the main agent in the New Testament. If his name is used alone in the old, without any sort of secondary titles, then Joshua becomes the main agent across all of inspired scripture.

In the end, dropping Alf will turn out to be correct. But there was another round of understanding still to come. This second round deals with the precise Paleo word definition for Alf. What, exactly, is a god?

Paleo Spelling

We have previously defined God, so "Wa-Lu" as the "first-shepherd." This because Wa is the first letter of the alphabet and Lu is the shepherd's staff. The secondary definition would thus be "Ta-Ku" so closes, or without, likeness or comparison.

But, Wa is a star. Though it has a 3d object, a sundial, for tracking time, the star itself is ephemeral. It is an idea. It is not a normal thing like all the other objects in the alphabet.

Understanding this nuance on Wa implies there is an alternative definition for the term God. "Imaginary-Shepherd" is perhaps the best English phrase. The secondary definition would be God "ends-growth."

This definition would imply that all gods are "imaginary shepherds." Having gods will stunt or end spiritual growth.

Note this is definitional, so there is nothing else that need be said. When the inspired writer uses this term, the god in question must be imaginary.

This would also strongly imply that Joshua is NOT a god. Nowhere in inspired text would we ever expect Joshua to be called out as a god. Certainly not by an inspired writer. Some character within the story might be doing this, but of course, incorrectly.

Joshua's name should thus always stand alone. We would never expect "Joshua God" nor "Joshua, God of Jacob" nor any other similar phrase to show up in author or narrator's voice anywhere in the inspired text.

So my first hunch at "imaginary Alf" was just pointing at the Paleo Spelling for "Imaginary Shepherd." That hunch was essentially a prophetic word pointing at the problem.

Dropping God

So we started in to proof read the Old Testament and started checking all the places where "Joshua" or "God" was showing up. "Joshua" as a stand alone, single name made much sense.

It also became quickly apparent that outside of what becomes Abraham's family, every other nation or people group have "imaginary shepherds" that can never take any real action in the world. Only Joshua is able to take real action. All gods, by definition of the word, are imaginary constructs. It is never proper to call Joshua a god. It is never proper to call him God.

We would eventually find a specific story that essentially proves this idea. But before getting to that story let me return to the campground.

Massive Edit

We were taking turns reading paragraphs and it was pretty obvious exactly where "god" had been added by editors when the Divine Name itself was being changed.

For the editors, the "god" term marks the highest level of spiritual being. There are fights within the text of who is the most important god.

There is a stereo type for old cattle ranchers. They often named their ranch dog "Dog." The same happens in the text. "Elohim" is happening when someone named their god "God."

Ultimately, for the editors, it is the "god of Israel" who is the highest spiritual being. The specific name itself is disputable, either Yahweh in the southern kingdom or Elohim in the north.

Solomon would be the first editor and he almost certainly changed the divine name from Joshua to Yahweh. Other editors would presumably follow along. Perhaps later editors add Alf to Yahweh? We don't know the exact history. In any case, it has been a very, very long time since Joshua was used as the divine name in public copies of the Old Testament.

Once we figured this out, each of us could read out in real time the corrected English that should be used when "god" was showing up in the text. People of faith know Joshua by name. Nobody else knows that name. No one who knows Joshua would call him "god" since Joshua is not an imaginary shepherd.

We were very quickly into nearly perfect agreement about how the inspired story must have originally been written. We could finally see through word level edits.

The Old Testament is going to read just like the New Testament. Joshua is the main agent across all of inspired text. Anyone who does not know Joshua uses "god."

Work Ahead

When we do reading like this, Ryan normally takes screen shots on his tablet and then uses the tablet's pen to mark the correction on that screen shot. He then comes back later to run through his list of screen shots which then drives updates to the master manuscript files which then show up in the apps.

Ryan was generating screen shots at a rate we'd never seen before. Divine Name references are common. All of them have been changed by editors.

Both of us were incredibly excited about how the entire manuscript should clean up once this editing pass is fully entered into the computer.

Distracted

In that process we lost our situational awareness. This was not good on hot summer days in a campground with a view of a lake, but without trees.

By Friday, we were both sunburned. Ryan was burned rather badly on the tops of his feet. He had been wearing sandals. The toilet was the better part of a football field hike from our campsite. Even if we stayed carefully under our canopy, we could not escape the sun when we went over there.

That evening we decided to break camp early on Saturday morning and return home. There, we could continue with our reading, but out of the sun and in the comfort of the shop.

By Saturday afternoon, we were now lifted out of the Lion's Den. By Sunday we returned to our read. We were off pace, but wanted to continue.

Beyond the historical narrative, the tampering of the editors gets more difficult to undo. Prophetic writings are particular targets for the editors because they involve personal stories of real people who knew and interacted with Joshua. Editors took the authority of prophets to create theology. So working through the prophets is more difficult than historical narrative from Judges and Kings.

There are places, though, where the prophets now suddenly make much more sense. Little did we know what was waiting for us in the Book of Daniel.

Lion's Den

The link here is to Daniel 6 in the BRB. This is the story of Daniel surviving the Lion's Den. Interested readers may want to read it themselves. You may also want to try some other translation, you'll still see what is evident in the BRB.

By Chapter 6, Daniel is working for the king. His peers do not like how well Daniel is doing. So they set a trap. They get the king to issue a decree. For 30 days, anyone who would petition any god, or any man, except for the king, would be thrown into the den of lions.

Daniel reads the petition and then continues his custom daily prayers to Joshua.

Nearly everyone who reads this story today, normally thinks that Daniel is ignoring this decree and praying anyway. This becomes a scriptural basis for why following god is thought to be more important than following kings. Modern readers think Daniel was rescued by Joshua as an exception to the king's decree. This is flat out wrong.

If you read what Daniel says when he is brought up from the Lion's Den you can see that Daniel makes a point. Daniel was not guilty before Joshua, which is why Joshua sent an angel and calmed the lions. Daniel also makes the point that he is not guilty before the king himself. Daniel is explaining that by praying to Joshua he had NOT broken the king's decree.

Why would this be so?

Daniel knows the definition. A god is an "imaginary shepherd." Joshua is not one of those. Joshua is also not a man. Since Joshua is neither a "god" nor a "man" Daniel was free to pray to Joshua as always. He did not break the king's decree. This is why Daniel was innocent. He was innocent before the king because of the definition of the word "god."

What we found in the Lion's Den story was confirmation of the story we had found at the Lion's Den campground. Joshua is NOT a god nor is he a man. To call him god is incorrect.

Son of Man

Even more interesting, the overall plot of the Book of Daniel hangs on this very point. The Book of Daniel is establishing the unique nature of Joshua in a chapter before it moves on to the nature of the incarnation which will happen for us in the New Testament.

After the Lion's Den, Daniel then introduces a term used to describe Joshua's incarnation state as the "son of man." This expression is used to indicate that he will be like a man to everyone who meets him. But, Joshua in the New Testament is not really a man in the most general sense.

More to Come

There are many, many other interesting stories which I expect to cover in weeks to come. As of this week, Ryan is through making updates to the TT covering material from Genesis and Exodus. More soon.

Assyrian Deportation

For readers here who may want to peek ahead, think about the story of the field commander during the Assyrian Deportation. That commander knows that gods are imaginary. He knows Solomon's temple is to Yahweh, so there is an imaginary shepherd in Jerusalem. He rightly makes the claim to the men on the city wall that no god had been able to defend any other city from from his army. The same will be true of Jerusalem, since Yahweh is imaginary.

What that commander miscalculates is the nature of Joshua who is defending a remnant in Jerusalem who still knows Joshua.

The overall story of the Old Testament is the history of the various remnants who know Joshua. Usually, this was only a few people. At times the remnant was measured in thousands. These are the groups that Joshua interacts with and defends.

Unlike imaginary shepherds, sometimes Joshua steps in and changes the flow of history. Most of the Old Testament narrative is about the places and times when Joshua stepped in and changed history.

For that remnant in Jerusalem, Joshua stepped in and defended Jerusalem against the Assyrians. "For the sake of David" is the expression. This marks the key soul in that remnant.

App Updates

As this blog goes out, Ryan is making a few other changes to our scripture app. Let me review those.

Story Grid

The link here is to the Story Grid app. There are 2 main adjustments to note. The first is that the row of content from the minor prophets has now moved up by 2 rows to the Ha row. This seems to do a better job of putting the prophets into something of a historical order.

Awareness of Joshua seems to ebb and flow across history. It peeks at the time of crossing the Jordan River. It never reaches that level of faith again.

It gets particularly bad when Solomon builds a temple to Yahweh. At the time of Solomon, awareness of Joshua seems to shift into small communities. The minor prophets appear to come from that era, when there are prophets around who can speak for Joshua.

Isaiah and Jeremiah are the prophets who pick up the Assyrian and Babylonian deportations. Daniel and Ezekiel are the last of the prophets and are found in the Babylonian captivity. So these prophets are now generally organized in historical order.

Prophetic Writing Trouble

I should note that in our recent reading, we found the prophetic writings are the most difficult to correct in terms of Divine Name. These writings appear to need a 2 step process. First, fix the Divine Name and then check if the containing stories make any sense relative to Joshua.

Editors appear to have hated some of these writers and their messages, so they significantly altered, so bulked up, that type of writing. Isaiah is particularly difficult. Though Isaiah is often quoted in the New Testament, there is no obvious plot. Isaiah may not be recoverable without the audit. Some of the minor prophets are similarly difficult.

Job

The other change this week is moving Job down by 2 rows. This lands him on the last row before the New Testament material. Fixing Divine Name references in Job also changes the plot, making that book very interesting. I will return to Job at some point in the blog once Ryan is caught up.

Job is following the Ne row. His early disaster is a seed planted. By the end of the book he has a double portion. So a seed like harvest. Job appears to provide amazing commentary on what it means to run a Joshua focused fellowship in an otherwise Zionist world.

Tobit, Esther and Job are the last 3 books of the Old Testament. They are taking place well out to the east, and not in Canaan. All 3 demonstrate faith in communities that are otherwise hostile. Tobit demonstrates a well lived faith walk in that sort of community. Esther, herself, appears to demonstrate how to live when nearly everyone around are sexual predators. If all writers sit in the throne room, then she has a well deserved seat.

These 3 writings become the context for the New Testament. New Testament era believers were also a remnant in a hostile environment.

Match Dates

Last Friday, so 13017-07-17 (2026-08-07) was the date that matches the 17th day of the 7th month at the 150th day as informed by Noah's Flood. I have previously indicated that we may have a 3 year advanced prophetic date series ahead of a Noah flood replay starting early in 2029. If this is correct, then last Friday would be a natural watch date. I had called it out earlier, but not in last week's blog.

The main headline for that date was the signing of a mutual defense treaty between Turkey, Saudi Arabia and Pakistan. This does appear to be an important headline match, but this treaty was strangely introduced.

It looks like the signatory countries did not release the text of the treaty in order to make it look like they wanted to defend themselves from Iran. So in this view they would defend themselves from Iranian attacks on US bases, especially in Saudi Arabia.

It was also strange that Saudi Arabia is in a low grade war with Ansar Allah in Yemen. Though neither Turkey nor Pakistan are coming to help Saudi Arabia against Yemen. So what sort of treaty is this?

Instead, this looks to be a mutual defense treaty in order to defend each other should they be attacked from Israel and/or the USA.

This view makes more sense. It appears to be preparatory to a larger regional war, perhaps 3 years from now, when Israel is removed.

There were no obvious headlines for the last year of Amaziah's reign on 2026-08-11, nor the start of Jehoahaz's reign on 2026-08-12.

Watch Dates

Peeking ahead, the last year of Jehoahaz's reign replays on 2028-08-26. We will return to that next week.

Shop Work

We were continuing our TT read from Tabernacles into this week. I expect to be back on the names related lexicon work next week.

Headline Review

The following caught my attention this week.

Russian Navy

The link here is to a post on Telegram detailing recent changes in Russian naval doctrine. From now on, Russia will respond in kind should the west seize Russian ships. This is an attack on the Lloyd's shipping insurance cartel in London, so prophetic Babel.

Russia is now pushing back on prophetic Babel over who controls the ships. Eventually, Babel is defeated.

Suez Moment

Many commentators are beginning to see how Trump has created for himself a situation in Hormuz that is similar to the 1956 war over the Suez Canal. This is the general 70th anniversary, when we would be expecting something like Suez to happen again.

Wikipedia CIA Controlled

The Wikipedia cofounder has been public recently about how the CIA and others are controlling content on Wikipedia. Hivites ultimately debate and hide truth. This has been a problem since Eden. Should we be surprised that this pattern goes on even now?

Chris Martenson on Oil

We continue to track closely the situation with oil. Chris Martenson is the best. He was a guest on another channel this week. Short answer is that futures markets are still being manipulated most nights in order to keep prices down, demand up, and using up normal buffer supplies. This is creating an unnecessary shortage. Major oil company CEOs are now warning of the problem.

X Continues to Falter

X continues to make algorithmic changes to allow Zionists to control the platform. The link here is another example. Masses of bad actors, say paid housewives in Israel, can effectively ban any account they wish. People of faith, so those who know truth, are always a remnant. X stands no chance of being a place for truth.

X Outright Banning

The link here is to a post on Telegram detailing the banning of perhaps the most important man in Yemen. Again, Zionists control X, that platform is not useful.

Trump's Catering Truck Fiasco

This link is to a Youtube video with Larry Johnson. This is one of many on the topic of Trump's return from the NATO summit in Turkey. Seems he boarded Air Force One as usual, along with his staff and reporters. Then he snuck out in a catering truck and returned to the USA on a military plane.

Trump is mostly being accused of cowardice over this. Other reports indicated the Iranian FM said that Trump is doing a nice job of destroying the USA on his own. Why would Iran want to take him out?

USS Abraham Lincoln Trouble

The link here is to a Sonar 21 article detailing some of the issues on board the USS Abraham Lincoln.

Initial reports called this a mutiny with 7 dead. Current reports are now toned down to problems with multiple suicides.

Citing sources, this article suggests the natural suicide rate is higher than the numbers currently reported, suggesting the current news accounts are false.

I strongly suspect the military is doing narrative control. We may learn more in 20 years when someone on board now eventually writes a book. Until then, we will never know for sure.

The US Navy is essentially part of the Babel Navy, so these ships should be plagued as part of the stories in Revelation dealing with the fall of Babel and loss of ships. So this is an interesting headline, even if not that severe in terms of loss of capability.

Russians Are Cat People

Survey says, Russians like cat videos too. Maybe Daniel's lions would be friendly to them also? Not sure if they get the Divine Name problem.

More Later,

Phil

Virginia

Phil Stone — Fri, 07 Aug 2026 18:29:35 GMT

This blog covers the founding and timeline for the State of Virginia. This clarifies comments in recent blogs about 2038. This is a component of possible future American history.

Precise Math

In several recent blogs I have hinted at how the series of headlines we are now in should finally settle down "about 12 years from now." I have also used 2038 as a general reference to that same general time. In this blog I fully explain the math.

There are 2 main prophetic stories that drive this timing. The story of the 10 Virgins in Matthew 25 will give us a date inside a time window in 2037. That story will also eventually lend its name to the State of Virginia.

Then, there is the story of Pharaoh's Egypt. That story, when measured forward from the founding of Jamestown, Virginia, will also triangulate into 2037. Once 2037 is over, we reach a "safe haven" time in 2038. Let me start with the story of the 10 virgins.

Ten Virgins, No Oil

The link here is to Matthew 25:1 in the BRB. This is in a series of end-times parables given in that general section in Matthew. In particular, this story involves wise and foolish virgins who have various troubles. This includes sleeping, keeping oil in their lamps, and finding a resupply, in order to be ready for a midnight visit by their bridegroom.

Conceptually, the timing of this story does not appear to allow an exact date. How should we place a term like "midnight" onto a general timeline of history? Midnight comes around every 24 hours. So once each calendar day. So this does not look like a story that could be dated.

Even more curious, the passage ends with verse 13 which teases the reader and demands being alert because readers do not know the exact time when that day will be.

So the problem is figuring out if there is any particular "midnight" that could be dated and thus matched to this story. At the same time we need to beware that there are likely tolerance or precision issues that may limit the answer.

The Process

The overall chronological story of scripture pairs prophetically with the public ministry of Joshua. His ministry days clock off recorded history at the rate of 30 historical years to 1 of Joshua's ministry days. This gives us a prophetic ratio of 30 years/day. (The 30 pieces of silver used to betray, or reveal, Joshua form the basis of this ratio.)

Given the 30 years to the day prophetic ratio, we pass a prophetic midnight every 30 years, but 1/4 of the way, so 7.5 years, into each of those 30 year long prophetic days.

Ministry Timing

The link here is to the Bible Time article that gives the dates for Joshua's public ministry. There is 1) The day of his baptism. 2) 40 days in the wilderness. 3) 390 days in a Jubilee year of favor 4) 3 days in the tomb. 5) 40 more days before his ascension.

Each of those ministry days maps out to 30 years in history. We are currently on Resurrection Sunday, the last of the 3 days in the tomb.

The current prophetic day, so the current 30 year interval, ends at the end of the year 13020 AA. We are currently in year 13017 AA. So about 3 years before we switch to the next prophetic day. That next 30 year long "prophetic day" begins on 13021-01-01 AA (2030-01-02 NS).

Midnight Math

So the story of the 10 virgins might be running on this same ministry schedule. It is a story about Joshua, so this is the first feature. The second point is that every single day in that ministry had a "midnight." Those prophetic midnights pass prophetically once every 30 years.

So what would be the next possible midnight beyond 13021-01-01 AA?

Midnight is 1/4 of the way through a calendar day, so 7.5 years through a prophetic day. Those 7.5 calendar years end on 13028-07-01 AA (2037-06-24 NS).

Triangulation?

The next step is to see if we can triangulate against this date. Can we find other stories that might confirm this timing?

We can do this with the story of the Road to Emmaus. We can also mostly reach this date from Jamestown, VA. Let me take each in turn.

Road To Emmaus

The link here is to Luke 24:13 in the BRB. This is the start of the story of the Road to Emmaus. This was on the afternoon of Resurrection Sunday. The story itself is measured as "60 furlongs" from Jerusalem. That timing likely means 60 years from "Jerusalem" which was formally reached by Jews in 1967. So this has a possible prophetic application next year, in 2027. Joshua starts to reveal himself at that point. Joshua is found raised at that point. The time when Joshua was in the tomb is over.

That story then continues. The crew that Joshua met on the road that Sunday afternoon, then runs off to tell others what had just happened to them. So if more of that story is still on a prophetic clock, then it points to events beyond 2027.

The rest of the Road To Emmaus story has unclear timing. Apparently, there was an after-dark set of meetings where Joshua met his gathered disciples. We don't know for sure if it was all of his disciples or only a few. We also don't know exactly the time of day when this latter meeting actually happened.

Match By Content

But, consider the content match between those late meetings after the Road to Emmaus and the story of the 10 Virgins. Both of these are on the topic of an unexpected encounter with Joshua at night.

So this meeting with the disciples might be the midnight we are looking for to match the 10 Virgins. It is a second witness to the next "midnight" in 2037.

Beyond those late Resurrection Sunday stories, there are not really any other documented meetings until we get to Doubting Thomas about 1 week later. For us that would be 200+ years later. So if this next 2037 midnight is NOT correct, then there are around 2 more centuries before we might try again.

Plague On Firstborn

The link here is to Exodus 11 in the BRB. This is the story of the final plagues on Egypt. The story itself gets to the term "midnight" at verse 4. Here Joshua indicates that he will plague Egypt at "midnight."

The story itself is setting up for a distinction that will be made. Some in Pharaoh's world will not survive that midnight. Others will survive and be taken to the promised land. In that case, across the sea, out of Egypt and back to the lands of Abraham and his family.

This story has similar content to the story of the 10 Virgins. Some will be ready for midnight, some not. This story of the midnight plague is a good textual back story to the main parable of the 10 Virgins. Content is lining up between these stories quite nicely.

Finding Modern Egypt

Placing a replay of the Egypt story on the modern timeline is something not easy to do. Where might Egypt be located? When was it first colonized? When would those 430 years begin? When would they be over?

We recently found some obscure answers to those questions. Let me review.

Virginia Beach

Over Unleavened Bread week at the start of 2026, Ryan and I traveled to Virginia Beach, Virginia. We spent the week there in an off-season motel overlooking the Atlantic.

We were nearly walking distance to the first reported landing of the original English colonists who then sailed inland and settled at what is now Jamestown, Virginia.

We took a side trip one day and drove over to the Jamestown visitor's center, not far from modern day Williamsburg, Virginia. It was a fun day. It was pretty cold, so there were not huge crowds. Friendly staff, bundled in heavy coats, were lonely and wanted to talk. We learned a lot.

For those who may not know the history, here is the key Wikipedia article about the founding of Jamestown.

Jamestown (Wikipedia)

That particular article has several other linked articles for those who may want to learn more. The most important idea is that Jamestown was established as "James Fort" on May 4, 1607 O.S. (May 14, 1607 N.S.). Jamestown was the first successful English colony in the Americas. From that date and place grew all the rest of the English speaking areas of North America. This includes later colonies in Canada.

James vs. Jacob

James is of course English for Jacob. Jacob is the family that went down to Egypt. Jamestown is a name match to Jacob. So setting up Jamestown is like settling Jacob's family in Goshen.

It turns out, getting established at Jamestown was not easy. You can read the article for some of the specifics about the trouble of setting up Jamestown.

Loss of People

The first group of passengers was about 104 people. All men. They departed with 105 and lost 1 on the way. We learned from the staff at the visitor center that most of the original colonists died the first winter. They had to learn how to grow food on swampy southern soils that was unfamiliar to colonists from cold, damp, northern, England.

There were later rounds of settlers measured in groups of 70. Jacob's family was also a group of 70. The second round of settlers was also only men. There were still heavy losses. The first women arrived later.

It is hard to even imagine how difficult life must have been for those early settlers. Very important to note, life at Jamestown was still way better than life in London. The same driving factors of Jacob going to ancient Egypt drove settlers going to Jamestown.

Prophetic Egypt

Before visiting Virginia Beach, we had generally thought of the USA as a type of prophetic Egypt. The Mississippi would be the match to the Nile. The style of Zionist political leadership matches the Pharisees of the New Testament and matches Pharaoh from Pharaoh's Egypt.

But by visiting Jamestown, we were seeing that by name and by numbers, the story of the founding of Jamestown was matching the start of the story of going down to Egypt.

Once we could see the founding fort, and dated history, it became a curiosity to see if we could time Jamestown as the start of the USA as a scheduled version of prophetic Egypt.

This math lands in late 2036, just ahead of the next prophetic midnight. Since Egypt also ends at midnight, we can now see prophetic triangulation. Let me show you the math.

Julian Calendar Query

The link here is to the Julian calendar tool page on the Bible Time website. This tooling allows conversion between calendars. It shows the Paleo Calendar for individual months in history. It shows months using a format called "date reports." These show individual days on various calendars. This is more complex than the common Calendar app linked off the front of paleo.in.

This report is the best way to look up the date for the founding of Jamestown. The URL link is already primed to the Julian month that shows May 4, 1607 OS, and May 14, 1607 NS.

By looking carefully through that report, it shows us that date was 12597-11-15 AA. The day number for that date was 4,595,295. The day number system is also in the Calendar app, so we can now move around by dates or by days from the founding of Jamestown just by using the calendar app. We don't need to keep using the more complex Bible Time tooling.

Measuring Prophetic Time

When we measure prophetic intervals across history we are always converting between prophetic calendar time and individual days.

The number of days in individual years is not fixed. Sabbath years and Jubilee years have 13th months. Depending on how some prophetic year interval overlays calendar time the total number of days will shift around.

Because of the structure of the calendar, the absolute error bound is 2 months. So unless we know what we are doing and why, we can be off by up to 2 months when calculating year intervals starting at any given day.

"Bond Man" counting always gives the shortest number of days. It starts a new calendar, so a "bond" or "contract" calendar at the date of the start of the interval. This form of counting does not care about the actual running calendar. It will reach its own internal Jubilee leap months only rarely. This is favoring the bond man himself, and minimizes the days of the contract.

"Calendar" counting just moves by date along the running calendar. It will sometimes match bond man counting, but not normally. Since calendar year counting rarely ends just after a Jubilee, it does not usually produce the longest number of days. Compared to bond man counting, there is up to 2 months of difference for the final answer based on the starting date and the number of years.

A special case of Calendar counting happens when the end of the interval is just after a Jubilee year. This produces the longest possible counts of days because it captures the leap months found in the 49th and 50th years of the Jubilee cycle.

Measuring From Jamestown

So, if we want to count days forward from the founding of Jamestown, we need to get our head around what exact counting system should be used.

Exodus 12:40-41 indicates that the total time in Egypt was 430 years. It then indicates this was accurate to the day. So time in Egypt was measured to the day. Let me show the 3 possible calculations for Jamestown. Then we can pick the likely correct one.

1) Bond Man Counting

Bond Man Counting begins a calendar at the start of the interval. So we want a stand alone 430 year calendar with the first day on the founding of Jamestown. This will minimize leap months and give us the shortest possible time.

430-12-30

The link here is to the paleo calendar app, primed to month 12 of year 430. We are using this to calculate the end of a 430 year bond. By inspection of the 30th day in that month we can see the total days is 156,840.

Jamestown was founded on day number 4,595,295 AAN. 430 years later using bond man counting adds 156,840 days. So 4,752,135 AAN is the day that ends 430 of these types of years.

It turns out to end on 13027-10-15 AA (2036-10-11 NS). This is 3 months ahead of Passover in 13028 AA. It is 5 days after the Resurrection Sunday annual holiday. This calculated end of Egypt is about 9 months before the next prophetic "midnight."

These gaps, especially to the Passover Holiday hint that we are short some number of months. This is expected when using bond man counting.

2) By Simple Calendar Offset

If we take the calendar date for the founding of Jamestown, we can then move along the calendar by 430 years and find the ending date.

So the date for founding Jamestown is 12597-11-15 AA. Adding 430 years yields 13027-11-15 AA (2036-11-10 NS).

This is 30 days after the date found by bond man counting. It is now 2 months before Passover in 13028 AA. The tail end of this interval is getting better.

3) As Lived

The original interval lived in Egypt ended just after a Jubilee. So it was the special exception which turns out to maximize the number of days in the prophetic interval. This form of measuring time suggests Joshua was waiting as long as he could before taking action against ancient Egypt. It represents a mercy delay.

To run this calculation we need to know the historical dates in order to learn the count of days spent in ancient Egypt. That date work has already been done on Bible Time.

Abraham To Exodus

The link here is to the Bible Time article that provides the chronological details and citations needed to show that Jacob arrived in Egypt in 9071 AA. The last full year in Egypt was 9500 AA. The Exodus itself would have begun at the Passover in 9501 AA.

So the exact calendar date of the "midnight" at the Exodus was 9501-01-15 AA. So backing up 430 years, the exact day of arrival would be 9071-01-15 AA.

How many days are between those dates?

Calendar: 9501-01

The link here is the Paleo Calendar app set to point at the month of the Exodus. Inside this calendar month you can find the 15th day, the day of the midnight plague. By inspection, you can see this was a Tuesday. The day number was 3,465,615 AAN.

Calendar: 9071-01

Same trick again. The link here is to the Paleo Calendar app set to point at the month of Jacob's arrival in Egypt. The interesting day was the 15th of this month. It was a Sunday. By inspection, the day number was 3,308,715 AAN.

You can do the math. The days between going to Egypt and leaving Egypt was 156,900 days. This is the longest possible day interval. It suggests the timing was set as a mercy delay against Pharaoh. This may be because Pharaoh at the Exodus was an heir of Jacob.

Jamestown Math, Again

Jamestown was established as "James Fort" on May 4, 1607 O.S. (May 14, 1607 N.S.). This was 12597-11-15 AA. The day number was 4,595,295 AAN.

If we add 156,900 days, the same day count as lived in ancient Egypt, we get day number 4,752,195 AAN. Poking around in the Calendar app we find this to be 13027-12-15 AA (2036-12-10 NS).

This is 1 month shy of Passover. That date will be 13028-01-14 AA (2037-01-08 NS). This is the date for the evening meal. The next calendar day, so 13028-01-15 AA (2037-01-09 NS) is the date of the holiday remembering the midnight plague on firstborn.

So think again about counting time from Jamestown. The time of arriving in modern prophetic Egypt at Jamestown, until leaving prophetic Egypt at an annual holiday of Passover, is only off by exactly 1 month.

This difference is so close that it warrants an eventual review of the known events at the Jamestown landing.

Did the ships and crew that brought the colonists leave after 30 days? If so, the math will become perfect over 430 years.

10 Virgins Are Warned

Thinking back to the story of the 10 Virgins, it warns that the precise date cannot be known. Readers are told to be alert. That warning appears to be indicating that we can only get a close calculation from other stories. We are being warned no accurate calculation is possible.

So the story indicates that we cannot fully calculate the exact date before it happens.

It looks to happen sometime in 2037. But it could be late in 2036, especially if there are headline matches that follow the Exodus from Egypt landing inside the USA.

This is all I can say with certainty. It should be over by 2038.

Though this is all I can currently say about time, there is more to say about the place.

State of Virginia

The modern location for Jamestown is of course in the US State of Virginia. The story of the 10 Virgins is matching Virginia by name. That state was named after Queen Elizabeth I, who was known as the "virgin queen."

By name, Virginia is matching the story of the 10 virgins.

By content, the 10 virgins story also matches the story of firstborn plague at the Exodus. So that also matches the timeline that started in Virginia.

So running a timeline based on Egypt from the start of that colony to our 10 virgin's midnight in late 2036 or 2037, we are now connecting the entire flow of America's colonial history to soon future events.

Virginia is also the starting territory of the lost tribe of Manasseh arriving in the Americas. This matches the history of Joseph going to Egypt ahead of his brothers. Virginia was ahead of the rest of the country.

Though the nation started in Virginia, the current capital is outside of the state. But, the Pentagon is inside Virginia. The Norfolk shipyards are not far from Jamestown. War is the main industry of Virginia. The wars that the USA are currently conducting are being driven from Virginia. The current war against Iran is being fought from Virginia. It is a war fought over control of oil.

Confederacy

One other component to this story that is worth considering is the role Virginia played in the Confederacy. It was the capital of the south during the War of Southern Succession. Of course that war was lost, and the Zionist victors rewrote the history.

I have skipped linking to the Wikipedia articles because they do not tell the southern side of the history very well. As southerners tell it, the south was what remained of the Christian heritage that founded the USA.

What we today call Zionists had already taken over the north by the start of that war. Federal taxes had been cleverly redesigned to strip the south of wealth in favor of the north. The south was unfairly taxed to pay for the federal government. That war was ultimately a tax revolt.

The same pattern is going on now against Russia. The bankers need Russia's, Iran's and China's wealth to pay for world government.

After the war, the native southern Christian culture was destroyed. The productive capacity of the south could no longer be used to promote southern Christianity. Zionist Christianity would fill the vacuum and replace traditional southern, often Presbyterian, Christianity.

The story of the 10 virgins is ultimately a story of faith. So fights over faith matter to this story. The Civil War is part of this story. Zionist Christianity is part of this same story. The 10 virgins have trouble keeping their lamps lit. They all fell asleep for awhile.

Finding 5 Virgins

The Confederate flag has 13 stars, one for each state in the confederacy. 2 of those states, border states, were never functionally part of the south. They were occupied by the Union at the start of the war.

Of the remaining 11 states that made up the confederacy, perhaps 1 of them should be considered undeveloped, or outside of the core. Florida would be one easy guess as to where that extra state might be found.

Florida already had European, but Spanish, colonists when Jamestown was founded. There had been Europeans in Florida for the better part of 100 years.

Florida was ultimately taken over because Spain could not defend Florida. Spanish settlers in Florida would move to Havana, Cuba. Florida was thus late to join the Union. Finally, Florida did not develop fully until after the invention of air conditioning. Florida is currently infested with Zionists who have moved there from New York.

Richmond

In this view the 10 virgin story would then point directly at Richmond, Virginia. It was the national capital of the Confederacy. At that time, it was the capital of the 10 virgins.

Those 10 virgins thus become a specific set of 10 states within the former Confederacy. Within those 10 states, 5 of them have a future story of faith that matters in the late 2030s, perhaps beyond.

Those 5 faithful virgin states are thus special, and have faith to handle Joshua's return. Or, if this is a symbolic story, to handle the final plagues on Egypt and move on to a community like Moses setup after Egypt.

Because the State of Virginia is the main villain in the wars involving Iran, I would not expect the warrior spirit of Virginia to become the seed for faith, but we will see. Parts of the original state of Virginia are now West Virginia. There may be a different faith found there.

In any case, readers here can speculate about where those 5 states, those 5 virgins with the oil of faith, may be found.

The Lamp

The story of the 10 virgins is ultimately a story of the lamp with the oil. The symbolic meaning of these features is always pointing at the lamp used to establish the audit pattern around the name Abraham.

The 5 virgin's with 5 working lamps are thus also symbolic for the base inspired text and then 4 more families of ciphered documents that spring from the main document.

So the community of faith that the story expects to find after 2037 is going to be based on texts that nobody yet knows.

These texts, or at least an early set of them, are what Moses reintroduced to the heirs of Jacob. So if the Exodus happens again, reintroducing audited text will happen again too. This is what brings virgins out from their sleep.

Watching Headlines

We are in a very frightful time in world history. Trump and his Zionist overlords, so Pharaoh and his officials, have started a 3rd World War.

What I have sketched out in this blog points at future government officials who will take on the roles of pharaoh and his officials in the mid 2030s. They will probably not be the same people we know now, at least not most of them.

Like ancient Pharaoh, that future pharaoh and his first born son, will also be defeated.

It is not likely to be pretty, just like it wasn't for pharaoh and his officials in ancient Egypt. Remember, ancient Egypt was ruined and abandoned. History mostly repeats.

The ancient events following the Exodus from Egypt are not well timed, but they are pretty well documented. We can expect the same here.

By 2038 the worst of all of this should be over. Don't give up. Keep pressing ahead. When Joshua says jump, ask how high. Do what he says. The potential rewards are worth taking risks.

More Later,

Phil

Cathay

Phil Stone — Fri, 31 Jul 2026 20:57:41 GMT

This blog looks at the vocabulary word Cathay. Before that, we reintroduce the BR app. Then commentary on an UNZ article, status on names related lexicon work and a headline review.

Bible Reader

Ryan has continued to work on updates to our standard set of apps. This week the Canon Bible has been dropped in favor of the Bible Reader app. The permanent link is off the front of Paleo.In.

We think of our apps from 2 perspectives. We care about the low level technical aspects of our apps. So in this perspective we care about features and purpose and how they get used.

Our other perspective looks at the overall set of apps. When we look at our apps that way, we think about curriculum. What are the set of lessons that are needed to bring students of the text up to speed? What are the lessons that we have been through on our journey? Are those lessons captured in our apps? In this overall view we want to make sure that the set of apps covers all the lessons that matter.

History

One of the most important lessons is the history of Christianity. That history created the diversity of the Christian traditions as expressed in the many Christian Bibles.

Americans, especially Protestants, tend to know none of this. Neither Ryan nor I were taught any of this in our own early Christian upbringing. There was no hint that our tradition was full of problems. There was no hint that it was the result of a political process run by emperors, kings and their bankers.

Since we mostly deal with the Bible, one easy way for us to teach this history lesson is to simply present many different versions of the Bible.

These are the basic artifacts from that complex church history. Bibles become the concrete topic for discussion. How did these come to be? Why are there so many of them? What were the translators up to when they built those texts?

Whole Translations

Bibles as passed by history come to us as named translations. The ASV or the KJV are examples. A given translation was created by someone for some reason within some tradition in some language at some time in history.

For most of history, bibles were also constrained by the need for the printer to sell enough copies to make a press run profitable. So not all translations ever made it to print. Translations thus encapsulate a whole bunch of competing issues when it comes to their creation.

So it is important to be able to see these texts in something like their original published format. Viewing historical texts in something like their original published form is the general purpose of the Bible Reader.

That app presents the texts in an electronic form. So the texts in that app are not exact copies. But, it approximates the original printed forms.

Preface Materials

Most published Bibles were the result of a significant amount of work. They often had a wealthy sponsor, or a wealthy publisher. Money usually comes with an agenda. Just like modern electronic media is controlled, so too, have most printing houses been controlled. The needs of those people usually overrode the obvious desire for an accurate translation.

The teams that published those works usually wrote a preface that explained what they were up to with their translation. This is often advertising copy. But at times that material covers serious issues of translation and the forces at work around the task of producing a translation.

Downloadable copies of Bible manuscripts don't usually include the preface material. Most modern readers are ultimately concerned with the differences in the texts, not the motives of the translation team. When we were younger, we certainly thought that way too. It is a reflection of overall maturity. Young people tend to not understand the breadth of evil in the world.

So in this BR update, Ryan has been chasing down the preface materials. When he can find them, he is adding them into the various Bibles included in the BR app.

For readers here wanting an interesting study in the history of Bibles, I would suggest reading through the preface materials found in the BR app. These usually come after the Table of Contents in those Bibles.

Bible Forms

The BR app presents whole texts in their original printed book order. We think of this as their original, inbound, form. This is interesting for understanding the overall work.

For most conventional Protestant Bibles, the overall form is about the same between Bibles. Before about 1800, Protestant Bibles included the Apocrypha, so they were longer in history. Once Jews started controlling Protestantism, those books were dropped because they do not have Hebrew language originals. So even Protestantism is not fixed in time.

Even the 10 commandments changed in Protestant Bibles after about 1950. Don't kill, an absolute commandment, became Don't Murder, a limited commandment.

The RSV was a commercial flop because Isaiah lost the prophecy about an expected virgin birth. This, too, because the Jews were changing Isaiah, so Protestant translations were keeping up. What else would modern Zionist bible publishers be expected to do?

All of these manuscript changes are part of the prophetic replay of Passion Week. This is the time when Jews rule. We will clear that time in history in the 2030s. Until then, Christians suffer under Jewish mind games. The high ground for those mental attacks is the text of scripture itself.

Ancient Greek

Outside of Protestant Bibles, the overall form of Bibles can get quite strange. The most extremely different examples center around the Septuagint Old Testament Greek. Not only does the Greek Old Testament provide copies for "extra" books, some of those Greek books are not actually the same as we know from the traditional Hebrew. Parallel and matched versification becomes very, very hard to pull off.

So the BR app is now intentionally designed to present whole manuscripts in an approximation of their historical, printed, order. This goal allows the app to contain manuscripts no matter what their original form might have been. The app is designed to allow easy presentation of any Bible in an approximation of a printed form.

Technical Notes

The BR app is also design to allow whatever level of markup may be available in those texts. Our manuscript markup system is quite powerful. Should there ever be a desire, and resources, we could imagine adding markup to those texts.

The new Bible Reader has been updated with the new Settings system. It has also been designed to provide complete Bibles as though they were stand alone apps. The next/previous functions stay within individual Bibles. Moving between Bibles is done through settings or by tapping fancy arrows on the front covers.

Verse Reader

Low level, so verse level, comparison is not done well in printed Bibles nor in the BR app. Instead, our VR app provides a place for that level of study. The link here is to our VR app. The permanent link is off the home page at Paleo.In.

As of this week the VR app has also received a refresh. The first goal is to include all of the same texts as in the BR app. So the number of texts in the VR app is growing.

This app has lost the front cover, contents, and back matter that were previously part of this app. This app is not approximating a printed bible, so it does not want facsimiles of covers.

We are starting to see the power of "one page wonder" apps like the Story Grid. New users get to see what the app does on first load. Regular users can get right to work.

The VR app has been updated with the new settings system. But in this app, settings get complicated. The app level settings in the right menu deal with Theme, Font Size, and displayed Bibles.

Individual Bible texts have additional asides that are reached from tapping on their letter codes on the left side of each row. This design allows for notes, perhaps even preface materials, and then any translation specific settings. This, theoretically, allows the settings to match the needs of each translation. It allows translation settings to show off what is possible with the matched translation. Currently, there are no translation specific settings, those will come with future updates.

This week's update to the VR now includes all Greek texts that are known to follow Protestant versification. This means all New Testament Greek texts we have on hand are now in that app. Technical work still remains for this app, this is a good start. There are still issues with Greek.

Planning For Greek

Our intention is to merge all of our Greek text based Bible apps into the VR and BR apps. As of this week, all of the easy manuscript moves are now done.

There remains the problem of really strange OT Greek versification. This impacts the VR app and how the texts themselves are presented. We have had a planning session on this problem. We have a plan to fix it. But, this work is not easily. Respecting the Septuagint versification is the tricky part. More on this later.

Greek Names

Getting NT Greek into the VR has become urgent because of what I am seeing in Paleo Bible lexicon work. Ryan has moved the texts that can be done easily. I may also add Greek to Paleo letter transformation to some of those texts in order to study spelling of Greek names.

There are clearly games afoot related to our common English New Testament names as they have passed down through historical Greek.

Most readers here who know the text will recognize Greek names with their characteristic "us" ending. Cornel, for example, has a Greek form of Cornelius.

I expected to find the Aramaic based New Testament names to either match their expected Greek form, or to use perhaps a simpler form. Aramaic is an older language and it tends to have short, 3 letter, names. Perhaps Cornelius would be Cornel in Aramaic?

Instead there is no obvious correlation. Some names, like Paul, come with both a Greek form, and a simple form. Philip, for example, is always in the Greek form. "Philipus" would be the normal English given the spelling of that name in the Aramaic NT.

It looks like translators who subscribe to Aramaic primacy are covering this up. This detail impacts any theory of origins for the New Testament itself.

I now suspect the New Testament as passed to us today in Aramaic must have been edited in waves. Not just by Ananias, our normal villain, but in different languages.

The Aramaic New Testament was going through the same type of edits as English Language Protestant Bibles have been through, only worse. There must have been an early fight between Greek Primacy and Aramaic Primacy that was fought through edits. The known history of the development of Syriac in Turkey was going on at least a century after the events of the NT.

In that century sits a time window for much manuscript trouble.

So the Greek texts may need to be referenced to solve issues with the Paleo Bible. Ryan and I were prophetically pressed hard on the issue of Greek texts for recovery work. Names, at least, seem to need the Greek references in order to settle issues there. More on this as we go.

In any case, if you keep a set of our apps on your devices, you can drop the Canon Bible and install the Bible Reader. The Greek specific apps will eventually be dropped in order to reduce the overall number of apps found off of Paleo.In. The resulting set of apps will have more value in each app.

Cathay

When we first learned about the idea of Aramaic Primacy we started using copies of the Lamsa Bible. Indeed, someone in the fellowship we were part of at the time ordered a case of Lamsa Bibles so everyone could have a copy.

It is a curious English Bible in the sense that it is based on the Aramaic texts of the Bible. It is outside of the standard Greek/Latin heritage used by nearly all other English Bibles.

Lamsa was an immigrant to the USA and wanted an English text based on the Aramaic Bible used in what is now Iraq. He began translation work in the 1930s. This work was done by hand. It was without a big publisher behind the work. He appears to have worked mostly by himself. His bible became something of a cult classic because it was strangely different from normal English bibles.

One of the strange differences was how he occasionally used the name "China" in certain places across his translation. Nobody in the western traditions of the Bible would ever think of such a thing. Nobody educated in the western texts would think this could be correct.

As I have been loading names into the Paleo Bible, one of the Bibles that I am checking is Lamsa's translation. I found his reference to China and could finally understand his logic for using that modern place name.

The link above is to the Wikipedia article for the ancient name of what is now northern China. "Cathay" is the modern English for that name. That name lends itself to the airline named "Cathay Pacific" which is the flag carrier of Hong Kong. So the name "Cathay" applies in some way to southern China as well, even into the modern era.

Lamsa uses the term China to translate the paleo Ku-Ta-Yo-Mo. There is also a variant, Ku-Ta-Yo-Wa. (There was no computerized spell checkers, nor audit, for ancient scribes.)

Normally, in English Bibles, this word is translated as Kittim. A strict Paleo transliteration is either "Kutayom" or the variant is "Kutayo" where the trailing Wa draws the vowel on the Yo.

Moving from Paleo to English, the Ku can become k or c or ch. The Ta can become either t or th. The Yo as an ending can become i or y. The trailing Mo can become m, n or just drop off.

You should be able to play with this a little and see that "Cathay" is reasonable in English for this word. Lamsa just finished the translation and put in China as the modern form of Cathay.

So if you read through that Wikipedia article, you can see "Khitan" as one of the ancient variants. This is using the Mo to n change we see commonly with word endings for place names. So now you can see why Lamsa might correctly pick China as a recognizable modern English place name for that ancient place name in his English translation.

But...

Translating names is hard. Lamsa is probably correct in that this was an ancient name for what is now modern China. But then he adds an interpretive step within his running text. In our electronic world of displayed texts I would probably prefer such a step to be a function of the lexicon, not a function of the translation. Though if I was super strict on this, the place names for Greece, Italy, Spain and Egypt would change to ancient forms too.

Lamsa was also not fully consistent in his use of China. That name shows up in his translation of Revelation for the place name Gog. There is no Ku-Ta-Yo-Mo in Revelation in Paleo. (At least in the manuscript that we know.) It is unclear why Lamsa would translate Gog as China. This is another example of why translation is hard. Separating translation from interpretation is also hard to keep straight.

Ancient Knowledge of China?

So now, let me back up to the issue of the base text. Would ancient writers of the text have known about China? Could their understanding of the world include geography at the eastern edge of the Asian continent?

I would answer this yes, of course.

They were on the western end of the Silk Road and would have been trading with China since soon after Noah's flood. China was well known in ancient times. It was unknown to backwards Europeans. The Wikipedia article shows that European bias.

One of the problems the world has right now is how China has become something of a manufacturing power house. They basically make everything. Other economies need to produce wealth for themselves. How to do this with China doing most of the work is hard to figure out.

The reason the ancient silk road was so important is because China has always been a manufacturing power house. Ever since soon after Noah. I heard a comment on a podcast here recently that even during Roman times, the planetary GDP was still higher in China than in Rome.

Of course China is going to have been an important ancient place name. Now we know where to find it. Other countries have ancient names too. We will save India for future reference.

Birth Of Protocols

The link here is to a long form article on UNZ by a guest writer, Nick Kollerstrom. It documents the known history of the writing of the book called "The Protocols of Zion."

I frequently reference the Protocols of Zion because it does a nice job of explaining so much about how our modern world actually functions. Outside of scripture itself, this would be on my list of the top most important books that anyone should read. Stated in reverse, if you have NOT read The Protocols, you are not educated in how the world actually works.

The article linked above goes through what is known about the original authorship of that book, as well as the known publication history. This article adds considerable back story and details that are not in the book itself. If you have ever read the Protocols of Zion, or might consider reading that book, I recommend reading the article linked above.

Taking Control

There are certain key points that really matter to our work here. The main issue is how Jewish bankers took over control of the English and French national banks early in the 1800s. This was done deliberately because the private, Jewish, international, bankers knew they could take over the whole world through the issuance of fiat currency. They fully took over the USA in 1913 with the Federal Reserve Act. They have now taken over nearly all other national banks.

In terms of prophetic timelines, the Passion Week replay begins about the same time as the earliest origins of the stories involving the crimes of the bankers. This is the back story for how the Jews functionally take over rule of the world along the main timeline of earth, especially the Passion Week time of that overall timeline.

Remember, Passion Week is when Joshua deliberately gave over rule to the Jews during the tail end of his public ministry. His crucifixion becomes World War II within that larger and longer prophetic week. The story of Zacchaeus tells us his purpose for Passion Week. After Passion Week, his ministry shifts. He was appearing only to his disciples, which indicates the world will be ruled in some other way across the centuries to come.

The replay of Noah's flood beginning in 2029 is what ends the Passion Week time. I would currently expect that war to stretch out to maybe 2038 before it is fully over. Prophetic stories dealing with "midnight" (like Matthew 25:16) are around 7.5 years after the start of Noah. At that time, we move into the next prophetic passion week calendar day, but only by 1/4 of the way across the next 30 years. 2038 is also 430 years from first settlement of Jamestown, VA. James is English for Jacob. This was the start of Egypt in the USA. 430 years from there lands in 2038 as well.

Protocols Details

The article linked above goes through how the Protocols of Zion were published in various places in order to warn local populations about the crime of central banking. This never really prevented that crime from happening. That method of publishing details in hope for a change is as silly as thinking the US public could ever fix Washington DC by some political action. The affairs of nations are ultimately in Joshua's hands. He will change governments in his own time and by his own means. Joshua lets Pharaoh rule. Then Joshua does not let Pharaoh rule. This is a very simple summary of the Book of Exodus.

The article linked above goes into details about how possession of copies of the Protocols of Zion has been punishable by death. This was especially so in Bolshevik Russia because this was when the Jews were ruling Russia. They feared the public might do something should their crime be found out. Russia is one of the few places where the Jews do not rule, which is why there is a current war against Russia at all.

The article above also suggests that book might be the most commonly read book around the world outside of the Bible itself. This, alone is a curious idea.

One other point of interest is that the Jews apparently took over Masonic Lodges as part of their takeover of governments. This would explain the work of people like Albert Pike who in the 1880s redefined how those lodges function. Those lodges, common across much of the USA, are also part of the problem of Passion Week.

I have not yet done a full set of charts for Passion Week headlines from the past 200 years. That week was full of strange interactions between Joshua and the Jews of ancient Jerusalem. Prophetic replays would be expected in the political world of the central bankers.

Match Dates

We were watching Friday, so 2026-07-24 as a possibly interesting date because this was about 150 days out from when Trump first starting bombing Iran on 2026-02-28. This would be in some sense the "end of 150 days of the waters covering the earth" from the perspective of a Noah flood related timeline. This appears to be a 3 year prelude to 2029. For some reason the math appears off by about 14 days.

At 2026-07-24, so as last week's blog went out, it looked like the USA might have been preparing for even more strikes against Iran. Instead, the USA stopped bombing targets in Iran. Iran also stopped most of their retaliation. There was a mostly calm weekend that followed. Calm was not to last very long.

At the weekend, there were some strikes on Saudi Arabia, especially a strike on oil facilities by Ansar Allah in Yemen. Saudi Arabia is being blockaded and attacked in retaliation for their blockade and attacks against Yemen. Before the week was out, facilities at both ends of the pipeline across Saudi Arabia had been struck. All Saudi oil shipments had been suspended. This is a very big deal as the overall planetary supply situation just got very much worse.

Meeting With Netanyahu

The stall in the war across the weekend appeared to have been timed so Trump could meet with his boss, Netanyahu, who arrived in DC on Monday. This seemed to be the meeting where Netanyahu could dictate the next phase in the war against Iran. Trump's in person meetings with Netanyahu are generally followed by changes in the Iran war strategy. This happened again this week.

Instead of the Zionists directly attacking Iran, they instead shifted to Saudi Arabia who started taking on Iranian interests in Iraq. This shifted to formally using the Saudis as the next Zionist proxy for the war. This also shifted to a strategy of defeating Iran along its edges. This is a hint at a future ground war. The plan is presumably an eventual ground invasion of Iran via Iraq. This would be attempting to repeat the Iran-Iraq war from the early 1980s.

It has been many years, but I remember reading the history of the Saudi family. Short answer is that they are of Jewish descent. They should be thought of as an occupying force in Arabia, just like AIPAC in the USA, just like the royal family was in Iran.

Also of note, Zelensky's Kiev also attacked an Iranian vessel. We already see these wars as the same. Zionists don't control Russia, nor Iran. Now the formal fighting is merging.

This Ukrainian attack was probably an attempt to provoke Iran to use previously unseen long range weapons that could perhaps reach Ukraine. So the military purpose was to provoke Iran in order to learn what their missiles can really do. Instead of striking Ukraine, Iran appears to have struck Zionist targets in Egypt.

Funeral

The 2026-07-26 watch date did not have any other obvious headline besides the expected funeral in DC for Lindsay Graham. All the normal nefarious politicians assembled to honor the loss of one of their own. That prophetic date was a Sunday. Netanyahu departed for that DC funeral very early on Monday morning. Formal ceremonies were on Tuesday. This is close enough for a match.

Bombing Resumed

By the end of the week the USA had resumed general bombing of Iran. The war was back on. Why would we expect anything else? The Zionist side does not have any real military targets in Iran. They continue to strike civilian targets in Iran.

Watch Dates

Peeking ahead, we are now watching 2026-08-11 as the prophetic replay of the last year of Amaziah. The reign of Jehoahaz begins the next day, so 2026-08-12. These are at the end of Tabernacles and in the second week after this blog goes out.

Shop Work

Most of my shop work this week has been working on the names annex to the lexicon for the Paleo Bible app. This involves making several successive passes across the raw names data in order to clean up the list of names and prepare it for use in the Paleo Bible app itself. This work involves a back-and-forth movement of updated code and then manual touch up work. This is a very strange work path where manual work is augmented and checked by software.

As of this week, there are 2505 different entries in the names data. This fractures the count some from the eventual lexicon because some names come in related forms. The big issue is how the names of real people then lend their names to people groups later on. Not all of these cases are currently in the same entry. So the 2505 is overstating the eventual lexicon size.

There also appears to be variant spellings of many of the names. We were taught about added vowels when we first took a Hebrew class. What we were not told is that actual vocabulary words may or may not have the same set of added vowels. This becomes a fundamental proof of the idea of added vowels. But, nobody teaching this point wanted to state this obvious dirty little secret. It implies carelessness or a manuscript history beyond our normal ideas of inspiration and transmission.

Added vowels are particularly true of names. Given my working expectation for inspiration, I would expect all such added vowels to go away in the audit. I am also now starting to see the text as handled carelessly by ancient scribes.

My current pass is adding paleo forms. This was driven by the problem of how English spelling is being driven by strange transformations, especially from Hebrew word forms. Almost all Biblical names in English that end in "h" have no such matching letter in Aramaic. There are a series of other less common, but still irritating name changes.

Reboot Names

I have looked at the names long enough to see the problem differently than before. Instead of trying to match back to well known English names, however bad those names may be, it is better to reboot the whole names system and start again and match English to inspired Paleo.

Nobody should be bringing what they know about a name from an English Bible into the world of the Testimony. Nobody should be looking back like that.

If I don't fix this problem, who will?

Once I thought about this problem, this way, I set out to estimate English pronunciation of names given by Paleo spelling, not Hebrew spelling. In this pass, I am working out a formal transliteration from Paleo spelling of all names into English. My formal notation will show up in lexicon entries.

Most of the time, the Paleo will match known English, which is surprising. The expected form, after removing added vowels, usually has the same set of syllables as we know in English. This is also surprising.

Names that have different spellings, because of different added vowels, also return to a common pronunciation. This is also very nice to see.

Names with double vowels and words with known shibboleths are a little more strange. But those form a special set of problems that can be understood.

Stats

From those 2505 distinct names entries in the lexicon, there are currently 5544 different inbound word forms that involve names. These inbound forms are clustered under individual names roots. Because of the nature of the problems involved, these counts should be considered more accurate than real life. Every time I touch something, these counts usually change.

Variations on names mostly involve uses of different prefixes against the roots. Some endings provide an indication that the word is pointing at a group of people instead of 1 person. I expect those to eventually end up in the same lexicon entry, but finding the pairing is not easy.

Note that overall counts will change some as I insert this current data into the lexicon. There are some manuscript differences which will impact counts. These names occasionally collide with regular vocabulary words, which will also need to be worked out.

I was attempting to get this set of names into the Paleo Bible before Tabernacles, but there was just not enough time. It takes several work days to make 1 pass across 2500+ names. This is still much more efficient than loading general words. 300 such words took about 5 weeks. In the end, taking names as a group, is around 10 times as efficient as general vocabulary.

Assuming no prophetic work items coming out of Tabernacles, watch for the next Paleo Bible names update to hit live servers in late August.

Headline Review

The following caught my attention this week.

Vance Telling Trump

There has been strange news flows out of the USA over the starting and stopping of the war. Vance has little chance of winning the next presidential election because of Trump's war with Iran. So for every pause, someone gives Vance credit. This link is an example.

Netanyahu Departs for DC

This link has a pic of Netanyahu boarding the plane in Israel for Graham's funeral. This is a record of the early Monday departure matching the Sunday watch date for a dead northern king. Usually Netanyahu visits Trump to reset war strategy, and this trip was no different. By the end of the week the war against Iran had resumed.

Yemen Against Saudi Oil

Photo

The top link here is one of the early posts dealing with how Yemen took out Saudi oil facilities. This in retaliation to Saudi actions in south Yemen. The Saudi's don't seem all that bright. They would attack points in Iraq a few days later. The bottom link with one of the many satellite photos of the damage. Oil prices rose as this impacts Saudi supply to world markets. Both ends of their main cross-country pipeline were damaged.

Trump Sleeps at Funeral

Notes On Trump's Speech

The top link here is to a clip of Trump who appears to doze off at Graham's funeral. Hopefully, just over work. The bottom link has details on Trump's speech over Graham. Not a nice guy. A strange prophetic fulfillment for the death of a norther kingdom king. The northern kings probably were not nice guys either.

RT On Funeral

The link here is to the full length RT article on the Graham funeral. RT is more polite.

Money Out In Iraq

Oil wealth ultimately drives governments. Small governments, like Iraq, are already out of money due to the shutdown of oil flows. The link here suggests the Iraqi government is suspending most government payrolls over loss of oil income. That government is less resilient than other parts of the world. Give it time to spread.

Invasion In Spain

Heavy Transport

Italy Closing Borders

Massive Rally In Yemen

The Yemen public is rallying again. This time against Saudi Arabia and the blockade. War is spreading through the region.

Tabernacles Week

This year Tabernacles runs from late Tuesday next week through the following Tuesday. Ryan and I are planning to camp for that week and are off from regular work for the next 2 weeks. Our intention is to read through the Testimony as it currently stands.

There should be a couple short blogs over the text 2 weeks, provided we have internet access. The blog will return to normal after the holiday.

More Later,

Phil

App Parade

Phil Stone — Fri, 24 Jul 2026 20:46:18 GMT

This blog introduces major upgrades to all of our apps. We start with the Story Grid before moving down the whole list. Then notes on the Paleo Bible, especially issues with names. Finally, a headline review.

Story Grid: 494

The big change with the Story Grid begins with changes that expose the current story to the URL for the app. If you are familiar with that app you know most of the stories are shown in "asides" which are also known as pop-ups. Previous to this week, those asides could not be reached from outside of the app. Someone using the app was required to tap the Story Grid square and then see the aside.

So now, as someone moves around in the app, the URL for the app changes to reflect the currently displayed aside. This is a powerful change, which allows all sorts of fun uses. It may be easiest to see with an example.

The link here is to the Story Grid app as normal, but now specifically to the Qu-Qu tile. This is number 494. Note that if you follow the link, not only does the app itself come up, but also that story is displayed. It is open and ready to read.

This is a very nice addition because it allows external references to any of the content inside that app. There are no longer any pages at all in that app. As far as the URL is concerned there is only ever just 1 page.

External Cites

If you poke around in that app and watch the URL you will see how the URL changes based on where you are in the app. The URL is now visibly maintaining the internal state of the app. This allows the URL to be copied around and kept anywhere. Following the URL back to the app will restore the state to match the URL. This makes any external cites easy to do. It has a few other interesting implications.

Browser Back

Not only does this give external access to what was an internal feature, it also puts the pattern of movement between asides into the browser's history. This enables the browser's "back" function to go backwards through that same aside history.

Supporting the browser back button suddenly became important once we redid the story related tiles. These are now much easier to use. But a common use case is to chase down related stories and then back up to the main story being studied. This is the most common use pattern for studying the story folds. Serious users, like Ryan, really want to have this feature in the Story Grid app.

No Back Button

There are some situations where there is no browser back button. The browser itself might not provide a back button. Apple's browser, at least traditionally, has not supplied a back button. Apps that are installed outside of the browser also have no back button.

So we have also added a "back" button inside most of the story related asides found in the Story Grid app. Poke around and you will see it. This makes the most typical study path evident and easy to reverse.

Tracking Current Tile

Moving around between stories in the app also causes a highlight to mark the current tile in the main grid. This highlight causes the main grid to scroll around and follow the current aside.

Once the current aside is closed, that highlight remains on what was the active tile.

This is another important feature because it allows anyone using the app to clear the current aside in order to study the general location on the main grid. But once out of a particular aside, that highlight indicates which story needs to be tapped again in order to return to the aside that was just active.

Again, this is all function needed by anyone serious about learning the grid.

Story Next and Previous

For all of the story related asides, there is also now a pair of arrows in the aside. These are in the top right, under the X that closes out the aside.

These arrows move in story number order. The left arrow goes down by 1 story. The right arrow goes up by 1 story. This has been added to make it easier to study story sequences.

The stories in each row of the table advance by 1 letter of the alphabet. So a common study for any given row is to read each story in sequential order. This allows the reader to spot the content advance that tracks the change in the letter. It is possible to read all the way through the Testimony using these arrows.

I read through the Qu row as a devotional to try it out. This is a nice new feature for this sort of scripture study. For that particular row, each story carries some aspect of the meaning of the letter Qu. It then also brings in content and meaning based on the second letter.

Right now, stories are still settling into their places. Eventually, once story placements are certain, this becomes a very serious study tool.

Replacing Study Bible

More and more, we are seeing the Story Grid app as the inspired replacement for what are commonly known as Study Bibles. That form of printed Bible brings notes from someone with access to money who can then steer crowds on how to think about what the base stories might mean.

The inspired answer is better. The inspired stories are designed to fold against other stories. Typically, there are 8 such folds as shown in the tiles tab under each aside.

If you want to know what a story means, or at least what it is like, then follow the matched tiles.

Ryan and I are just exposing the inspired system. Readers must decide how to apply. No priest gets to stand between the reader and what the text actually means.

As the grid is filling in, these pairs are exposing story meaning in amazing ways.

Future Use

Exposing asides to the URL is a nice feature. We can use this trick in other apps when it may make sense. It is possible to finally imagine a timeline app that would be built around a main timeline graphic and then use asides for dealing with dated events. This design for a timeline could then support cites from external sources like blog posts. In any case, our environment for building apps just got a whole lot more robust.

Settings

One of the important things the Story Grid is now demonstrating is how to pack more information into what appear to be individual asides. This is a very nice trick because it makes the natural complexity easier to learn.

Once we figured out how to pack more information into asides, we started to rethink our other uses of asides.

The top right menu of our scripture related apps have typically been cluttered with various asides related to formatting. These "settings" are now grouped together in a single aside. You can see this in the Story Grid app. The link above is to the Settings aside in the Story Grid app itself.

If you look through that settings aside you will see all the formatting choices that control how the text of scripture is displayed. There are also a few other settings dealing with the app itself. This includes the app's theme, and font size.

The individual settings themselves should be pretty easy to figure out. If you look at the drop down right menu you will also see it is now significantly shorter.

So once that was working, we liked it enough to want to update EVERYTHING to work the same way. All of our apps have been updated this week with at least new Settings related asides. Let me work through the list and point out other changes that are going online with this week's blog.

BRB

The link here is to the BRB. You can tap on the right top menu and see how that menu is now dramatically shorter. This should be very much easier for anyone to discover and use.

This does not (yet) have external URL access to asides. You'll need to poke around to see. The first thing to notice is the right drop down menu is very short. It has a pattern that we are using across all of our apps.

Intro

When there is some sort of written introduction, that will be in the top choice, labeled "Intro." You can see in that intro how we are using the same tricks as the Story Grid to compress a bunch of prose into an easy to use format. In the case of the BRB there are important notes on the villains.

Lots and Search

After the intro comes any app specific tools. In the case of the BRB there are Lots and Search choices in that menu.

Note that Lots now has a menu bar. That bar lists "Calculator," "History," "Info," and "Audit." This brings into 1 place materials that were spread around previously. The History was in its own aside, far from the calculator. The Info for lots was behind a circled I, the Audit was in the About. All of this is now clean and well organized and in one place.

Search works as always. We recently updated the Search system. No changes to search itself as of this week.

Settings

Then the BRB has a link to Settings. This new aside has all of the settings that are available in the app. These are generally listed in the order of their impact on the user interface of the running text.

Note that as of this week's update Ryan has been making sure that essentially all formatting in the running BRB text can be turned off. So the actual list of choices in the settings aside is longer than in the past. Beware. With great power comes great responsibility. You can now turn the BRB into something like a black-and-white printed book. How quaint.

All of this is happening in 1 aside with all the settings easily discovered just be scrolling. This is very much easier to learn. It is now easy to survey all of the available settings.

Contact

Continuing down the BRB right menu, Contact is listed next. It works as always. No particular changes this week.

About

About is the final choice in the right menu. We have intentionally moved out most of the prose that was once kept in About. There are now 3 key things kept in the About. This is now true across all of our apps.

First, there is the typical build info, like build date and revision numbers. Though not needed very often, it does have a common use. Running lots in a group requires synchronizing everyone's copy of the app to the same build number. The top of the Abound is where that number is found.

Then there is a theme verse. This is just a personal touch, like a prize for visiting this dusty corner of the app.

Finally, there is also the sharing related QR Code. This makes it easy to install the app on a friend's phone. Everyone with a phone can now hand out copies of scripture.

2026 Tabernacles

Tabernacles week starts at Sundown on Tuesday, August 4, 2026. It ends at Sundown on Tuesday, August 11, 2026.

We are planning on attempting a full read through the current draft of the Testimony across that week. Normally, a full read takes a very busy 8 days, so in common years there is not really enough time for a full read. This year is a common year, so there is not really enough time. We will likely run a day long, we'll see.

TT App

In order to be ready for that week, we have added a setting to the TT app that is called "Division." This impacts how the books in that app are divided into sections.

The default Division is based on the Patriarchs. This breaks the Testimony down into sections that follow the promises Jacob gave over his sons.

The new Division is called "Holiday" which divides the Testimony into what are ultimately 9 different reading sections. These sections are based on taking the Story Grid and grouping them into 8 major sets of 3 rows each. Revelation and Hebrews are in their own short section 9.

By flipping this setting to Holiday, the Table of Contents and the main menu in the TT app flip over to major grouping by the holiday related Story Grid rows. For the main groupings there are 3 reading sessions, so 3 rows, for each day in the holiday.

We don't yet know if there is enough time to read through at this pace. We are going to try. I will report back after that week is over on how this went.

Calendar App

The calendar app has been updated to the new Settings format. At the same time, there has been an update to a setting related to holidays.

There is a Reading section in that app's Settings. These enable read markers of various types to be placed in Calendar cells. The most commonly used Reading markers are Sabbath Reads. These show up on the calendar as SR: labels in Sabbaths. The Passover Reads and Tabernacles Reads show up on days within those annual, week long, holidays.

The Tabernacles Reads choice had been limited to the 8 day versions of those holiday weeks that show up in Sabbath and Jubilee years.

As of this week, that option now runs in all years, with day 8 after the common year holiday week normally ends. This is really only useful for hard core Testimonians. We will run with this setup over Tabernacles Week and see if we want to keep it there permanently. We may add a day 9 for the tail.

Clock

While I am on the issue of the Time apps, the clock app's Setting aside gained a much better interface for selecting the clock face. Check it out.

Updating All Other Apps

We were having so much fun with the improved interface that we then moved on and started upgrading all of our other apps. I am saying "we" but Ryan did most of the work. I was tracking down technical issues as the week progressed.

There are 13 Web Apps listed off the front of Paleo.In. All but Canon Bible were updated this week. Let me show off what was done.

Verse Reader

The Verse Reader has an updated right menu and settings are grouped.

Verse Reader Greek

The Verse Reader Greek has updated right menu and settings are grouped.

Greek Research Bible

The Greek Research Bible has updated right menu and settings are grouped.

Bible Harmony

The Bible Harmony has updated right menu and the settings are grouped.

Sabbath Reads

The Sabbath Reads has updated right menu and settings are grouped.

Qu Map

The Qu Map has updated right menu and settings are grouped.

Paleo Bible

The Paleo Bible has been updated in the same way, the right menu is updated and the settings are grouped. But, more has happened to this app this week. Let me go through the details.

Font Size Control

Earlier versions of the app did not have correct handling of Font Size. That problem is fixed this week. The Settings displays samples of the standard font sizes. The font used in the running text now actually respects those sizes. So it should be possible to see more text on screen.

Paragraphing

There is a new setting that can be used to control the type of Paragraph formatting. The current 2 choices are Block paragraphing and Verse Per Line. Paragraph placement is being shimmed in from the paragraphs used in the BRB. This is intended to allow more dense display of text on page. Apocrypha books currently have limited paragraphing.

Navigation

There is also a new setting that can be used to control the type of navigation used in the app. The 2 choices are Chapter or Story based navigation. Chapters are of course the traditional chapter breaks. Stories are a better, more natural type of navigation.

When navigation is switched to Story, the right drop down menu shows story names instead of chapter numbers. This is a much nicer system if you know your way around in the text.

Story headings have been added to the Apocrypha. Some of that is still a shim. There is still a huge amount of work to do on this app. But progress is happening.

Names

I had started to load names a couple weeks ago. Eden was the second such name. It is also a word for time. I had touched the problem and power of what will become Paleo roots. But, I also needed stronger tools for determining what English names to use with roots only when those roots are used as names. It was time for a design iteration as per the problem of loading names into the Lexicon.

I've got a plan for a much better tool chain that cross checks paleo roots against locations where those roots are used as names. Any other root like Eden should now be easy to handle. This new work flow must be done sequentially. The first occurrence of each name must be checked and entered into the lexicon. As of this week, I am currently in 1 Chronicles. This is the worst area of the text because of the abundance of rarely used names.

So names are now a large single piece of work that will go into the app all at once. So no particular updates to the interlinear data in the Paleo Bible app this week.

Because I am using an internal version of the VR app, I have visibility to all the different English used by different texts across history. Since I need to load those names into the new setup, I decided to load conventional modern English as the first round of these names. I don't intend to end there, but I could imagine conventional English might end up under a setting. I could also image more correct English names as the default view once we are past audit. So running what becomes a second set of names makes sense now. This pass does not need to be perfect.

This was a good conceptual starting point. But it soon got strange. My mental model of Biblical names was sorely inadequate for what is actually going on in the text. Let me review what I am seeing.

Trouble

I have never actually looked very closely at this problem in the past. This work has been a MAJOR learning curve on the differences between Aramaic based texts and the Hebrew/Greek/Latin/English based tradition that everybody in English already knows.

I set out to prime the system with conventional English. These names APPEAR to come from Jerome's Latin which was known before English vernacular bibles became popular.

Jerome visited Bethlehem so Jews could teach him Hebrew and he could have help making his Latin translation. This is where western Christianity broke from Orthodox Christianity. This is why the Orthodox generally consider western Christianity as a break away from the inspired tradition.

I now suspect that Jerome was a Masonic, so Zionist, plant who was intentionally breaking western Christianity away from its historical Greek roots. His club of sponsors could eventually make the text say anything they wanted. Hint: Zionism does not exist in Orthodoxy. Jerome's work was when western Europe was first defeated by Jews in the war of religions. That battle still continues against Russia, Iran, China and a few others.

So the ultimate chain from Paleo to English was via Aramaic, Hebrew, Latin and then English as it has evolved for centuries. The New Testament has no Hebrew in the chain. So the New Testament chain is something like Paleo to Aramaic to Greek to English, where English has continued to evolve. Of course the Orthodox chain does not have much Hebrew, provided they are on the Greek Old Testament.

The model I have spelled out here are mostly conventional, accepting disputes over Aramaic primacy. This is, though, some sort of imaginary chain. It does not explain everything going on in the text. There are a few other points that seem to matter to what happened across history.

Editors

So what language did the Editors use? The professor I have linked in videos seems to think there is linguistic evidence of some Hebrew to Aramaic. That would not surprise me. Editors were not writing in Paleo. So their edits were in Hebrew or Aramaic. Hebrew sources for additions would explain the clues the professor is hinting at in Aramaic.

The implication here is that the number of translations in the chain of transmission into English is now different for different passages in the text. This is not just New Testament vs. Old Testament. It is based on where edits were being made. So some passages will naturally have different problems based on their specific history.

Sound System

So there are known sound system issues through this language chain as well. Most everyone knows the Y sound in Hebrew comes out as J in Latin. Q comes out as C, K or CH. S and Sh sounds are forever messed up. Those even happened in Judges. I was prepared for these differences.

The Scripts exhibit shows these differences too. There appear to be times in history when nobody was literate in the western world. Pentecost impacted language systems across the planet, especially across the Roman world. It was a New Testament era replay of the Tower of Babel. These sound system and letter pronunciation differences can be explained through that history.

But, I am finding another sound system change. The D and R are also changing across names, as seen down across time. This one is interesting because it explains yet another interesting problem.

The Scripts exhibit that was 3d printed last year also shows digits. Most digits are just Paleo letters, in order, matched to their number. One of those digits is wrong.

The Du letter should be the basis for the drawn form for the modern digit 4. Instead we find the Re letter is the basis for the drawn form for the digit 4. Remember, R did not always have the descender. Even in English you can see the 4 and the R are mirrored but similar.

Where, or when, the chain of transmission saw the Du-Re reversal, I cannot tell. I can see that current English names will at times have changes in all of these letters. We've known roots of names like Ya-Qu-Ba in Paleo might become J-K-B in English. Now the R plays games too. Once we get to the rare names, with letters like R, the amount of changes becomes much more widespread.

Legal Translation

It has been a few years since I reviewed this point in the blog. But the modern history of translation is important to remember. When the European Union was formed, they needed to write law that meant the same thing in each national language of Europe.

This needed a set of translation skills not normally practiced. Translation of law had to mean the same thing in each national language of Europe.

This is a difficult skill. It is only taught in a few places in Europe. It has a whole family of translator tools that go with the problem. This includes careful authorship of the original laws. Translations are thus unambiguous as well. There can be no ambiguity in European law as there is in most American law. Courts in Europe don't need to define what laws mean as much as courts do in the USA.

Some of those modern tools are statistical. Accurate translations tend to exhibit similar statistical patterns as the original. This only happens because the translators are taking special care in their work. Sloppy translations, so all ancient translations, tend to have fewer unique words than the original. It was a report of those tools used against Aramaic as compared to Greek where I first learned and believed Aramaic Primacy.

Another important modern translation tool is called round-trip translation. This involves taking a base text, translating into some other language, and then having a DIFFERENT translation team, translate it back into the base language. The parlor game "telephone" is built around this same idea.

I have been using this round trip tool in my head as I have been working names for the lexicon. Let me explain this by the example I learned in school.

Example

I remember a particularly interesting session in a Master's level English class. The professor was dealing with real world problems for international advertising.

The rule taught in class was that any public writing needed to be through a round-trip translation process. This means you hire a translation from your source English into a target language. Then have someone else translate back into English. If it does not mean the same thing on the way back, you have a problem.

Importantly, both sides of that process could NOT be done by the same translators. Nor even done by the same translation service. This had to be done before any money was spent on using that translation in advertising.

The professor's best example of this problem was from a Coke campaign. "Coke Adds Life" was the phrase blasted across all media in the USA at the time. Most Americans, in the mono-culture of that time, knew the expression.

It was so popular, Coke then ran the same campaign around the world, including in South Korea. Not only did Korean sales of Coke products collapse, they started getting nasty feedback about having run such a terrible ad campaign.

Of course the Coke executives had no idea what they had done. They hired consultants to figure it out. Those consultants came back and said you spent a ton money telling Korean language speakers that "Coke brings back dead relatives from the grave."

The original phrase, "Coke adds life," does not actually mean anything in English. The translators had no idea what to do when moving the English into Korean. They guessed. But, they did not know their hack translation would be splatted across the country. To their credit, they did pick the same total number of Korean words as English words.

This is why round trip translation is important. It is turning out to be a good check of English manuscript translations. When the Aramaic, which is near Paleo, is available, does it match the English? Could the English be translated back to Paleo and mean about the same thing? I am running these questions in my head with every verse I am looking at.

Translator Care

So let me ask the question: How much care did ancient slave translators put into the task of translating additions to sacred scripture?

Did they treat their work like the translators working on European law?

Did they think they were going to have a huge audience?

Or were they just translating strange memos from the boss without much care?

Dusty Corners

I use the term "dusty corner" to indicate any area of any project which does not normally get much attention. This could be your attic. This could be at the zoo in the deer section. (Especially if you live where there are deer.) It could also be some part of the Bible that does not get attention very often by readers.

Some dusty corners should not be dusty. The last 3 chapters of Judges is a good example. Those chapters are dusty because the content and implications are scary to most readers. Some dusty corners are dusty for good reason. There are many long genealogies in the text that do not carry much weight with most readers. Who cares about who begot who? These are natural dusty corners.

Dusty Genealogies

So I have been loading names from dusty genealogies into the lexicon. In effect, I am doing a round trip translation. I start with a Paleo term. In history this was an Aramaic term. This is already once removed from a theoretically audited original Paleo text. Here soon, we will audit our way back to that layer.

So my current tooling starts with unaudited raw Paleo. I then survey down the list of intermediate translations and see some English for the ancient name.

The KJV is about the oldest English that matters because it resembles modern English. The KJV usually agrees with modern English. At least for major names. The KJV is still stacked on Jerome's work. The KJV era names, especially for the major, common names, are the names everyone knows in English. For uncommon names, like in dusty genealogies, there is more strange stuff going on.

Very new translations, like the NIV, are often diverging even more than the KJV.

The joke when I was young was the NIV is the "Not Inspired Version." No kidding. The NIV is picking up recent changes in the Hebrew texts from the past 100+ years. No one ever told me the NIV was based on a modern edit of the Old Testament. This is a dirty little Zionist secret.

In any case, there are many places in the text where there are dusty corner verses, which do not get much attention, which do not even remotely round trip back down to Paleo.

This can be caused by sound system changes. I explained that above. Those are not that serious. This can also be caused by modern editing, say the OT Hebrew used by the Zionists building the NIV.

These changes can also be caused by careless translations somewhere along the historical translation stack. These were not modern legal high-skill translators. At times they were doing rough paraphrases. It is not unusual to find verses with strangely different order in the various phrases that make up the verse. These are things I never expected to see.

More Later

I have been moving fast for time. I do have about 2300 names to enter. So I am not taking notes. I am not trying to collect evidence. Once the tooling is done there will be ample ability to come along later and study this problem more completely.

But I am using this blog to record what I am seeing. We will return to this topic again in the future.

War News

This week we were not particularly looking for any change in status with the war in Iran nor the war in Ukraine. The Friday this blog goes out is a possible shift related to Noah, so perhaps something with the Iran war. We are basically approaching 150 days from the start of the war. I will return to this date if needed in next week's blog.

There has been considerable reporting from sources in Pakistan dealing with the Trump administration itself. The short story here is that Trump appears to be unable to stop the Zionist war against Iran. Trump appears to have been tasked to get a cease fire. This, presumably, to give the Zionists time to re-arm.

The Iranians have answered Trump with requests to do the agreed upon items from the MoU. This is presumably a real test on whether Trump is able to carry out any executive branch function of the American government. Trump appears unable to carry out anything agreed to in the MoU. Someone else is running the USA. Some of the people around Trump are probably minders, set there to control everything Trump says or does.

So the USA continues to bomb Iran. Iran then continues to bomb American military targets around the Persian Gulf. Unless the Zionist side escalates in some way, Iran appears able to slowly remove all American bases from the region.

Many American assets have been moved to Israel. This is some distance from Iran compared to, say, Kuwait. Iranian's have the missile capacity to strike Israel. But, Iran appears to be "sweeping the room" of Americans starting from the east.

Yemen

The Ansarallah government in Yemen has now closed the south end of the Red Sea to ship traffic related to Saudi Arabia. Other ship traffic is free to pass. This blockade adds many weeks of shipping time for oil from Saudi Arabia to reach Asia. This time delay is because that traffic must go around Africa via the Suez canal. This also limits maximum ship size as super tankers cannot fit through the canal.

This closure changes the cost equations for Saudi oil. It should give the Europeans a chance to out-bid Asia for some of that oil.

Just a note on the proper name. Western media uses the term "Houthi" to denigrate the leaders in south Yemen. Houthi is the name of one of the major families in that region.

The use of the Houthi term implies south Yemen does not have a legitimate government. That government's actual name is Ansarallah. Because western media refuses to use the correct name, there are 3 different English spellings in common use. Ansar Allah, Ansarallah and Ansarullah are all used in different places. Presumably one such spelling will settle out over time. I am using the compounding of Ansar and Allah. This seems the most respectful of the 3 different common forms.

I will attempt to use their correct name in blogs going forward. If "Houthi" was the correct term, then the drone videos of massive rallies in Yemen would suggest the Houthi family has maybe 2,000,000 members.

Since the American government is occupied by Zionists in similar fashion, perhaps we should pick a denigrating name for the American government. How about Last Trumpers?

Watch Dates

Theoretically, we have a possible funeral or death or some similar headline for a northern king on 2026-07-26, which is the Sunday after this blog goes out. Weekend dates usually see headlines pushed off to adjoining days.

This will presumably fulfill with the Graham funeral. Preparations should begin on Monday, with formal ceremonies in DC on Tuesday. State level ceremonies are on Wednesday. But, note, there is quite a bit of heavy western hardware moving towards Iran for a possible strike over the weekend. Another attempt at defeating Iran might be the fulfillment headline. The Jewish work week in Israel begins on Sunday, which for them is a fine day to start a war.

Peeking ahead, we have a possible minor Noah date on 2026-08-07 which should see something around Iran. We reach the replay of the end of Amaziah's reign on 2026-08-11.

Headline Review

The following caught my attention this week.

Note, I have recently learned that X does not let inbound links render for non-subscribers. I don't know if this is always true, but it seems to be. For now, I will still keep using a few X links.

Link rot is also a thing. The best long term answer is to keep screen shots in our own systems. That is a work flow and blog change that likely comes with a timeline app. If someone has a better solution, please let me know.

War Graphic

The link here is to a Zionist prepared graphic of ground invasion war plans in order to conquer Iran. Art is easy. War is not. Barring use of nuclear weapons, the advantage is still with Iran.

Nuke Plans

The link here is to a long form article on SGT Report dealing with post 911 nuclear war doctrine changes. Small nukes have been used by the USA in various places in the modern era. Iraq is thought to be one of those places. (Lebanon and Syria are others.)

This article is being linked from current social media posts with commentary on the idea that the Zionists are planning a nuclear war against Iran using small scale nukes. Resorting to nukes is the escalation strategy for anyone loosing modern wars. It is the USA war doctrine to do so.

These weapons drop the cost of war considerably. As the USA becomes dirt poor, these weapons will become popular. Even inside the USA.

Nuke's For Saudi Arabia

The link here is to a Zero Hedge article dealing with Trump granting nuclear tech to Saudi Arabia. This is said to be for commercial nuclear based energy.

This for the country with more fuel than nearly any other place on earth. This also for a country which is mostly sandy, sunny, desert. This is an deal place for solar panels, not nuclear energy. Fat chance this agreement is really for energy related uses.

Most social media commentary says this is to cover for granting the Saudi's their own nuclear weapons. We are heading towards nuclear war.

Press TV, Saudi Nuke Deal

More on the same Saudi Nuke deal. The issue is proliferation of nuclear weapons. Everyone knows this. Trump is a fool to not admit it. They want the Saudi's to nuke Iran so Russia and China do not nuke the USA in retaliation for the USA nuking Iran.

Rubio and Lavrov

There was a high level meeting between Russia's Lavrov and America's Rubio during a larger conference in Asia. The link here is to a Zero Hedge article with a few details.

The media people asking questions were following war news reality based on social media, unlike the media crew at the White House. Rubio goes meta.

The Zionists cannot stop conquering Russia. It is their religious goal.

The other way to think of this meeting is Lavrov is the cat. Rubio is the mouse. Maybe this should be this week's cat video?

Tass: Rubio and Lavrov

The link here is to the TASS summary of the same meeting. Tass is a class act. Rubio says there is much work to do in order to end the conflict in Ukraine. Why? I can answer that. Rubio still has much work to do in order conquer Russia. Only that will end the war in the minds of the Zionists.

Ukraine Collapse

The link here is to a post on telegram with the population statistics of Ukraine. For those old enough to remember, the death/birth ratio in Ukraine is now nearly the same as the Khmer Rouge in Cambodia in 1976 and worse than the Rwandan Civil War/Genocide. This part of Europe is now worse than anywhere in the 3rd world. Thank the Zionists for making Europe 3rd world.

More Later,

Phil

Paleo Roots

Phil Stone — Fri, 17 Jul 2026 20:51:34 GMT

This blog explores special problems around Paleo roots. Before that, more notes on the letter Qu, especially from Disney's Sleeping Beauty. Then, as war returns, a cluster of possible upcoming watch dates. Finally, a headline review.

Letter Qu

Last week's Blog went through a review of the letter Qu. The meaning of this letter has been lost to us since we first worked out the 3d models over 16 years ago.

Perhaps one of the most important themes of this letter is how a tree takes time to develop before it produces abundant fruit.

We may have lived that definition with our understanding of this letter itself. We worked out the letter definitions very early in the study. But we finally figured out Qu about the time the meaning of that letter applied to our own work. We are currently working Story Grid and Paleo Bible. These are the abundant work items that have taken many years to develop.

Rethinking Disney

We originally traveled to Disneyland following the holiday schedule. We were using Disneyland as a surrogate for the temple in Jerusalem. We wanted to know what it was like to celebrate holidays as was done in the text. Being stuck in Los Angeles traffic was less trouble than being stuck in donkey traffic arriving in ancient Jerusalem.

At the time we did not understand the temple system was a Jebusite perversion of the Tent of Time as setup by Moses and Joshua son of Nun. So we were doing what we thought was right, but we were thinking wrong because of the work of editors. Everyone is in the same trap.

To be fair, our very first trip to Disneyland was as a result of a very vivid prophetic dream that involved a long drive, parking lots, palm trees and a snow capped mountain. Only Disneyland fit everything from the dream. Travel to Disneyland was not originally our own idea.

Eventually, our overall understanding of inspired scripture changed once we understood the problem of editors. That understanding only came about 10 years ago. We have not traveled to Disneyland since that time. There has been no prophetic leading to do so.

Our hope now would be to finish building a complete set of 3d printed exhibits and then figure out a place to set them up. I will return to 3d work after the Paleo Bible has been through audit.

But, finding the meaning of the Letter Qu has caused a return to thinking about Disney and Disneyland. The last time we were at Disneyland, we understood the other letters, but not Qu. So if there is insight to the letter Qu at Disneyland, we need to find it by starting over again with the Qu related rides at that park.

The tight coupling of the design of Disneyland to the Qu Map suggests Joshua was doing something very prophetic trough Walt Disney and his team of designers. We first saw that years ago. Our understanding on this point has not changed.

The prophetic design of Disneyland has even continued here recently. The new Star Wars Land fills in the Yo letter at the park. This had been a waving chief on a horse. Now it is a whole land. So the complete prophetic design has been filling long after Walt's day, even into our day.

As a note, Star Wars Land is the Yo on the Disneyland Qu Map. The Yo on the national USA map is in Alaska. Presumably, Alaska is still to be fully developed. Perhaps we need to study Yo at Disneyland again? I digress.

Ride Pairing

Our Qu Map app carries many notes about Disneyland that distill the Qu Map from the Paleo Letters to that park's main rides. Those notes are the result of over 100 days spent in park.

Curiously, the 100th day we entered the park our addresses had changed. So our drivers license addresses did not agree with the Disney computer. The computer probably figured we had stolen someone's annual passes. We were sent to customer service to get this worked out.

The woman at that desk had quite a few questions for us in order to make sure we were the rightful owners of our passes. We had to explain where we once lived. We had to prove we knew the park well.

Once she was happy that these were our passes, she updated her computer. Then she commented that this was the 100th day we had ever entered the park. That we would be told this was our 100th day, on our 100th day, suggests Joshua had ordered our steps the entire time. It turns out, we did not have very many days left before our time studying the park would end.

That park is where we first even figured out that there even was a thing like what we now call the Qu Map. It was an expensive and time consuming lesson. Ideas that seem so simple and are now so self evident do not always come easily nor cheaply. This, itself, is a good example of Qu and building orchards. They take time.

As we were figuring all this out, we realized there were matches between the designs of the rides and themes related to letter definitions. For many rides, we also studied the back stories for those rides. Many of those stories involve movies or printed books or events in the history of the Disney company. When available, we also purchased copies of the matched DVDs.

Rethinking Qu

So finding a better definition for the Qu letter means we need to recheck the Qu related lessons from Disneyland. This might update notes in the Qu Map app. It might just add some detail we still do not see. It may enhance our understanding of Qu.

The Qu letter ride at Disneyland is "Sleeping Beauty Castle." This is the central icon for the entire park. It was originally patterned after a certain castle in Germany. The designers of the castle in Disneyland famously tried to play tricks on Walt.

They had built a prototype model so they could think about the eventual castle design before building it. (This itself is an example of Qu, the small grows into the large.) Some of their castle model parts could be rearranged.

Just before a certain meeting with Walt, the designers changed how the parts were placed. This was done as a prank, minutes before Walt walked into the meeting. Walt is said to have known this was a prank, but then he accepted the change, creating the Disneyland castle as we know it today. The designers themselves were shocked.

The interesting part of the Qu is the upper part, so design changes at the upper part of that castle are an echo to the Qu letter.

In terms of the overall park design, the cluster of rides mostly behind the castle can be understood as the orchard for the Qu. There are 25 such castle rides and other points of interest. I covered some of those details in last week's blog.

The castle itself has a walk-through. The content of that walk through has usually been tied to the original Disney film "Sleeping Beauty" which was released to the public in January of 1959. When the castle was originally built, that movie had not been released. It was a preview of what was to come. That original castle interior design was also an example of Qu. The seed was planted. Fruit would come later.

The Sleeping Beauty movie has a rather strange history. Ryan and I pulled out our copy of the DVD and watched it again in order to review it for Qu related content.

While watching that movie, I remembered certain details of the making of that film. I chased down those details as part of this review. Turns out, not only is the content of that movie following Qu, but the history of making that movie is also following Qu. Let me explain.

Wikipedia: Sleeping Beauty

For those who may want the full details, the link here is to the Wikipedia article about the making of the 1959 Disney film titled "Sleeping Beauty." There are many details about the crew that made the movie. Those details don't seem to particularly matter for us here. But the overall history is very important to the meaning of this letter.

Disney registered the movie name in 1950. So it was nearly 9 years before release. Disney planted the seed in 1950. The first crop was 9 years later. This is the Qu. Plant a seed and wait and wait and wait for harvest.

Internally, development was mostly suspended in 1954 because most of the crew working on the film was redirected to designing Disneyland and to developing various TV series for that new medium. That film crew would mostly return to work on the movie again in 1956. This is another example of the Qu. Plant the seed, then go do other things while waiting for the harvest.

The DVD included the movie, but also a bonus feature which was the TV show from January of 1959 when Walt introduced the movie to the public. Walt mentions they had spent $6,000,000 making the film. By the time the film left theaters, Disney had lost $900,000. It was a box office flop. First season harvests of fruit trees tends to be small. More Qu.

The film would be re-released to the public several more times. Eventually, the 1959 version of Sleeping Beauty would become one of the 40 top grossing films of all time. Qu harvests come late in life. So too, was this movie a star performer, but not right away. More Qu.

Struggles

Disney struggled with this movie in part because there had been 2 previous Disney princess movies, Snow White and Cinderella. Walt was trying to make this movie different enough from the earlier 2 movies in order attract an audience. Use of 70mm film was one of those changes.

One of the issues was how much of Pyotr Ilyich Tchaikovsky's original music score should be used in the movie. In the end, composer George Burns wrote new music for the movie, but in Tchaikovsky's style.

The links to Tchaikovsky show up in the TV show, and that show gives a short biography of his young life. He seems to have had a vision for this music when he was young. But he was only able to complete it when he was much older. Again, more Qu.

Tchaikovsky

Beyond our scope here, the biography of Tchaikovsky on Wikipedia shows his music caught up in the social conflicts in Russia across the 1800s. His level of skill was covered by grants from the Tzar. The Zionists in Russia in those days were trying to change Russian culture to reflect European culture, this even included music.

Tchaikovsky was caught in this struggle. Part of how he survived was to develop his own musical style. I would now explain that social struggle and context as the Zionist controlled Europeans attempting to seduce the Russian public to join the Zionist plan for conquering the world.

This was the Zionist response after Napoleon failed to conquer Russia by military force. The Bolsheviks at World War I were the 2nd attempt at conquering Russia. Hitler was the 3rd attempt. Ukraine is now the 4th attempt.

Putin now struggles with the same Zionist social pressure as seen in Tchaikovsky's day. The musical score for the Sleeping Beauty ballet was the result of the same struggle we see everywhere, a struggle the USA has currently and commonly lost.

Sleeping Beauty Ballet

The link here is to the Wikipedia article dealing with the original ballet upon which the movie is based. One point is that most princess stories share many elements. Walt was fighting this in his own version. He wanted Sleeping beauty different than Cinderella and Snow White. But, princess stories are in effect a cluster, or an orchard, of similar stories. More Qu.

Princess stories make up some of the rides that go with the castle at Disneyland. More Qu.

Disney also shortened the original story of the Sleeping Beauty ballet. In the original score, everyone was asleep for 100 years. Changing the story this dramatically is perhaps why the original theater audiences did not like the film. But note, a 100 year sleep is yet another example of Qu. The royal court sleeping at the same time as the princess is the Qu's orchard. More Qu.

Russia?

If you read through the plot of the ballet, first published in 1889, you may also see that ballet as a prophetic parable about future Russian history. So 100 years from the publication of that ballet becomes the 100 years to the fall of communism, itself at the end of the prophetic 1000 years for Russia.

Russia was touched by evil with the Zionist Bolshevik's in 1917, though it had been going on more subtly since Napoleon.

Philip appears to be prophetic for current work to defeat the dragon. Growing in strength to defeat a dragon is... More Qu.

In any case, there is a robust set of Qu related stories behind the Sleeping Beauty Castle in the center of Disneyland theme park. It is like a beacon pointing at the entire family of stories that deal with coming of age. It is one of a cluster of princess stories.

Aramaic Roots

Our Paleo Bible work is ultimately based on the Aramaic manuscripts of the Bible passed to us by history. Most things that are thought to be true involving those texts should also be true of our Paleo work.

So I have been monitoring Youtube videos from Michael Wingert who is a professor of Aramaic. The link here is to a recent 27 minute video that he posted on Youtube. The main point of the video is to give 10 reasons why learning Aramaic is a good thing to do.

Most, but not all, of Wingert's reasons would apply equally well to Paleo. Paleo should be generally easier to learn because it uses a better alphabet. Learning Paleo will give up the ability to read other ancient Aramaic writings, especially from early church fathers. Instead, Paleo should gain ciphered documents, which is going to be better. In any case, most of his list applies to us as well.

The video itself is a count-down style format. So Wingert starts with reason number 10 and then goes down the list to reason number 1. That final reason is to be able to read the original New Testament.

In other videos Wingert has hinted he subscribes to the idea that the Old Testament was written in Hebrew first. I suspect in reality, the edits were in Hebrew first, which is outside of his frame of study.

The second to the last reason, so reason number 2, is the "root system" of Aramaic. The video does not spend much time on this point, so it is unclear why this is so important. Whatever this feature may be, Paleo will share the same characteristic. Wingert hints that the root system gives visibility to ancient thought. Interesting, but he is hiding the essential detail for this important point.

Spelling Defines Meaning

Wingert's point about roots is something I am coming to grips with as I work through the problem of the Paleo Lexicon for the Paleo Bible app. His understanding of the root system will probably be weaker than ours because we see Paleo word definitions as tied to the spelling.

No one that I know of normally discusses this aspect of ancient writings. But, Wingert is still warning us that there are shared roots across Aramaic terms that are NOT shared in other language systems. Those shared roots are some sort of special key to unlock the meaning of the text.

If 2 words share the same, say, 3 letter root, then those 2 words must also share a concept space defined by their spelling. Even if we don't initially understand why, those 2 words must be closely related to each other.

Names

So I finished my lexicon code rewrite this week and then started loading names into the lexicon. I am loading them in sequential order. So in order of first occurrence down through the text. Adam and Eden are the first 2 names.

Adam is already screwy because the BRB has many more uses of the name Adam than actually found in Paleo. I did not expect this. So I skipped ahead after Adam in order to think about this more. My general strategy on using the BRB to regulate Paleo Bible names may itself be trouble.

Eden: Oo-Du-Ne

So I moved on. I wanted to keep loading more names to see how this works. I fell into serious conceptual trouble as soon as I got to Eden. What I really ran into was a glaring example of Wingert's reason 2, shared roots.

In the BRB there are only 19 occurrences of Eden. But in Paleo there are very, very many more uses of Oo-Du-Ne. Those uses are spread all the way out, even into Revelation.

Eden is NOT a normal place name with a Yo-Wa ending typical of most places. Eden does not end in Mo which is also typical of place names. It is just a word. There is no grammar marking it as a place name.

I chased down other uses of that Paleo word. I never knew Eden was referenced in Revelation. Did you?

I had to stop lexicon work and start thinking about this vocabulary word, and how it is being translated.

The Garden

English readers know Eden as a garden. It is the place were Adam and Eve started out. It is eventually where those of us who are saved eventually end up. The beginning and ends of stories are often the same.

When Joshua tells Peter that Joshua will return later to take Peter with him, the implied destination of their travels is Eden.

Outside of the text, I believe Eden to be an actual place inside a moon of Saturn. It is mobile, like something out of a Star Wars movie. I've been taken there in a couple of prophetic dreams. So I understand the design of Eden. I will eventually build a model. It is known as the "blinking moon." It draws attention to itself for good reason.

So would we expect Eden to match some other vocabulary word in the Paleo Lexicon? Eden should not be that tricky.

Because English does not have the same shared root system as Paleo, there is NO conceptual match in English between Eden and any other thing in the text. English place names rarely have any conceptual meaning. "Seattle," for example, has no conceptual meaning. It is just a place name.

Turns out the same root for Eden is also translated as variations on the English word "time." You know it in Revelation as "a time, times and half a time."

Only the context determines if the word comes out as "Eden" or "time." Some grammatical forms do indicate time. There is no "the Eden." But, "the time" is common.

This is also not the same word for time used in compound words like the "Tent of Time." There is some other time vocabulary word over there.

So Where Was Adam?

So now we've stumbled into the good professor's "shared roots" reason 2 for learning Aramaic, so Paleo.

Ancient readers of the inspired text appear to know from the simple vocabulary word that Adam and Eve were "placed in time" at the start of the Bible. Adam and Eve must have existed outside of time "before" that happened. Even using "before" is a screwy idea since "before" implies time.

The only conceptual space I have to even frame this problem is from accounts I have seen of people who had near death experiences. They went somewhere "outside" of normal time. They spend a long time there. Then they returned to our normal time, without much of our time having passed.

Adam and Eve are apparently placed in time in some similar way. The place where they began is named "time" in honor of what happened there.

More Lexicon Changes

I am afraid this is only the 2nd Paleo name to get looked at. There are about 2300 names still to go.

Roots turn out to be a technical mess because there are apparently many mysterious meanings that are lost in English. I would now expect far fewer actual root words than we know in English. This is what the professor apparently understands well. He was just hinting at the surprise that awaits anyone who learns the language.

It looks like I still need yet better tooling for loading the lexicon. I need to play around some more. More on this in future blogs. In any case, I did update the Paleo Bible app this week.

Paleo Bible

The link here is to the Paleo Bible app. Permanent link as always is on paleo.in. The English interlinear for this week's release was generated from the new Lexicon code. There are a few important changes.

This revision intentionally does not give English for Paleo prefix words of 1 letter length. Instead you will see a "-" for the English. This follows the convention used with roots. The single dash used there implies the reader needs to think about the correct English.

The few paleo prefix words are very easy to learn and to guess. This removes clutter in the English. It also does not mess up special cases, where the English may want some special form for a single letter word.

We can all play with this form this week. We will see if this is a good idea or not.

Stats

I rewrote the statistics code to count values as they relate to the Paleo Bible itself. So stats are now calculated by scanning all the words in the actual displayed text of the app. This approach also counts single letter words. It better estimates the feel of the coverage actually in the app.

As of this week there are a total of 686,560 paleo words in the Paleo Bible. 518,303, so 75.49 %, have English interlinear data. 168,257, so 24.51 % are missing English. When English is missing, the word is flagged with a ?. Words flagged this way are not yet in the lexicon, so they may also be missing prefix parsing.

The lexicon itself has 351 actual root entries covering 9387 different inbound forms. There remains 41,532 inbound words that are not yet handled. 351 roots is enough to read about 3/4ths of the text. This is a rather interesting encouragement that learning the language should not be all that hard.

You can see by comparing stats, that those 41,532 need to be entered in order to explain those 168,247 that don't yet have English. So about a 4 to 1 ratio on average for words that remain. I do not know how many roots are still to be entered. Shared roots is now a thing.

The pace of work will slow down in order to fill in the rest of the text.

The lexicon needs a better conceptual tool to track the problem of seriously shared roots. I designed the tooling so far to work well with English, which is what I know. More on this later.

Match Dates

This past week we were watching for a change in kings between Monday and Tuesday. So on Tuesday, 2026-07-14 should be after Joash and on to the start of Amaziah's reign.

The main event had begun the day before when Trump resumed war against Iran. Trump began bombing targets around Iran. Trump issued a blockade against Iranian ships, especially the Iranian coast.

Iran's parliament declared the MoU over and started retaliating against American targets located across the region. Iran sank at least 1 ship that had been tricked by the USA into passing through Hormuz. Captains are now refusing to transit Hormuz except through Iranian waters under Iranian guidance. As a practical matter, Hormuz is closed.

Iran is carefully retaliating against US military targets in the region. Most of the main US bases in the area appear to have been struck by Iran. The USA appears to be out of important targets in Iran. Most of Iran's important military assets are underground. This as per Revelation 9.

There was also strong hints coming out of Yemen that there would be an attempt to close off passage of ships to and from the southern end of the Red Sea. As far as I know, this has not yet happened. Yemen may close that waterway as their own retaliation against Saudi Arabia for attacks on Yemen.

Trump was threatening to bomb civilian energy targets in Iran. Iran threatened to turn out the lights across the entire region should this happen. Trump seems to have backed down. But note, Trump tested a nuke, probably for use against Iran.

Netanyahu is expected in the USA for Graham's funeral, so the 2 men will likely agree on future war plans against Iran at that time.

Bottom line, war against Iran resumed at that prophetic date. It may be half-hearted on Trump's part until Netanyahu gives Trump new orders.

Watch Dates

Peeking ahead, we are now in the replay of the reign of Amaziah. The end of Amaziah's reign replays on 2026-08-11. Like Joash, Amaziah was assassinated, so a theme right now is funerals. We will return to that date as it gets closer.

There is a passage, 2 Kings 14:17, that times the death of a northern king as having happened 15 years before the death of Amaziah. This implies a weakly dated possible political death, or funeral, in the western world around Sunday, 2026-07-26.

This particular date has serious tolerance issues even with calculating that date because of 1 based math. We don't know with certainty the writer's time convention for these types of time references.

Graham's funeral is currently scheduled in DC for 2026-07-28. As long as that funeral does not move, this will be the prophetic match.

The next date on the Noah series for this year is during Tabernacles on Friday 2026-08-07, this is when the ark rested after 150 days. These 150 days are generally counting Iran war dates. There is a 5 month reference in Revelation 9:5. That passage hints at an unsuccessful war. It also has a more likely fulfillment with Noah in 2029.

The actual war against Iran began about 2 weeks earlier than expected by a Noah offset from 2029. So the actual war with Iran started early when Trump bombed Iran on 2026-02-28. We might now expect a 150 day headline to also land early. If so, that would be around Friday, 2026-07-24, which is the Friday after this blog goes out. This is aligning with the date given above.

It is also possible that the MoU based war delay provides a time gap. This might explain a gap in the war which might now close in. We'll consider this scenario after we see how these various dates unfold.

Followup to Babel

I recently went through the logic behind why the City of London is the best match to the Revelation 18 stories dealing with prophetic Babel.

This past week I saw a post on X dealing with NATO's weakest points, so those points which if struck conventionally, by Russia, would cause NATO great harm. A small cluster of 3 buildings in The city of London was the top of that list. The following link is to that post.

NATO Targets

Because money is just now records in computers, attacks on those computers, and the offices of the people who run them, become attacks on money itself.

Certain such targets would effectively defund NATO. Read the post if you are interested in the full list of specific targets.

If these targets were hit conventionally, the collateral damage would be minimized.

In my previous Revelation 18 post I was looking at maximal nuclear damage. This post is revealing a possible minimal conventional fire that would also fulfill Revelation 18.

This is a text book example of knowing the general prophetic story, but not knowing exactly how dramatically it will eventually fulfill.

Exactly how angry is Joshua with London and the people who rule from there?

Headline Review

The following caught my attention this week.

Death of Lindsey Graham

The link here is to an RT article summarizing the death of South Carolina Senator Lindsey Graham. He died Saturday night, July 11, 2026, at his house in Washington DC. He had just returned from Kiev. He was an anti-Russia war hawk. Trump ordered flags at half mast, in honor of a war criminal. I can't think of anything nice to say.

A Dog's Death

This link on X gives a 2 minute video of Alexander Dugin commentary on the death of Graham. Dugin could not think of anything nice to say either. Dugin is more polite than I would be.

Trump: Graham Blew Up

Trump answered a question about Graham, and explained that part of Graham literally blew up. Trump's mental condition looks unable to maintain reality. He may be telling us what really happened to Graham in Kiev. At least a part of him seems to have blown up.

Kiev Sequence

There are serious issues about the events surrounding Graham's death. If his funeral lands on the prophetic dates listed above, then he was killed by war. The prophetic story prevents his death as by a normal medical condition.

This post on X details a possible sequence of Graham's death. Note that the factory Graham visited, and the hotel where he would have likely stayed, were both blown up Friday night in Kiev by Russian missile and drone strikes.

These scenarios would explain a serious need for the USA to strongly cover up the actual death of Graham. Graham's death goes into the history books just like the assassination of President Kennedy. Nobody will ever know for sure what really happened.

Graham Won't Be Missed

The link here is to a long form article on UNZ which survey's Graham's sorry career. This article is barely polite. He will not be missed.

One curious detail is that Graham died about 2 days after his 71st birthday. Minding calendar issues, he basically lived only 70 years, and exactly 70 years.

Isaiah 23:15 calls out the years of a king as 70 years. Graham's life length now identifies him as a type of king. Graham's funeral can now match the prophetic of a northern king just fine.

This was a full natural life, but with no bonus time for him. Perhaps millions died because of his politics. Depending on what share of those deaths are personally attributed by heaven to him alone, he may never return again.

Peak Prosperity, Diesel Price Spike

The link here is to a Youtube video from Friday, July 10, 2026. Chris Martenson has been closely following oil prices. He believes they are being artificially manipulated down. This is being done for political reasons, so the public doesn't see the impact of Trump's war with Iran.

Artificially lowered prices will make the oil shock worse because demand is higher than it should be. (Naturally higher prices now would shed demand, preserving fuel.) In this video he shows the first real spike in Diesel prices. This may mark the "plague on livestock" which should accompany the funeral in Iran.

Dangerously Low

The link here is to a Daily Mail article that details a strange series of events at Gatwick Airport near London. Note that Gatwick is the smaller of London's 2 large airports. Gatwick specializes in international flights. I have flown through Gatwick several times on business trips many years ago.

That headline event involved an airplane that had trouble after landing. It was unable to turn the front nose in order to exit the runway. This meant it could not clear itself from the runway.

That first flight was now safely on the ground, with ground crew help. But, this backed up another 14 more flights that needed the now closed single runway at that airport. So those flights were put in a customary holding pattern waiting for the crews to finish clearing the runway.

9 of those backed up flights then declared 7700, so low fuel, emergencies. They had to be immediately rerouted to other airports before running out of fuel while still in the sky. All flights landed safely, but barely.

Europe is burning off the fuel normally kept in jet aircraft tanks for emergencies like this. This problem is a direct effect of fuel shortages caused by the war in Iran. Diesel and Jet Fuel shortages have been predicted for weeks.

This is a very real example that fuel shortages are going on. This is also a strong example that the industry is trying to hide their fuel trouble while creating a higher risk of fuel out crashes.

Europe should be canceling flights instead. They will be canceling flights here soon enough in any case. European politicians do not live in reality. I wonder at times if they were hired by the same folks that hired Trump. They all seem to think alike.

The fuel shortages are now really becoming a plague on livestock, a plague on transportation.

Nuke Test Off Florida

The link here is to a USGS page with the report of a M3.9 explosion off of Ponce Inlet Florida on Thursday afternoon, July 16, 2026. By looking at the signature of the quake they know this was not a natural quake, and say so on their report. Alternative media used to do this alone. Now the USGS is doing this. Nice. The USGS is showing that someone tested a nuke off Florida. This was NOT a small explosion.

Trump had said Iran would glow, so this is probably a US Nuke test. It was reported by USGS, so everyone knows. World War III is now beginning its climb to the general use of nuclear weapons.

US Downs Iran's Port Control Tower

The USA has been targeting the control tower where Iran monitors ship traffic through Hormuz. That tower has been out of commission for many days. The link here shows the final collapse. The USA has limited munitions. It is now attacking vanity targets. This is not a way to win a war.

Blocking SSL Certs

This link is to a post on Telegram by The Cradle. It documents how the USA (so Zionists, a sub type ultimately of Satanists) have blocked issuance of internet security certificates for Iran's FARS news agency.

The internet culture has a way of building around these sorts of troubles. In the end, evil might not be something that software engineers can design around.

Long term, we would expect the USA to eventually loose control over the Internet because of this. In the short term, this just looks petty. Printed Bibles are looking better and better all the time. I would not expect the internet as we know it now to survive Noah.

9 minus 1 equals 8

The absolute very best cat video I have seen in a long time. A great way to relieve war stress. Thankfully, the cat survived.

More Later,

Phil

Letter Qu

Phil Stone — Fri, 10 Jul 2026 19:16:38 GMT

This blog reintroduces the Paleo Letter Qu. Before that, more changes to the story order in the TT, and more updates to the Story Grid. Then status on the Paleo Bible and a headline review, especially the funeral in Iran.

TT Table of Contents

The link here is to the Table of Contents in the Testimony app. This page provides a nice overview of the sections and books that make up our current cut of inspired text.

Last week, the Gospel of John moved to the start of the New Testament. This caused Ryan to start looking at what stories set the context for the material in John. This led to another shuffle of the order of the central sections of The Testimony. That shuffle is live as this blog goes out.

There are 2 major changes worth noting. First, all the writings of the Old Testament prophets are now together in 1 section. This section of prophetic writing follows the historical record of the time of the kings. The second major change is that all the writings "from the east" are now bunched together ahead of the New Testament.

It may be easier to see in the Story Grid. But Isaiah and Jeremiah are on the Ha row. Ha is a coral. Isaiah was trapped in the city of Jerusalem. Jeremiah the same, and more specifically in the prison house. These are examples of corals that informed their lives.

Daniel and Ezekiel are on the The, or wheel. Ezekiel sees the wheel within a wheel. He also get a heavenly visitation. Daniel is similar, while also dealing with time.

The minor prophets are on the Yo row. Yo is a hand. So at least a set of writings. Their order remains unclear.

The center writings, of Psalms and Proverbs, have not changed position. They provide some sort of central interlude when viewed on the Story Grid.

Then what follows is a section of material written in the east. Job starts this section and is called out as a man in the east. Tobit, Esther and Ezra follow Job and together, these set the context for the New Testament.

Ezra, in particular, is the book that carries the commissioning letter that creates the religious system of Jerusalem that is running at the time of the Gospel of John. Of the available OT Books, Ezra does the best job of explaining where the New Testament temple system originally began.

Aside from the minor prophets and Psalms/Proverbs, there is a reasonable book chain running across this order, which is in part why Ryan felt confident in making this change.

This change in book order impacts the general contents of The Testimony, it also impacts the Sabbath Reads and it impacts the Story Grid.

Story Grid

The Story Grid app was also seriously updated this week. There had been a series of reports pages that were reached from a drop down menu at the center top of that app.

Those reports pages are now gone. The app itself is now a single page app like the clock and calendar. All interesting content is now reached by tapping on the tiles in the main grid. This should make the app much easier to fully understand, and much quicker to learn.

The content of the reports pages has been moved into the various story pop ups. The individual report content has been simplified and given a very nice geometric display.

In order to see this, select any story tile out in the middle of the app. You will now see a "tiles" choice in the popup. Select that choice and you will see the content that was once in the reports pages.

That new content has a very special design. The current tile in question is always in the center of that new display. Tiles that fold against the central square are placed geometrically to indicate what axis they fold along.

The row folding tiles are along the horizontal row of that tile's grid. Column folding tiles are along the vertical column of that tile's grid. Positive and Negative folding is shown on the positive and negative diagonals within that tiles display.

Not all tiles have all possible folds. This is especially so along the edges of the Story Grid itself. So some displays do not have the full set of 8 possible story pairs. When vine and river pair are the same, there is no duplication in the grid as shown.

Tiles are arranged out from the center based on direction and distance. So tiles from stories earlier in the Testimony will be above. Diagonal tiles are often found through strange wrapping rules. The new display format ignores the complexity in finding the folded tile, and instead presents the final answer just based on story distance from the current tile.

This new tiles layout is elegant and very nice. We reduced the number of tiles to a maximum of 8. These are just Vine and River pairing along the rows, columns and diagonals. These are the main story pairs and are enough for our intended use cases for this app.

The only story in the grid which does not have paired stories is the Quad-Quad story in the bottom right of the main grid. This is Hebrews, which we believe was Joshua's own writing. It is the story of belief. It is a story that must be taken on faith. Fun.

We are still debating certain technical issues dealing with making the app easier to navigate. I have some code work to do for this. More on that soon.

Trouble With Qu

Our current set of Paleo letter definitions was worked out soon after the first set of 3d models was worked out. This was over 15 years ago. We eventually found the Qu Map and could match those letters to objects on the ground. In the case of the Qu letter, the main national object is the Gateway Arch in Saint Louis. The main original concept for that letter was the idea of location.

At the time this was worked out, we assigned the Qu to a "brain." This assignment came because the Qu part of the Qu-Du object is the brain on the sower and reaper 3d models. This was very much an exception to the general letter identifications. Nowhere else on the sower and reaper models does any other letter gain a definition. Almost by definition, there has always been trouble with this identification. At the time we did this we had no other idea what the Qu letter might actually be.

As I have been loading Paleo words into the Lexicon, it finally dawned on me that we have the definition for this letter messed up. Let explain the conceptual problem and then how that problem gets fixed.

Very Low Tech

I continue to be impressed by how the words going into the lexicon are very low tech. The world view of the Paleo writing system is from the perspective of a shepherd. Abraham is perhaps the best reference example in the text. Though he seems to have grown up in Ur, most of his life is spent living in tents in Canaan.

Isaac and Jacob are not that much different. Though they all know of Egypt, and spent time there, the basic life of these men and their families takes place living in tents. Hebrews 11:8-10 stresses that Abraham and his heirs Isaac and Jacob lived in tents. Numbers 9:15-23 contains a long story about the time after the Exodus when everyone lived in tents. The text itself is calling out shepherd life as the frame for when much of the text was originally written.

This appears to be the general frame of living from which the vocabulary words are to be understood.

What sense does a brain make to people living in this sort of situation? If they eat internal organs, then sheep brain is a type of food. That is about all anyone cares about brains.

Stand: Qu-Mo

Last week's blog looked at variation on Qu-Mo, the word for "stand." So in that definition I used the "spine" from our old Qu letter definition in order to capture the idea of standing up.

Elder: Qu-Sha-Yo-Sha

This week I loaded a term used in the Revelation throne room, the term is usually translated "Elders." Though one interesting use of the same word was for an "eldest" son. Brain might apply to those in the throne room, but a teenage son is not a person where we would ascribe high thinking.

You can see from these examples that the concept behind the letter Qu is now some how related to some aspect of time. That concept is not really captured in the brain.

Names of Letters?

I also began to wonder if the letters of the alphabet have paleo words for their own names. I have loaded a few already. Oo-Ne-Ne for eyes. Ba-Yo-Ta for tent.

These words explain the item depicted in the 3d model for the letter. Maybe this is true for all the letters? We'll see once the Lexicon is fully loaded. But, even so, might there be such a word for Qu?

Tree: Qu-Yo-Sa

Then I remembered I had already loaded a candidate paleo word that starts with Qu. "Qu-Yo-Sa" is the root. "Qu-Yo-Sa-Wa" is the most common form, over 200 times. This latter form translates as "the tree."

The middle letter, the Yo is a possible added vowel. So with this example we don't know for sure if this is the correct spelling. So don't go memorize this yet. In the end it might be "Qu-Sa."

The Sa, by the way is a post. So this meaning of tree involves a post, which is nice. There is at least 1 other word for tree, so this is some special type of tree. We need to figure this out from the model.

The Design of Qu

I will post pictures on Telegram for those who may want to see this again. But if this is a tree, the lower part is the trunk. The upper part is 4 perhaps pruned branches with an enclosed area like a round tree top.

Trees that grow with that shape are called "fruit trees." This is not like a cedar tree. This Qu letter is depicting a cultivated, fruit bearing, tree.

I remember when I was young my grandmother taught me that fruit bearing trees naturally want to take on the shape of their fruit. This is how you can tell a pear tree from an apple tree just by looking at it. Optimal pruning wants to follow the natural design for the tree. So pear trees should be pruned in a pear shape, while apple and cherry trees should be pruned more like spheres.

So the 3d model of the Qu letter would point at trees that bear spherical fruit. Apples would be a scriptural term that might help specify the type. In any case, knowing this is a fruit bearing tree immediately helps explain the Qu letter much better than we have ever done before.

Qu: Time

So the Qu letter is showing up in words that seem to involve time in some way. Do fruit trees have a time component that would apply to terms like elders? Or teenaged sons?

Fruit bearing trees take time, measured in years, before they can bear abundant fruit. If you plant an apple seed you need to come back 5 or more years later before you start getting fruit from the tree. This is not like planting carrot seeds, where the crop is ready to eat in a short time.

The fruit from a fruit bearing tree is also where seeds are found. Some of them will be planted for the next generation of trees. But the entire cycle time for fruit trees is much, much longer than most other crops.

Going back to the idea of an eldest son, so a teen aged son, he will be going through puberty in that time of his life. Again, Qu is picking up the idea of a reproduction cycle measured in years.

In the case of an elder in the throne room, someone who has lived a long life, they now know Joshua well. They also have lived long enough to understand the world, especially evil, which normally hides.

Human elders are old enough that they can accurately reason about the evil in the world. They are old enough that they can now bear abundant intellectual fruit. Teenagers cannot do that. They don't have enough lived experiences.

Genesis 41:46 gives Joseph's age when he first appeared before Pharaoh. Joseph was 30 at that point. This is the start of having enough lived experiences to begin to think well about life. Having raised teenagers is perhaps another typical milestone for this. Numbers 4 has several references to age 30 being the starting age for serving in the Tabernacle. This is probably not an inspired passage, but even the uninspired writer understood human intellectual development.

Qu: Orchard

Fruit trees are not normally planted alone. They need to cross pollinate. So they are normally planted in orchards. They produce much more fruit individually if they are near other trees of the same type, which will also produce more fruit than if planted alone. The elders of Revelation become elders because they live and work together. Their throne room is their orchard. Being together in 1 place is very important.

This idea gives rise to what we see with the Qu Map. We see the pattern of the Qu letter modeled out in the design of the Qu Map. The Qu Map is picturing an orchard. Each tree in the orchard is a little different. They cross pollinate.

Let me be a little more precise. Someone running an actual orchard wants different types of trees. Cherries, for example ripen earliest because they are small. Various other types of fruit also ripen at different times. It is possible to design a real orchard where the harvesters are able to work different fruits across time in the order of the various harvest seasons.

So a real orchard wants male and female versions of each tree and it wants different types of trees. We see this in the Qu Map. The vine pairing of the letters is a male/female pairing system. Then there is an arrangement of more distinct types across the Qu Map. This all now makes perfect sense and relates back to the low-tech world of someone living in tents.

Orchards are a bother because they prevent the farmer from moving. But if the farmer can stay in 1 place, then the orchard eventually produces much fruit.

The center object wants to be a well. Real gardens in history were centered on wells to reduce the amount of work needed to carry water to each tree in the garden. We see this on the USA national Qu Map with Memphis. It is near the confluence of the Mississippi and Ohio rivers. It also has 4 famous aquifers.

So the idea of an orchard is the unifying idea that explains how location is such a common idea around the Qu letter.

Qu Map At Disneyland

One of the curious design features of the Disneyland Park is how the central castle, so the Qu ride, is itself made up of a collection of smaller rides. We have known this for a long time. Now we know why.

The Qu is a fruit tree, but it wants to be found in an orchard. So those central rides form the orchard that goes with the Qu. They naturally go with the castle. They cross pollinate each other. If you visit that part of the park you want to ride various rides while at the castle. You want to sample the orchard.

At the same time, of course, the entire Disneyland park is also arranged following a Qu Map. It too is an orchard. Keeping with this symbolic vocabulary, each of the major rides is a different type of fruit tree. Everything is starting to make sense.

From Joshua's spiritual perspective, a Qu-Map is where he is raising souls. Souls take years, really many life cycles, in order to fully develop. Just as there are different varieties of fruit trees, there must also be different varieties of souls. Male and female is just the first order division. "Tribes" will be the second order distinction for types of souls.

Qu-Du Pairing

On the vine exhibit the 2d drawn forms for the Qu and Du merge together into a specific 3d model. The Du is a sack or purse or bag.

Once we see the Qu as a fruit tree, the bag now has a reference. It is the real bag used to harvest fruit from trees in an orchard. Real harvesters use big bags that have straps that go over their shoulder. Conceptually, they gather the different fruits from the orchard. This is why that bag holds different things. A woman's purse, also holding many things, now becomes an excellent reference example.

Conversely, fruit from trees is placed in bags. This gives rise to an idea that bags imply storage. Fruit is usually preserved in various ways so it can be eaten outside of harvest season. Wine, so in a wine skin sort of bag, is another example.

Qu-Ku Pairing

On the River exhibit, we also see the Ku and Qu letters as pairing with each other. If you look down on the Qu object and then look down on the Ku object you can see these are the same 2d top shape. This is why they pair.

The Ku is a sprout or seedling. The Qu is a full grown tree. It should be easy to see how these pair. The reference seedling is now going to be something that can ultimately grow into a tree. A child can grow into an elder.

Main Street Adjustments

Fixing the definition of Qu also triggers corrections to the map of letters along Main Street in Disneyland.

The Qu letter had been assigned to a certain window on the west side of main street. It now moves to the full Emporium store front. This is a store front with "produce" from around the world. So an orchard.

The Re letter now moves to the gate where motor vehicles and the horse drawn street car enter main street. The Re is a head or ram and matches Detroit and vehicles. They move around like cattle. In Disneyland, of course, they move up and down main street after entering from that gate.

On the east side of the street the film theater now becomes the Du letter. That theater is the bag keeping harvested fruit. This is where early, preserved, cartoons are shown. This was the first crop that started the Disney company.

The Ge, so scythe, is shifting to what was once the main street tobacco shop, now just the statue of a chief out front. Traditionally tobacco shops used a statue of a Native American chief as an icon. Think peace pipes. The Ge location on the national Qu Map is in North Carolina, once the home of tobacco, harvested with a big knife, the Ge.

National Qu Map Adjustments

This change in Qu adjusts 2 locations on the national USA Qu Map. Mostly this impacts Saint Louis. But first let me touch on Washington DC. This is the Du, or purse. Now that we see a harvester's bag as the reference purse, we can think better about Washington DC.

Fixing Washington DC

Washington DC is basically where national taxes are collected. Traditionally the US Treasury was the actual place of those collections. So the Du is a harvester's bag, and so the match to taxes collected in DC gets much more clearly defined.

Taxes are coming in from across the entire orchard, so from all locations on the national Qu Map. So this now ties to Washington DC in a much more specific way. It is the place for the harvester within the orchard itself.

Besides money, we can see the same fruit from the orchard will also be the elected officials who come in from around the country. Each is different. Each has a different personality. Each has different priorities.

They meet at the capital building in the center of Washington DC. These days we might say they have gone to seed, but I digress. In any case, we can now define the primary function at Washington DC in terms of how it relates to the rest of the USA, the rest of the national Qu Map.

After adjusting the Du to the film theater on main street in Disney we can now think of national politics as a type of political theater. We don't actually know what goes on in secret in DC. Just like we don't know for sure what is in some woman's purse.

The Smithsonian Institution is now also important to DC. Bags preserve harvested fruit. So the museum system of Washington DC now also fits in nicely with the letter definition. The Smithsonian is preserving the fruit of the labors of Americans from across the entire Qu Map for the USA.

Fixing Saint Louis

Perhaps the biggest problem with our national Qu Map has been understanding the city of Saint Louis. The Gateway Arch is the obvious Qu letter in terms of modern iconography for the city. When including the underground spaces below that arch, it is a nearly perfect Qu letter.

But, how else does the city map the Qu letter? Most other cities on the map have pretty good and pretty obvious matches to the meaning of their respective letters. We have previously been unable to figure out how the Qu letter goes with the history and character of Saint Louis. No offense intended, but we have not been able to find any evidence of a brain there.

The answer is going to be easy to see once we get our head around the 1904 Saint Louis Worlds Fair that was held in "Forest Park" in the summer and fall of 1904.

Forest Park, of course, is already a hint at the orchard sense of the Qu letter. So we are already fixing a long standing problem.

That fair was celebrating the 100th anniversary of the Louisiana Purchase. That huge chunk of land will be something like the national "orchard." The Great Plains are a massively productive food growing territory that came into the country with that purchase. The Qu letter implies the orchard, so there is the match to Saint Louis.

The city of Saint Louis, of course, was named after a French king by the same name. This links the city to the nation from whom that land was purchased. Everything is starting to click together and make prophetic sense.

World Fair Documentary (TV, 1962)

World Fair Documentary (Modern)

The links here are to a pair of documentaries on the 1904 worlds fair in Saint Louis. The first is to a 1962 TV documentary that includes historical footage of the fair itself. This is especially interesting because it includes early moving pictures of various scenes at the fair. This first video includes a brief interview of a woman who had attended the fair when she was young. This was a real place, with real people.

The second video is a more modern documentary with a good selection of photos from the fair. This is a more modern academic analysis of the fair itself. It discusses many of the cultural impacts the fair had on what was a quickly developing country that was shaking off the effects of the civil war.

The first documentary is about 1 hour. The second documentary is about 2 hours. If you only have time for 1 of them, I would recommend the second. It is more technical, more like a modern classroom, in terms of the known history of the fair and the politics and reasons it was built.

Because Saint Louis has been a long standing problem on our national Qu Map understanding, I am going long on this linked content for this blog. Anyone really following the national USA Qu Map study should really watch at least the 2nd of these videos. What follows here are written notes mostly taken from those documentaries.

Interesting Details

At the time of the fair, Saint Louis was considered to be the central marketplace for half of the mid west. The city itself was in competition with Chicago. Ultimately, Chicago grew larger than Saint Louis because rail traffic pinched south of the Great Lakes and so funneled through Chicago. The 1904 Worlds Fair in Saint Louis was intended to put Saint Louis back on the map for national attention. 20,000,000 guests visited the fair itself. (This is probably the turnstile number, actual people was probably fewer.)

In order to outclass the Chicago World's Fair, which had been held about 10 years earlier, everything in the Saint Louis fair needed to be bigger and better than Chicago. Saint Louis's fair would become the biggest World's Fair ever held. It had been planned for 1903, the anniversary of the Louisiana Purchase itself, but construction ran long, so opening was delayed to 1904.

The Federal Government matched the locally raised funds. The feds kicked in because this was a celebration of the expansion of the country itself. This national funding is the Qu-Du pairing of the vine across the national USA Qu Map back to Washington DC.

The River Qu-Ku pair links Saint Louis to Portland and Seattle. On the ground, this was via the Oregon Trail across the territory of that same Louisiana Purchase. So we finally can see both expected city pairs for Saint Louis. We could not do this before.

Ferris Wheel

Perhaps the most iconic exhibit at the fair was a massive Ferris Wheel. This was the largest ever built. It had originally been built for the Chicago World's Fair. It was moved to Saint Louis for a second life.

Each gondola on the wheel was the size of a small railroad car. That ride would be the standing Qu of the Qu Map for 1904. Ferris wheels became famous and common after that 1904 fair. Most county fairs in the USA now see Ferris Wheels as common rides.

The current Gateway Arch in Saint Louis, our standing Qu on the current national map, was most likely inspired by that earlier Ferris Wheel ride at the 1904 fair.

Immense Size

We like finding world class superlatives on Qu Map locations. There was a 3 way competition between Paris and Chicago and Saint Louis. The Eiffel Tower was another competing icon that drove the immense size of the Saint Louis fair. Matching the Eiffel tower was in part satisfied by the Ferris Wheel. The 2 documentaries given above disagree on the size. The larger number given was around 1500 acres.

There were also 1500 buildings constructed for this fair. These contained exhibits from around the world. Produce, and other engineered products, were a prominent feature of this fair. Most famous American inventors of the time were personally at the fair. This included Edison and Bell. Again, like a Qu Map, this fair is looking like a massive orchard. A massive exhibit of produce and product.

Disney Affinity

As you watch pictures and events at the fair you will probably see echos of the fair at Disneyland in California. Walt usually took inspiration from other places, and you can see many parallels between scenes at Saint Louis and what Walt opened at Disneyland about 50 years later.

Walt was born in Chicago in 1901. At age 4, he moved with his family to Marceline, a town in central Missouri. Hearing personal accounts from people who attended that fair probably impacted Walt's young life. It would have been a source of regional pride, even if he was too young to have taken it all in. It may be the fundamental inspiration for building Disneyland, a type of permanent worlds fair.

Both the Saint Louis 1904 fair and Disneyland look to be Qu Maps in concept. Walt's version matches the Qu Map in a very technical way. I would need better documentation to study the 1904 fair map to see if it maps geographically to a Qu Map.

Note the "Pike" at Saint Louis becomes "Main Street" at Disneyland. Both of these are the "trunk" of the Qu Map. Main Street at Disneyland is kept open after rides close. The mile long Pike at the fair also remained open after the other exhibits closed. One end of the Pike had a castle from the alps, similar to the castle at Disneyland. There was also a fake mountain at the fair, like Matterhorn at Disneyland. As you watch the videos you can see several other matches to Disneyland rides.

Modern Tech

The 1904 fair included considerable examples of the then new use of electricity and electric lighting. Though the tech itself was around 25 years old at the time, the use in decoration, including out doors and under water, was something very new. Edison himself was a consultant on the lighting problems presented by the fair. Many fair goers from small towns did not yet have electric service in their towns or houses.

Olympics

The Olympic Games system was also just beginning. The fair was the venue for the 3rd modern Olympics. This was the first set of games in the Americas. There was a rudimentary set of games, like marathon and swimming. This was the first games when trophies were awarded. The fair introduced the concept of the Olympic games to the American public. Eventually Olympic games grew larger and are now prevented from happening in the same cities as world's fairs.

Anthropology

There were also a set of "anthropology exhibits" in which around 2000 people from various cultures around the world were brought in so they could show their cultures to fair goers.

By modern standards this is now considered a troubling aspect of the legacy of the fair. Modern attempts at the same purpose usually bring in examples of high culture. The Saint Louis fair brought in examples of low culture. Watch the videos to see what I mean.

To most fair goers, these were the most well remembered exhibits because of how different these people were from average Americans. Remember, there was no video in those days. For average fair goers there was no way to learn about foreign cultures. Americans still have trouble with learning about foreign cultures.

Ultimately, the Qu Map of earth is Joshua raising souls. So this is an interesting prophetic match, even if the 1904 fair was not well executed by modern standards.

Disneyland, our other reference Qu Map park, represents cultures from around the world as well. Disney learned from Saint Louis, and does a much better job of this, without the demeaning components as seen in 1904 in Saint Louis.

Food

Food was another major component of the fair. Many modern foods were first introduced, or at least popularized, at the fair. There were 130 places where guests could eat. Those places are said to have employed around 25,000 food service workers of various types.

The ultimate Qu Map reference is to an orchard. So diverse foods is a major marker for a Qu letter orchard. Disneyland also has lots of different types of food. This is an aspect of Disneyland we don't normally think about. Epcot in Florida has an annual food fair, which is a match to the theme of orchard.

Final Notes

In the end, the 1904 fair in Saint Louis is considered the pinnacle of all worlds fairs. Modern Disney parks are essentially permanently standing versions of world fairs.

The 1904 World Fair in Saint Louis is a fitting marker for the "orchard" of the Qu Map in Saint Louis. It provides a more robust marker that matches the meaning of the Qu letter. The Saint Louis Gateway Arch is the standing reminder for that same letter.

Saint Louis Art Museum

The modern location of the 1904 world's fair is now a large park complex north of I-64, west of downtown Saint Louis. This modern park is smaller than the original fair. Some of the acreage was sold for houses.

The link here is to Google Maps pinned to the art museum building which was built for the fair and still stands. This was the only building at the fair made out of concrete. This so it had no fire risk to the borrowed art displayed at the fair.

You can zoom out and see there are many other places to visit across the former grounds of the 1904 fair. This includes a zoo, golf courses, lakes and other things. This park complex is perhaps the best location in the Saint Louis metro area for a precise Qu Map national target.

Six Flags Missouri

In 1971 the Six Flags theme park was built west of Saint Louis. This is along I-44. The link here is again to Google maps, but pinned on Six Flags. This park should perhaps be considered part of this national Qu-Map location. It captures the regional heritage of the 1904 fair.

Shop Work: Problems with Paleo Names

I have continued to work on tooling for the lexicon that is driving the new Paleo Bible app. This week I put major attention into the problem of names. I also started rebuilding the software behind the lexicon.

As I was playing around with the Paleo Bible at the end of last week I realized I really wanted most names entered into the Lexicon. Names function something like an address system. If you know who is involved in a certain story, you may then generally already know the story. To paraphrase an old friend of mine, if you cannot name it, you cannot cut it.

I have also been tracking how many roots are entered into the Lexicon. I am doing this to monitor how much learning is needed to learn Paleo. Names do not really impact learning difficulty. They form a different body of terms that do not add complexity in the grammar. They have no suffixes, for example. They only use the standard prefixes which are easy to spot. So the learning issues with names are not the same as other vocabulary.

Even when it comes to printed lexicons for stock Bibles, it is possible to purchase "names dictionaries" which just deal with names as a separate type of writing. So dealing with names really is a special case problem.

So my counting of roots needs to be changed. I need to count names as a special type of word. They need to grouped together and treated as a special type of word. Even their entry into the lexicon presents special challenges.

Before this week, names were being sprinkled into the lexicon. This makes management of the English for names more difficult. The English for names is itself irregular. This set of words needs special care.

Previously, if I knew the name, I just put it in. If I didn't know the English for a name, in order to save time, I just followed the BAU text's English for the name. That text is very strange when it comes to names. This itself was yet another big and growing problem. Any time I see myself trying to "save time" I know I am in some sort of trouble.

Fixing Names

So I started playing around with this problem to see what I could do to handle names in a better way. The first step was to use the BRB text to survey the problem. I wrote some code to find all names, remember all the specific cites and then display them in order of first occurrence.

By that work I found there are about 2300 names. (Depends on if counting place names and people names or not.)

Once that was running, I realized I wanted to use the BRB set of English names in the Paleo Bible. The BRB has a quirky set of English names. But, by using that set, both bibles would be in agreement. It would also then be trivially easy to "de-quirk" names in both texts should Ryan ever want to do that.

So this sets an interesting strategy for loading all names in the Paleo Bible. For normal words, I need to start with a Paleo root and then go find the English. For names I need to start with the BRB English and then go find the Paleo.

Shortening a longer story, I took the names from the BRB and generated a complete set of configuration files for Paleo Bible lexicon entries. Those files now already include all of those BRB English language names.

These lexicon entries also include all the specific cites where those names were found in the BRB. This cite data can be used to handle problems where certain names are also common vocabulary words. Any given paleo word is only really a name when there is a cite covering it in the BRB. Otherwise, the word is a common word and it should be looked up in the normal lexicon.

After creating all those configuration files, all that remains is adding the Paleo spelling for those otherwise now finished lexicon entries. This saves much typing.

At least another week before Paleo Bible gets updates. More on this next time.

King Joash

In terms of our normal timeline watch dates, we are nearing the end of the replay of the reign of King Joash. The final days for that king are next week, those watch dates are given below.

There are 2 main stories within Joash's life that replayed this week. The first is how Joash commissioned the rebuilding of the temple in Jerusalem. The second key point is that he was assassinated by Zionist officials.

In 2002 this same prophetic season replayed when IDF soldiers entered Bethlehem. They were chasing Palestinians. That triggered a multi-day standoff at the ancient church built over the traditional location of Jesus' birth. The IDF wanted Palestinians who were hiding inside.

What we saw this past week was a much bigger and grander version of the same thing.

It was Zionists, ultimately Trump, who replayed the assassination of Joash. This was new this time around, and a closer prophetic match than seen in 2002.

The IDF is again on the hunt. This time they want to capture the entire Iranian political class, and replace them with Zionist puppets. That part of the Zionist war against Iran still continues.

The various religious venues for the funeral are matching the church in Bethlehem from 2002. In terms of temple rebuilding, Iran in effect "rebuilt" some of the funeral venues, especially the final burial location.

This side of the prophetic story is more important. Headlines this week ultimately set up for a future rebuilding of Temple Mount. That future detail matters. First let me step through the main events this week.

Iranian Funeral

On February 28, 2026, Trump assassinated the spiritual and ultimate political head of Iran. Because of the war that followed, the Iranians delayed the funeral until this past week. This delay brings this assassination under the time and prophetic stories of the assassination of king Joash.

The funeral began in Tehran, and then moved through various venues in Iran, then Iraq, and then back to the final burial location in Iran.

In the end, an estimated 43 million people were involved in the funeral itself. These counts are mostly taken from cell phone data taken at specific venues and along the route of the funeral procession.

This is by far a world record in terms of the numbers involved in the funeral. The deaths of Popes are similar, but those funerals have never reached such large numbers of people.

News Stream Optics

Most of the news streams that were covering the funeral were also tracking general headlines. So what the world saw online was pictures of huge crowds weeping over Trump's murder victim. Then those same online news streams showed Trump acting like an idiot or spoiled brat or both. In any case, Trump showed no remorse.

Iran gained strong and obvious political support for whatever may come in the future war against the Zionist west. It was unclear if they had such support before. Now they clearly have such support. The Iranian government has gained a political mandate to go deal with Trump and the rest of the Zionists. Iran can now fulfill its ultimate prophetic destiny as called out in the Book of Revelation.

Let me give some key links to various media that frames details of this remarkable event.

Galloway/Marandi

The link here is to a George Galloway video on Youtube. This was the first video I saw with a personal report on the ground at the funeral. The core ideas that would develop over the week were evident right away.

Galloway let Marandi talk. Marandi ultimately commented about how he was seeing people raise a certain flag which in that culture is a call for revenge.

This red flag, calling for revenge, was seen later in all videos that followed across the week. The public in Iran wants revenge. They have given the Iranian government permission to carry it out.

Revenge

The link here is to an Iran Military channel post on Telegram. You can see some English graffiti and some examples of the red flag that calls for revenge.

Larry Johnson: Pearl Harbor

Larry Johnson picked up on this idea and made a video, linked here, that likens Trump's February 28, 2026, bombing and killing of Iran's leadership as the equivalent of Japan's strike on Pearl Harbor.

This was the first time I had seen this story taken to its natural conclusion. The United States public immediately wanted revenge after Pearl Harbor. So too does most of the public in the Middle East.

Remember that we are watching for general themes from both World War I and World War II as showing up again now. Replaying of the World Wars is the main theme for our time. It will run out into the 2030s. This is the season of the prophetic application of resurrection Sunday. This is the time when Joshua told his disciples to remember all that had happened over the previous... 210+ years.

Pearl Harbor was a defining moment because it brought the USA into the war. This was not the main war, Russia would be the ultimate party to conquer Berlin. Iran is secondary to the war in Europe. But Trump's bombing of Iran does mark another event from World War II that now has a very clear match in our day.

Future Temple Rebuilding

The main timeline event in the time of Joash is a reference in 2 Kings 12:6 about a temple reconstruction that happened in the days of that king. If you read the whole story you can see how it was not actually completed at the expected time. Instead Joash had to get involved and make it happen later. All that is dated in that story is just preparation for rebuilding.

If you keep reading, you can also see how Joash died. Joash was killed by a conspiracy between various government officials.

It is hard to think this way, but the king's family are not really Zionists. The Kings are just heirs of David from Judah. The officials that carried out the assassination were Jebusites, whom we would call Zionists today.

We just watched the burial of the leader of Iran who was murdered like Joash by a conspiracy of Zionists. In this case, the conspirators were Trump and someone from Israel, maybe Netanyahu, maybe someone else.

What we just saw this past week with the funeral in Iran is ultimately the rebuilding of the Temple. This is the other story with king Joash. By this I mean the headline where some eventual Persian King can authorize reconstruction. That future Iranian king just got all the political support he needs to carry out that work.

Of course the Dome of the Rock still stands. Israel is still working to get rid of it. By watching the funeral this week, we are looking ahead at what is to come. Iran will eventually rebuild, just like Joash, they would be expected to rebuild the Dome of the Rock.

Plague on Livestock

Late last year Ryan and I sketched out the likely map of the Plagues on Egypt to the Jerusalem Kings stories as found in the text. King Joash was called out as the likely king for the replay of the plague on livestock.

By attacking Iran during the funeral, Trump proved his evil nature. The Iranians cannot trust him to make a deal and keep it. The Iranians must either defeat the Zionists or be defeated themselves.

Low grade war will likely involve keeping shut the oil flow of Hormuz. Livestock is likely symbolic for automobiles. Those machines will now be plagued by events this past week.

We are now in early July when fuel was expected to become hard to find in the USA. This is an important headline to keep tracking. Iran controls the oil, there is no dispute on this point. Where and when the livestock stops moving is still uncertain. Other parts of the world may see oil shortages before the USA.

Watch Dates

We are now watching 2026-07-13 as the prophetic replay of the end of the reign of king Joash. The following day, so 2026-07-14, is the start of Amaziah's reign. These dates are the Monday and Tuesday after this blog goes out. The funeral in Iran should be mostly over, and the Iranian government will be less restrained.

Amaziah has a generally long reign, ending for us on 2026-08-11. So whatever follows will run for about a month.

The most obvious venue is to watch for a change in the conditions of the wars in Ukraine and/or Iran. Surprises can come from anywhere.

Headline Review

The following other headlines caught my attention this week.

Blockade on Yemen

The link here is just a note that the Iranians were able to break the blockade imposed on flights to Yemen. Rubio recently discussed wanting to take out Yemen by secret means. Instead the opposite is happening.

The King No Longer Defends The Faith

The link here has an interesting note about how the King is no longer the defender of the Christian faith. Given that London is the seat of prophetic Babel, I am not all that surprised. If he won't defend the faith, is Joshua going to defend his city? This is a setup for the Babel stories from the Book of Revelation.

Aalo Atomics at Idaho National Laboratories

The national Qu Map for the USA puts the Ze letter at Boise. The buckle can be thought of as a lock, which closes off places the public cannot go.

Idaho National Laboratories is the main marker on the ground. For good reasons, this is mostly located in a desert. (Sill good for spotting UFOs if you know where to camp.)

In any case the link here is to a new startup which got their new reactor running for the first time at that location. That company is based in Austin, Texas. There were 3 other companies that did the same in the previous few weeks.

Imagine the mess created by ground war fighting around nuclear plants. None of this is a good thing. This is a technology that should forever remain behind lock and key. They were racing to get this done by the 4th of July as per an executive order signed by... Trump. (Why would I be surprised.)

Red Card Controversy

The link here is to a post on Telegram with a summary of the Red Card Controversy. In the most simple terms, Trump cheated. He used his power to get a US player reinstated by FIFA. This, of course, meant the US team could no longer win the tournament by fair play. This probably wrecked the moral of the US team. The US team proceeded to badly loose their next game.

This controversy was going on at the same time as the world was watching the funeral in Iran for Trump's main murder victim. So the world now sees him as a murderer and a cheat.

Nord Stream Insurance

The main industry of Babel, so London, is insurance. This is how they take a cut on all shipping planet wide. Insurance rates through Hormuz are normally 2 percent of the value of the ship. 7 percent here recently because of the war.

London also insures other shipping related things. So the link here is to a lawsuit filed against insurance companies in London in order to get an insurance payout to fix the Nord Stream pipeline.

Would we expect Babylonian Judges to be fair? They protect their own.

We should not expect righteousness from the capital of evil.

Follow Up on Ford

In a recent blog I covered how Trump had asked Ford to learn to fly in order to make weapons to bomb Russia. This is already nuts.

The link here is a report on how Ford recently fired a diabetic employee for eating a cookie. Someone thought the employee stole the cookie. They did not bother to even ask. You can read the sorry details yourself. The fired employee got a better job closer to home, so it worked out better for him.

Why are so many American companies so badly managed?

Final Tally: 43 million

Final tally on the funeral procession now coming. Estimated at around 43 million people. Nothing like it in history.

MoU Over

Before the funeral was over, before Trump's victim was even safely buried in the ground, Trump had the US military bombing targets in southern Iran. Why should we be surprised? The link here was the first report that the Iranians now consider MoU as effectively over.

Many are now expecting the war to resume soon. Watch the prophetic dates early next week as a possible time for this.

We might expect Iran to take out all oil production equipment across the Middle East. This will eventually crash the dollar because US Government debt interest payments are ultimately funded by the profits from Arab oil. At least this is a plague on livestock.

We should probably be preparing for a depression. As a reminder, there was a depression between World War I and World War II. This is another part of history that should repeat in some way in our time.

This is about the longest blog I have ever written. This has been a very crazy week.

Less Later,

Phil

Arise!

Phil Stone — Fri, 03 Jul 2026 19:43:30 GMT

In this blog we use the new Paleo Bible app to look at the Paleo word for arise. Before that more updates to the Story Grid and updates to the Paleo Bible app itself. Then feedback from last week's blog and a brief headline review.

Story Grid

The link here is to Row 15 in the Story Grid app. This is the first row in the New Testament, so the Gospel of John.

Ryan has made some technical changes to all the row pop ups in the app. But this row is starting to get settled out and starting to get notes. He has changed how the row related story folding notes are displayed. This has become very much easier to follow.

If you tap on the box at the left side of that row, you will see the popup for row related notes. In the top edge of that row are 2 choices where the action has been this week. The "V Pairs" and "R Pairs" choices have been reworked.

These 2 choices now use tables for formatting the various story pairs across the row. This had been done with standard prose indented lists. Using tables brings a rather dramatic improvement in following what is going on in these notes.

V Pairs

The "V Pairs" are for Vine Pairs. This means the stories are matched in the same way as the letters are paired on the Vine Exhibit. Stated a little more simply, the stories are paired as though the row was folded in half. The middle of the row is pulled down in the displayed table.

This pairing pattern is similar to the well know Chiastic structure that has be known for centuries in passages across the text. At this level of analysis, that same internal structural pattern can now be seen as operating at the level of stories.

So if you tap on the "V Pairs" choice in that popup you will see a nicely formatted table. There are 2 columns. Stories from the row start on the top left square in that table. They progress down the left side. At the bottom they reverse and come back up the right side.

Rows are colored by their vowel, which gives the popup the same sort of look and feel as the base table itself. This is also very visually appealing and invites users to tap and explore.

If you tap on any given row, that row opens up and shows specific pairing notes. Tap again to hide the notes.

Notes are being rewritten to only show why the stories pair together. This is basically the place where story placement evidence is presented. In previous iterations the notes were less focused in terms of purpose.

R Pairs

The "R Pairs" choice at the top of that same row popup works similarly. In this case the story pairing is following the letter pairing of the River Exhibit. In order to distinguish the difference from the V Pairs table, the River Pairs are colored in alternating shades of blue. This to remind of water flowing down a river.

Conceptually, when building an ideal curriculum, we would expect introduction to the river exhibit to happen before students eventually explore the nuances of these tables. So the River Exhibit will have become known before going deep into the lessons of these tables.

Just like the V Pairs table, the rows can be tapped in order to display the specific notes. Tapped again in order to hide the notes.

Ryan has been reworking the notes in row 15, the Sa row, as he has been working carefully through John. This is probably pretty close to the final list of stories and their placement. This is nice to see in a middle row in the table because it becomes an anchor point for working out stories along other rows.

Paleo Bible

The link here is to the Paleo Bible app. I have been working on a long list of technical issues with this app. Some are in the lexicon that goes with the manuscript. Some issues are in the app itself.

This week, the Lexicon code now has a long list of internal audits that fail immediately after words are added or changed. So the double question mark case should no longer occur.

On the Paleo Bible app side of the work, I have changed the app to client side rendering. This reduces the installed size of the app from about 160 megabytes to around 35 megabytes. This is a faster load and is easier on our web server. I would expect the size to climb back as we add more markup to the running text.

Client side rendering means there are phases to the rendering process. On screen render times are longer than before. For small books this does not matter at all. For longer books, like Jeremiah and Psalms, the load times are noticeable.

To make this run better I added support for a spinner that shows up when books are loaded from storage. The user interface is better because it shows something is going on.

The spinner is touchy new code. The challenging design issue is if someone moves away from an unfinished page load. It may still have bugs I haven't yet seen. I will be monitoring it for trouble for awhile. I have tested it on Brave on a desktop PC. Let me know if serious trouble elsewhere.

Future Formatting

As a reminder, the app is currently using a verse-per-line format. This is only a shim. It will eventually end up under option control to look more conventional. The rendering system for the manuscript is already configured to handle all the same formatting tags as found in the BRB. That formatting just needs to be added to the Paleo Bible manuscript. This is a future work item.

Once more of the BRB level of formatting is added to the Paleo Bible, then options will control exact formatting. At present, there are story headings in the Paleo Bible and then only verse-per-line formatting. Verse numbers are on the left hand side of each page. This allows easier navigation until other parts of the app are finished.

Word Level Addressing

Functionally, this week, the Paleo Bible app gained word level addressing. This is an important new feature because it gives us a way to identify any word by address without needing to know anything else about the Paleo language.

So we can start to use the app to explore anywhere we want and have at least a way to point at specific words by address. Word level addressing implies all sorts of technical issues we've never faced before. Let me catch you up on the problems.

Word Address Notation

So you can use the Paleo Bible app and explore anywhere you want. You will see word level addressing everywhere. But, I would suggest looking at Mark. We will return to Mark below.

Each word in each verse now has a number assigned. This shows up as a superscript just ahead of each Paleo word in a verse.

These word numbers are matched to, and counting, the inbound words as passed by history. So they are always going to count from 1 and go up by 1 for each historical word as we find them.

So if you open up Mark in the Paleo Bible linked above, you will see Mark chapter 1, verse 1 at the top of the page. You will then see a row of Paleo words for that first verse. Each word has a superscript number in front of the Paleo word itself.

Variant Manuscripts

Note there is still a variant manuscript study that needs to be done with the inbound texts. When that work item happens, word numbers may shift around on the verses that have textual variants.

So in an absolute sense, these new numbers are not fully fixed. Overall manuscript versification also still needs to be checked. So, for now, word numbers are pretty stable, but not absolutely stable.

Split Words

If you go look again at that first verse in Mark 1:1 you will see that word 3 actually has a 3a and a 3b. This word level address notation is important. It indicates that history passed us 1 single word and that our lexicon system has broken that single word into 2 different parts. Those parts are labeled here as 3a and 3b. In this case 3a is the prefix "Du" commonly translated in English as "of." 3b is the name "Joshua."

The designation of a and b means there is a current interpretive step going on within our work. This is not how history views this compound word.

You will see these sub word addresses throughout the text. All prefixes are split off. Some whole compound words are also split off.

Future Work

The big project still ahead is the audit work. This will be running through the text at a letter level, leaving behind more markup that will indicate what is going on with inspiration.

Future work gets very much easier once each Paleo word has an assigned word level address and has some assigned rough-cut English.

This is why some of this work is happening in a strange order. I am still focused on the Lexicon, but I am stopping to work on other technical issues, like word addressing and spinners, as these issues crop up and bother me.

Addressing Conventions

So we just added word level addressing to the running text. How do we write a scripture citation that is accurate to the word?

This is one of the many strange problems we are likely to encounter along the way. An old machinist once told me, if you "can't measure it, you can't cut it." (His machines built measuring tapes. There was a double pun in his assertion.) We need to be able to measure to any given word in the entire text.

This means we need to write cites that are word accurate. So as a convention, I am extending normal Bible citations to include word level addressing.

Mark 1:1~3 is an example of a cite that calls out word 3 in Mark chapter 1 verse 1. This allows us to write about and cite individual words. This particular cite is to the first reference to Joshua's name in that same first verse in that first chapter of the Book of Mark.

We can then extend this same notation by adding sub-word identifiers to the cite. If we want to cite the prefix, then Mark 1:1~3a gets us to the Du prefix. Mark 1:1~3b gets us to Joshua's name.

As the Lexicon can also split up compound words, the sub word marks are not always to prefixes.

Some prefixes bury compound words. "Ku-Lu-Mo-Du-Mo" is "all" compounded with "thing." It is written as a compound word, but also written as 2 words. See Genesis 11:6~16 for the first example. I am generally splitting anything that remotely looks compounded. Splitting compound words gets the splits setup for specific English.

One of the early phases of the audit will address the problem of prefixes and compound words. The audit conceptually has the freedom to pull prefixes back tight against the root.

Ambiguity

The way the inbound text jams prefix letters onto the root makes the text fundamentally ambiguous as passed by history. Some prefix letters are also the first letters of real roots. Some real roots are short enough that the prefix/root pair has clear meaning only when understood based on the sentence where it is found.

Understanding this problem has given me a good reason to eventually survey the vowel marks to see if any of those disambiguate the historical text. More on that later. I have started reserving, so keeping out of the Lexicon, certain inbound words for future study because of this problem.

So when the Lexicon system gives instruction about a prefix letter, or compound word, it causes that letter to become a stand alone word in the running text. This is ultimately what creates sub-word addresses.

Whenever you see word level addressing with sub word parts, you can know this was only a single word in history. So there is currently some risk that the split is being done incorrectly.

Maybe Mark 1:1~3a should be "Du-Yo" and Mark 1:1~3b should be "Sha-Ve-Oo." In this case that choice is absurd. But not always. So sub word addresses are a flag of possible ambiguity which may ultimately flag a mistake in the lexicon.

Filling In Sections

I have been working the lexicon by starting with the most frequent unique inbound word. I find the root and then load all forms of that usually new root into the lexicon. Then I repeat the process.

As I write this, the most common inbound word that is not held back has 107 occurrences across the text. In general, the roots are getting more difficult to deduce. Less common words tend to have more idiomatic English. This process is also getting easier in the sense that there are fewer words to compete against the word currently in question. So the work is shifting some from a couple weeks ago.

This suggests a possible general shift in lexicon loading strategy. It is possible to load words that are important for contextual reasons. We can theoretically decide to go completely fill in, say, all the words used in Mark.

Names, of course, also form an interesting group of words that could be entered together. Some names are already loaded. There are many other technical terms that could work this way too.

So I have been looking for places that might be interesting to fill in more completely. I was triggered in this by a Youtube video dealing with Mark 5:41.

So I have loaded the Lexicon with all the nearby words so we can have a Paleo word study against a Youtube video. This is the first of what should become many more word studies using the Paleo Bible app.

Healing Jarius's Daughter, Mark 5:41

The link here is to a Youtube video by professor Michael Wingert where he goes through the Syriac of Mark 5:41. Syriac as we know it now comes from around the year 100. It is claimed to mostly be a difference in letter shapes and vowel marks from the more common "street" Aramaic of Joshua's day around 100 years earlier.

This verse at Mark 5:41 is one of several verses internal to the Bible that argue the textual basis for the New Testament was not Greek but Aramaic.

In Greek there are translator notes in Mark 5:41 which do no exist in the Aramaic. The Greek is a transliteration of the Aramaic. The video linked above begins with the Greek phrase and the RSV level English of that verse. Then it turns to the Syriac of that same verse.

Note that I recently linked to a video clip from 2014 when Netanyahu told the Pope that Jesus spoke Hebrew. The Pope retorted that no, Jesus spoke Aramaic. This is one of the verses that supports the general Aramaic Primacy contention. There are a few others. Netanyahu was messed up because he does not know the New Testament.

This is an 8 minute video. It is the first in a very long series of similar videos recorded about 3 years ago. There are many other similar videos that I may return to in future weeks. This is just the start of what looks to be a very fun set of Paleo word studies.

Paleo For Mark 5:41

OK, so if you have the Paleo Bible open from the link above, you can navigate to that same verse. Mark 5:41.

Note that to help navigating through what is otherwise strange text, I have included the story headings that are found in the BRB. So you can scroll down following the story headings. You are looking for heading number 22, A dead Girl and a Sick Woman. This is the start of the story which runs from Mark 5:21-43. You are looking for verse 41.

Average Roots

Since this is the first time we are looking at a verse filled in mechanically using the lexicon, we can first notice that the meaning of verse 41 comes through in the English.

Remember my process, I am looking for the most common English for each word as surveyed across the text. I am also checking for integrity of the English against the meaning of the root.

As a made up example, if I found some Paleo root that comes to English as both "house" and "mansion" I would choose "house" if that was the common English.

I follow this pattern especially when this is the simplest form of the root. English does not always allow this pattern, but most of the time it does.

This process does not always work because English is irregular. Mark 5:41 is our first public test of this process. If you look at that verse, you can see this process is generally working. You can more or less make out the entire verse.

Gender

Note that the "Fe" ending on many of the words in this verse is triggering "he" in the English. This suffix is regular in Paleo but irregular in English. English adjusts the gender while Paleo does not. Because the Lexicon is not using adjacent words to pick off exact English gender, we see male gender in the current English.

See Mark 5:41~2b and Mark 5:41~5 where the Fe is triggering the common male gender in English. Turns out this is a much more rare case, female gender would be better here because the verse deals with a young girl.

Most of the manuscript is men fighting each other. So male gender is a better default. I might intentionally drop gender on these common words. Word 2b would become "hand-" and word 5 would become "to-."

Transliteration

Now look at Mark 5:41~6-7. These 2 words are the focus of the video linked above. These last 2 words are the words that get transliterated into Greek and then on to English via that manuscript chain down through history.

First point is that there is a sound system reversal from the Paleo letters. The "The" and the "Ta" letters are trading sounds. This is so even in the Syriac pronunciation used in the video. This is just curious. We will need to review sounds. The Greek appears to be translated from Syriac by ancient sound.

The entire sound system of the world is mixed up by the Tower of Babel. These are called "Shibboleths" where the S and Sh sounds were messed up even during the time of the book of Judges. We have been through a specific letter-to-sound recovery process. That should still remain valid.

Missing Greek Letters

Sound system problems show up with the final word, Mark 5:41~7. The first letter is a "Qu." So the Q in English. Greek does not have this letter, and the ancient translators to Greek had to pick a different letter. C and K are the 2 choices as the video explains. Both letters were used in ancient times by Greek translators to substitute for "Qu." This same letter sits in the middle of Paleo spelling for Jacob, which is curious.

English: Stand

That word, "Arise" in most English translations is coming from a very common Paleo root word, "Qu-Ve-Mo." "Stand" is the most common English, so that is what I have loaded into the Lexicon. "Arise" would make little sense in most places where this word is found. Stand works nearly everywhere.

Note there is a tone issue here. In the Greek traditions we read this as some sort of performance, with special vocabulary. Modern pastors play similar games when they quote Hebrew or Greek in order to perform for an audience.

The tone in the original is just "stand" or "get up." The video linked above also drops the tone to this level of speech. It is not a performance. Joshua just tells the girl to get up.

This choice of words presumably means she is healed already, and just needs encouragement to try and act on that healing. This is missed in the texts based on Greek.

Added Vowels

The spelling of that last word is also curious. The "Qu-Mo" root for the word "stand" has several different inserted vowels. In this case a "Ve" has been inserted. There is no difference in meaning between the simple 2 letter root and the "Qu-Ve-Mo" as found here.

This is an audit issue. It is a classic example of added vowels from our first class in Hebrew. The meaning is found by dropping the vowels and looking at the letters that remain "Qu-Mo."

The Qu is a brain with a spine. Thinking is one ideal, so use your brain. Using your spine is what shows up here. The Qu is used in words like tree, which also have spines, we call that the trunk. The "Mo" water, which among other things "flows" or "moves." Water is always moving. So the word "Qu-Mo" has the sense of moving or flowing the spine.

So the core idea of the word, in English, is to "move your spine." The second idea is to use your brain. Joshua may have chosen this word because he wants the girl to use her brain and thus also think about standing while standing.

For Ciphers?

It struck me in thinking about this video that we might have a situation where vowels have been added in to correct cipher related issues later in the process. This is a case I have never considered before. This might be a general issue with the whole problem of added vowels.

A 3 letter root with an otherwise silent added vowel will cipher differently than a 2 letter root without the vowel. So there might be an inspired use for these things we have not considered previously.

More on this as we get into the audit phase. "Qu-Mo" is all that is needed in the basic root as used here. In other parts of the text, the 2 letter form is all that is used to mean "stand." The Lexicon is designed to treat these as variant spellings of a core 2 letter root.

Once the Lexicon gets its own user interface, "Qu-Mo" will be seen as the ultimate root, and "Qu-Ve-Mo" as found at Mark 5:41~7 is just a variant.

Yo Suffix

The "Qu-Ve-Mo" root in Mark 5:41~7 has a "Yo" as a suffix. This letter also presents a strange set of problems.

Yo endings normally translate into English as either plural or possessive. Similar to "s" in English.

Generally, across the lexicon, a single Yo suffix is coming out into English as the possessive form of the root word. The word "house" with a Yo on the end will be "my house."

If that Yo is followed by yet another ending, then the Yo becomes plural. So "Yo-Fe" as an ending becomes "his houses" if the root was house.

I've now seen this hundreds of times and this is the general rule.

This Yo letter is ultimately a model of a hand. Hands can hold things, so possessive. Hands are at the ends of arms and have fingers, so plural endings. The 3d system works well for understanding this Yo suffix.

In this case the word "stand" does not need any suffix at all. It adds nothing. As a possessive ending, it would normally possess to the speaker. There is nothing plural going on here either.

A Fist?

If this does pass audit, perhaps the hand becomes a fist. In that case it would be functioning like an exclamation mark. So, stand! In that case arise might be a better English word choice.

In any case, you can see I have set the lexicon to supply "stand-" as the English for this specific variation in suffix. Stand is the root. The reader needs to decide what the specific form might mean in English.

In this case, there is no obvious other English for this form of this root.

Not Pronounced

In the video above, a point is made about this last letter. It is NOT pronounced in Syriac. As shown in the video, in printed copies of the manuscript, there is an underscore below this letter in order to tell the reader not to pronounce this letter.

So the reader is being shown to skip what might not actually belong in the inspired text. The ancient scribes saw the same problem I am seeing when dealing with this word in the lexicon. There is no meaning for this letter.

As a first example, this is looking like the lexicon is loading enough English to generally know what is going on. This is not perfect, of course, but it is encouraging that we have enough filled in so we can reason about various stories.

Young Girl

If you back up to Mark 5:41~6, you find the word for "young girl." This word is more complex. I loaded it early, and have learned a little about the grammar.

The "Wa" suffix at the end is normally "the." English does not normally need this specificity, but we find it in Paleo.

Ahead of that letter is a trailing "Ta." As a suffix this letter can have various meanings. For roots which reference a person this can mean the root is modified to express a feminine subject. So this suffix means the root is referencing a girl.

The "Yo" suffix ahead of that Ta may also be adding the detail, "small." The Yo is a hand. Imagine taking 2 fingers of a hand and pulling them towards each other. We use a similar ending in English with words like "puppy" where trailing Yo has the meaning small. So Yo implies the root is something you can perhaps hold in your hand. Stand alone the Yo usually means "my." Think something in hand.

The remaining fundamental root is "The-Lu." This is usually translated as something like youth. The Paleo word definition would be "wheel/time [of the] shepherd." So someone who is in the time of life that still needs shepherding, so adult supervision.

Watch Dates

We still remain in a quiet week. Peeking ahead, the next interesting prophetic date is 2026-07-13. We will return to that date next week.

Shop Work

Shop work this week has been spent loading data into the lexicon and fixing up the issues I addressed above in the app itself.

The lexicon now has 316 root word entries. There are 8816 specific forms of inbound words currently loaded. There remains 42,098 forms that are not in the lexicon. Still much work to do. But, it is getting fun. Words are getting interesting.

The lexicon can explain 362,250 words of the inbound manuscript. There remains 173,770 still to explain. This is now better than 2/3rds of the inbound text.

Tucker and Apffel

In last week's blog I mentioned how every individual Christian who attends Church can now be tracked by big money interests. One tool for this is geofencing, which is the tracking of cell phones ultimately using gps. This generated some feedback because it is becoming unsafe to be a Christian in the USA.

The link I was given was on a different social media platform, but to the same content as I have linked here. This is a link to Tucker's channel on Youtube where Tucker meets with Nathan Apffel.

Nathan is known as the man currently reporting on the business aspects of big churches. American tax law is setup to try and protect churches from taxation. But this gets seriously abused when it comes to certain mega churches, as the video explains.

There is an interesting passage in Matthew 17:24-27 that deals with taxation. Kings of the world exempt from tax those whom they consider family. So tax exempt churches are ultimately family of the king. So ultimately Hivite. Joshua explains to pay tax so as to show that his people are not of this world and do not work for the Hivite.

Towards the end of the talk, Tucker and Apffel discuss how it might be better if much of the more strange church functions were taxed. This would be in agreement with that passage in Matthew. For Tucker and Apffel this is an issue with side businesses. Perhaps it is an issue with all church buildings.

We don't yet know the ideal venue for full sets of the 3d exhibits. I currently suspect that private homes would generally be better than public meeting houses. Owners of houses are better natural protectors of potentially valuable exhibits. Ryan and I have attended church in very large private houses. There is much more respect for the place when you know someone owns it. You know you are there only by someone's good graces. The public has no natural right of access which also grants ushers more natural power over trouble makers.

Early in this longer talk, Apffel brings up the issue of geofencing. This is where it connects to last week's blog. Israel wants to track Christians in order to get yet more money out of them in order to support government functions in Israel. The setup they are using is to monitor cell phones that visit certain Israel friendly mega churches. From that point on, those phones are now thought to be owned by people from whom Israel can extract yet more financial support.

Perhaps the best way to stop this up front is to only attend church when your own phone is in a Faraday Bag. Amazon sells them, 2 for $15 this week, military grade. A little more money will get you better reviews. These bags are not that expensive.

We are in the season in history informed by the last 3 days of Passion Week when the Jews are running around in the streets, with their radio trackers turned on. The few disciples of the time are hiding out in upper rooms.

This will ultimately be fixed geopolitically. Just wait.

Headline Review

The following caught my attention this week.

Starmer Wants NATO?

This is a follow up to a recent news link dealing with UK PM Starmer. His last act in office was supplying weapons for a large strike on Russia. That appeared to be his very last act as the UK PM. Now he looks to want to run NATO itself. So bombing Russia was a job interview? London is a strange place.

Secret Elite

Every so often we get apparent leaks of lists of people involved in bringing the world to war. Hivite would be my Biblical term for these men and women. The link here has another list of 200 or so. This includes some infamous political types from Texas. No wonder they babel in public.

Restore Unity in Libya

So while the Iranians wait for war to start again, the USA is now out to "restore unity" in Libya. So when bombs don't work, the next thing to do is to trick this into happening. The real problem is parts of Libya can still bomb Israel. Why not just say so?

Funerals In Iran

The link here has the schedule of funeral events in Iran. These start July 4, 2026, and run through July 9. Will the trigger happy leave these people alone? Or not? Hard to say. Iran will be more likely to defend itself after the 9th. This gets us closer to the next prophetic date on July 13.

Red Skies Venezuela

The earthquake in Venezuela has left quite a mess. Some reports are saying 800 towers fell. The link here is to a photo of a strange red sky that has lingered in the earthquake zone. The coloring is thought to be created from dust kicked up.

There are references to red skies in Matthew 16:2-3. That story sets up a principle. Signs in the skies, like red skies, are not the way Joshua will be running signs. Instead he cites Jonah. Of course, not the fish story. What did Jonah build and show off? I wonder.

New US Embassy, Jerusalem

The link here is to a post on Telegram with a photo of the signing of a new agreement for the USA to build a new embassy in Jerusalem.

Opening of the current building was on a prophetic date. We would expect the opening of this new building to be similarly prophetic. Still a few years out, as they need to build the place. This is a spot to watch.

Military Summary 2026-07-02

The link here is to a recent Military Summary video. This channel carefully tracks the war in Ukraine. This is just for reference. The main event was a major set of attacks on weapons related targets in and near Kiev. Russia is also taking out gas stations across much of Ukraine. The Russian government appears to have released their military to finish the job in Ukraine. Will Starmer come to the rescue?

More Later,

Phil

Paleo Bible

Phil Stone — Fri, 26 Jun 2026 21:16:48 GMT

This blog introduces the new Paleo Bible app. Before that, some updates to the Story Grid. Then a discussion on Revelation 18, which showed up in last week's Sabbath Reads and informs an important headline. Finally, a headline review.

Story Grid

Ryan continues to work on figuring out the set of stories that make up the inspired subset of the Bible. The Story Grid app is where most of this work is happening. This week he traded rows for the Gospels of Luke and John.

This was driven mostly because this new placement causes the individual stories within those Gospels to follow patterns related to the row letter. Perhaps the easiest place to understand the letters is by thinking about the Qu Map. Let me start with John.

John

The Gospel of John is now on the Sa letter. So think about the Sa location on the Qu Map.

The Sa is a model of a post. This picks up the common meanings of the word post in English. So a post in a building or a fence post, or parcel post or outpost. On the Qu Map you can find San Antonio as the mapped US city. This city grew around the Alamo, what was an outpost. You can also find the iconic tower of the Americas, so a huge post. Historically there was also a major warehouse district, so parcel post. Jungle Cruise, at Disneyland, matches River Walk in San Antonio and picks up another theme, which is running from those who might seek your life. A row of posts is some sort of weak protection like a fence.

So going back to the Gospel of John we see themes similar to these across that Gospel. First point to notice is how nearly every story takes place at an identified location. Much of it takes place in secret, or at least to protect those involved. Nicodemus at night is done to protect Nicodemus from those who would want to kill him. Feeding the 5000 is an example of the supply sense of an outpost.

John explains that Joshua wanted to go to the Feast of Tabernacles but he needed to be careful because the Jews wanted to kill him. Think Alamo, or Jungle Cruise.

Ultimately the row ends with the Seaside Encounter. Here there is a miraculous catch of fish. This is a massive supply, again another example tied to the Sa letter and its related themes. In this last story, Peter is going to be given responsibility for what was Joshua's house. Peter is being "posted" there. He is being given the "outpost."

Note there is a curious number of fish, 153. This is the triangular number for 17, the price Jeremiah paid for land. This strange number is suggesting Peter is somehow following in the pattern of Jeremiah, but presumably with a much larger responsibility.

Luke

The Gospel of Luke is now on the Ze row of the Story Grid.

The Ze letter is a belt buckle. Similar to a lock. A buckle, of course, connects the 2 ends of a belt, so making a connection is a theme for this letter. Another theme of the letter is protecting places where not everyone can go. So secrecy, privacy and modesty are similarly related themes.

On the Qu Map, the 2 places that are most helpful for understanding this letter are Tom Sawyer's Island at Disneyland and Boise in the USA.

Tom Sawyer's island is locked away by raft from the rest of the park. The raft itself is like a buckle connecting to the island. That island is not always open because the island is used for fireworks shows after dark. The island itself is a treasure hunt, guests are looking for buried treasure, ultimately found at the back of the island.

In the USA this is Boise, which is the largest city in Treasure Valley. This is the name for the snake river valley in that part of the state. Again, you can see the theme of trying to unlock buried treasure.

This is also the general location for Idaho National Laboratories, located east of Boise. This is currently used for research and development of nuclear reactors. It is a likely place for the eventual burial of nuclear waste. This is a place where the public cannot go, at least not without permission. Of course the public is kept out for very good reasons. Those reactors and the radio active waste are behind a lock, or buckle.

So turning to Luke itself. Luke's Gospel begins with Gabriel's appearances to Zechariah and Miriam. These are connections being made like the 2 ends of a belt. These connections are being made in private settings. In Zechariah's case inside the Temple while there is a crowd outside. In Miriam's case she heads off to visit Elizabeth, but also to remain in private.

You can scan along the row and most stories involve some sort of important interpersonal connection, often in private, sometimes even at night. The calling of the disciples happens after Joshua is alone on a mountain for a night.

Even some small details involve this letter. The disciples are set to "unbuckle" the colt so Joshua can ride it for the triumphal entry. The very last story in Luke involves the upper room, a place of privacy, and then how Joshua is taken up from them. He was unbuckled from them.

Ryan is now working on story placement across these rows. He has put more attention across the stories of John this week. Those stories seem to be falling into place.

Paleo Bible

Several weeks ago I was suggesting here in the blog that the Paleo Bible app was a "couple weeks away." This past week Ryan asked me for some sort of Paleo search function for the Paleo Bible so he can find Paleo keywords in his ongoing story grid and BRB work.

It is hard to add a feature to an app that does not yet exist. So the first step was to get the app running with live interlinear data. Some of this is running a on shim that will be rewritten later, but at least the general interlinear function is now running.

Please consider this a preview. There is much more work still to come.

You can follow the link above to see this new app. The permanent link is off the front of Paleo.In. It is a web app like all of our other Bibles. So it can be installed on devices and run offline just like everything else.

The Paleo Bible does not yet have search, at least not this week. Search is very, very hard. Because letter level markup is coming, the manuscript does not ultimately have whole words like found in English. So search must be done very differently than we do in our current Bible apps. The words need to be indexed ahead, before they get letter level markup. Search will then work against indexes, not against the text itself. This is on my list of features still to add.

Interlinear Principles

I am currently attempting to identify all of the paleo root words found in the running text of the Bible. I have never had a strategy for this task in the past that actually worked. I was always in a hurry, so I was not giving time to understanding the real problems.

Words come to us as some sort of root that is surrounded by both a prefix and some sort of suffix. These are single strings of letters that must be broken apart. The prefix becomes stand alone words, usually 1 letter words. The suffix provides for various grammatical forms of the root itself.

Of course we are using an Aramaic manuscript base for this, and we have English interlinear available for most of the Bible. For some of the Apocryphal books we do not have an Aramaic interlinear, though you can see by playing with the Paleo Bible app that the Apocryphal books are filling in pretty well.

Troubled English

In this Lexicon work I am finding trouble with how the English is following the Aramaic. This is because 1) English is irregular in ways the Paleo is not. 2) Translators control tone so their readers can see words they expect. 3) The text has been edited, and editors and/or their translators used a different dialect from the base language. 4) Editors were dealing with topics for which there is no inspired vocabulary, so they were reusing terms.

I don't yet know what is inspired. So I don't yet have confidence in what English might be best for any given root. So I am attempting to give a "best guess" at what might be a trustworthy English word that matches each given root.

The lexicon is now an editable and maintainable resource, so it can be adjusted as the recovery work progresses. The English can be tuned as needed. This is an iterative process, and this is only the first iteration.

English Marks

In the Paleo Bible, on the English side of the interlinear, you will see a few important marks. These are indicating future work items that should get addressed as this work progresses. Let me call out the marks that matter.

? A question mark is used to indicate the Lexicon does not yet have any entry to explain the word in question. I am working to load all words into the lexicon. When that goal is reached, these question marks will go away.

?? A double question mark indicates internal problems in the lexicon itself. Typically, the inbound word is parsed, but English is missing. I will address these cases here soon.

- and -- so dash and double dash, are found at the ENDS of many English words. These dashes mark that I had trouble selecting the English word that should match the Paleo word in question. Note that there are a few hyphenated words in the lexicon so dashes mid word are OK.

A single dash marks a mild warning that there might be trouble. There is a suffix related analysis that waits for the entire Lexicon to be loaded. Single dash indicates this word has trouble which is most likely coming from the Paleo suffix. It should NOT be used when trying to understand the suffix. There may be better English.

A trailing double dash marks more serious trouble. This can be for a variety of reasons. Nothing about the English should be trusted. This is usually because there was no consensus in the available English I was testing when I was looking up the word. In this case I generally try and hint at the common English root, if that is even possible. The English word to the left of the double dash is thus an educated, but wild, guess. I treat the double dash as the "wild guess" marker.

Merging Roots

In many cases I find the English translation for a common word will use English synonyms. I am attempting to pick a single English root whenever this makes sense. A recent example was the Paleo word for "little." This can be applied to people, so it can become "young" or "little ones" in English. So I intentionally pick "little ones" as this triggers learning the root as "little."

This makes the English a bit strange. But this encourages learning the root word involved. When looking at sentences in the Paleo Bible built this way, these hints are usually enough to follow along with the meaning of the sentence, even if it is a little strange.

Conceptual Differences

Another word I ran into here recently was the paleo for "dwelling."

Nearly everyone reading this blog is going to picture a house as the core idea for this word. This is a mistake because of our modern world.

The underlying Paleo root word seems to indicate the geographic place where you live, not the structure.

So "camp" and "campsite" are closer in real meaning. Armies gather in these places. We just don't think of a dwelling as the place because we mostly live in fixed houses.

So in my attempt to pick good roots, I sometimes have picked roots that are unconventional because they pick a better concept space. Reading the text accurately requires some level of understanding the way of life of the people involved. I see this problem better now than I have before.

Crazy Differences

Another mind-bending example word from this week's set of words becomes in English "Holy" and "Holiness." This should not have been trouble. But, the Paleo root word here has a full set of the normal suffixes. None of those specific forms, beside holiness, ever gets translated into English at all.

Because English around the word Holy never needs to use grammar, I suspect our conceptual understanding of this word is badly messed up. I just loaded it as "holy--" for all grammatical forms in order to return to it later.

Irregular Du, Irregular Fe

The Du prefix in Paleo is irregular in English. I have loaded it as "of" for all uses in the interlinear. In English this changes based on the subject. "Who" is more accurate for people. "That" is used for certain types of things.

There is a "Fe" suffix in Paleo that I am loading into English as "he" or "his." This is the most common English. But, English for this is irregular. English adjusts the gender, so "Fe" might be "she/her/hers" or it might be "it/its." You will see this in the Paleo Bible interlinear, it is easy enough to see what is going on.

The Paleo I have looked at so far does appear to have a way to indicate some uses of feminine gender. A "Ta-Fe" ending is sometimes used for this purpose. But this is not consistent and may be a dialect issue springing from an editor.

Future Steps

Until we get through audit, we cannot tell what uses of Paleo words are actually inspired uses. So differences in word meaning cannot be accurately worked out until after we have first worked through audit issues. Words which do not pass audit, or which are located in sentences which do not pass audit, should not be used to inform common meaning.

So until that point, current English is a place holder. The lexicon will get adjusted to better English once we get a grip on the problem of inspiration.

It looks possible to add a hinting system into the lexicon to handle English irregularity. I have experimented with what those hints would look like. I am happy that such hinting is possible, but that work waits until later. Fine tuning English is not a task until after audit work is done.

Let me switch gears to the Revelation 18 story from this past weekend's Sabbath Read. That chapter hangs on the word Babel. A few weeks ago I showed how to define modern Babel. That definition was not complete. Let me review that term.

Babel In Palestine

When I originally worked through the Bible Time material I saw the 1948 formation of modern Israel as the "Jewish Return to Modern Israel."

I used that expression for a long time. It is based on the "7 times" prophetic offset from when the Babylonians invaded Jerusalem in Jeremiah's day. So this crude English construction was not so bad at explaining the headline.

Though I have not yet built the Crown Exhibit, I am starting to see history a little different. "If you cannot remember history, you are condemned to repeat it" is a different view, which is at least a working memory peg. This view is what we use whenever we rerun timelines. We expect the textual story to inform a headline in some way.

So instead of thinking of the Jews as returning to Israel, we should see the invasion by Nebuchadnezzar's Babylon as happening again in 1948. History was simply repeating at the 7 times offset.

In this view, we can expect that in Israel we will eventually see a Persian king involved in Temple rebuilding. This follows the "history repeating" view and has no explanation in the Jewish return view.

What is missing in this view is who or what was the Babel who invaded Palestine in 1948. In the language sense, of course, the heirs to the editors were involved in that invasion. But geopolitically, who is the powerful Babel that forced that 1948 invasion of Palestine?

So this past week's Sabbath Read included parts of Revelation 18. This is an end-times story about the fall of prophetic Babel. This chapter basically identifies the agents who are behind Israel, including all the way to this day. This chapter fills in our understanding of Israel. It also informs another obscure but very important headline this past week.

Let me start by reviewing Revelation 18, and what it says is going to happen. Then we will look at this week's headline.

The Fall of Babel

The link here is to Revelation 18 in the BRB. This is the core story that was at the bottom of last weekend's Sabbath Reads.

With all stories like this, there is the problem of identifying the modern location where it will take place. Conceptually, we have available to us all the information in the Lost Tribes study. We also have available the timeline. We also have available all generally known facts about the world.

Stories like this tend to pick off a cluster of identifying marks in order that at least some of them can be used by readers to match the fulfillment venue. If that chapter is new to you, or you are trying to learn how to do this yourself, I suggest reading the chapter and try and identify the modern location on your own, before you read my answer here.

In this particular story, there are certain identifiers that narrow down the problem and eventually we can identify London as prophetic Babel. Let me work through the main details.

The first main clue is the references to the "double portion." See Revelation 18:6. This is a tribal identity that applies only to Joseph. The seal date for this was in 1941 with the lend lease treaty that established funding for World War II. That date, of course, was between the US and the UK, which are the 2 expressions of Joseph's double portion. This is a point where BibleTribes.org goes into the details.

This narrows the search down to the English speaking peoples. But, how do we get to London?

In Revelation 18:10, Babel is called a "great city." So we would be looking for a great city somewhere in the English speaking world. In the UK the candidate is London. In the US that would be New York or perhaps one of the other large US cites. In any case, the judgment being described is now applying to a city somewhere in the English speaking world.

In Revelation 18:16 we see yet more description of the city itself. It is wrapped in basically "red white and blue" and inside is "gold, precious stones and pearls."

The cloth wrapping is a pointer at the flag. So the USA, the UK and for that matter Russia, all have this color of flag. So this is not particularly unique. But it is again limiting us to Joseph, but with a specific flag.

That same story also talks about an internal identifier of gold, precious stones and pearls. These are similar to what Solomon was collecting when he built his temple at Jerusalem.

These particular items are marking the reserve assets of international bankers and central bankers. Gold is the most common. In 1971 Nixon, at the direction of central bankers, took the US Dollar off the gold standard. Gold, of course, is referenced in Revelation 18. No gold means no ability to repay debt. Oil was established instead, and oil only pays interest. Once Iran wins, then there is no means to even repay interest. The Iran war is important.

Note that I am pointing at the US Dollar as the effective currency for London. Why? Central bankers use the currency of the largest military. After World War II, that shifted from the Pound to the Dollar. Bankers ultimately don't care what currency they are using.

So now we still need to narrow this down to either London or New York. The Federal Reserve has a building on the mall in Washington DC, but the main operation is in New York to be near the headquarters of the other main banks of the USA.

London, though, is a better match to the Revelation 18 story. The "City of London" is that square mile in the center of the metro area with its own legal rules. In particular, this is where Jewish bankers have mostly controlled the money of the world since about 1600 when usury was legalized in Britain.

By Revelation 18:17 we reach a passage dealing with boat masters and sailors. This is where the story narrows down to one of the main remaining industries of London.

If you have been tracking news for the last couple years you've probably heard how the west has regularly intercepted ships of the "Russian Shadow Fleet." France did this again this past week. This is a form of piracy on the part of the Zionist west.

Calling these ships part of a "shadow fleet" is a great example of Zionist narrative formation. Technically, a "shadow fleet" identification means the ship is NOT INSURED by any insurance firm based in London.

The problem with the war around the Strait of Hormuz is the insurance that ships need to travel at all. That essentially always comes from London. It is how London still takes a cut of every cargo shipped pretty much anywhere in the world. They close that strait at will simply by cutting off insurance. This is the industry that Revelation is using to mark London. This is how Zionists can open and close Hormuz, even without sending any naval ships to the region.

Revelation 18:11-13 gives a list of 24 different types of cargo that are associated with Babel. Again, London insures the transport of all of these things. In history they protected these items with their own naval fleet. Now through insuring, so taxing, all of these cargoes move around in the world at London's permission.

More Details

Once the city identification is made it is possible to scan it again looking for more details. Some of this is tied to the general history of London.

The 2 main historical points that matter is how London became the effective western capital of the Roman empire after the collapse of that empire. I was taught in school that Constantinople became the eastern capital while the western capital remained at the city of Rome.

I have read alternative history that suggests the culture of the western Roman empire remained better preserved at London because it was isolated on an island. London was across the English channel like Constantinople was across the Bosporus. Roman historical remains dot the landscape of southern England to this day. Think of the Roman Baths at Bathe. Think of Winchester's roman road design. Roman territory actually stretched up to Hadrian's wall.

Thinking of the Roman empire as splitting east and west suggests one capital went east and another capital went west. London is the western choice as the heir to the Rome where Paul ended his recorded travels.

Moscow, by the way, would be the modern heir to the eastern Roman capital. That matters to this week's headline.

Benjamin

Joseph was also brother to Benjamin. Joseph and Benjamin interact in strange ways when Joseph reveals himself to his brothers.

Benjamin was later mostly absorbed into the Jebusites. Reading that story in the Bible we can see links back to Sodom. We now know this linkage is expressed with terms like the "Epstein class." Modern politicians are chosen because they are fornicators of the worst sort.

Banking is another important historical national business of Benjamin. The Paleo root word for "Pharaoh" is the paleo term for "pay." Pharaoh can be known as a "pay master" or similar. The Pharisees of the New Testament are just "little pay masters." We know them as money lenders and bankers.

There are various banking centers in Europe. The Bank of International Settlements in Switzerland, for example. But London appears to be the operative capital for banking in the western world. It was London money and political power that drove the creation of modern Israel. There is a very well documented history of how London was ultimately the agent behind the formation of modern Israel. There are many, but let me review the easiest to remember.

Balfour Declaration

The link here is to the Wikipedia article with details of the Balfour Declaration from 1917 when Britain announced their intention to set up a Jewish state in Palestine.

Flipping this to prophetic vocabulary, this is prophetic Babel from Revelation 18 announcing their intent to invade Palestine as they finally did in 1948.

Modern Israel, of course, can also be called out as prophetic Babylon. They are the local agents from a bigger empire. This is all linking us back to calling London out as the capital Babel. This is in agreement with the Revelation 18 passage calling out London as Babel.

We can see more ancient manuscript hints at this in Revelation 18:3, where fornication is called out as an aspect of this end-times prophetic Babel. There was a cell phone video floating around a few months back of an apparently naked young man fleeing out an upper window of Buckingham palace. Presumably fleeing for his life. The Epstein class is going to be running everywhere.

Speed and Permanency

Near the bottom of Revelation 18 there are some details about the eventual destruction of this same prophetic Babel.

First point is that it happens fast. 1 hour is the time given in Revelation 18:19. In terms of ancient war, even World War II grade war, a 1 hour destruction of anything is nearly impossible.

Revelation 18:21 describes the weapon used as a "mighty stone." The most dense stones on earth used as weapons of war are nuclear. This is why depleted uranium bullets are used. They are more dense than lead. One large nuclear core will take out not just London, but southern England as well.

Professor Karganoff has been on western podcasts trying to warn the west that the western actions are causing Russia to contemplate the use of nukes in order to try and stop this war. So far, the new discussion is the use of small nukes as an attempt to get the west to back down.

Revelation 18 is telling us that Russia will not be successful in getting the west to stop attacking Russia.

Once Russia has enough and decides to nuke London, they may choose one of their larger weapons. Something that may take out not just London, but all all of the southern British Isles.

A large nuclear strike may leave a crater so deep that London is filled in by the sea, never to rise again. Mighty is the Lord God who judges her.

Current Headlines

This week we passed the 85th anniversary of the start of World War II in Russia. They call it the Great Patriotic War, because they were defending themselves from European, primarily Nazi, invasion. Russia has been fighting off Babylonian invasion since at least Napoleon. This is a long term goal. The bankers want to conquer the world. In any case, we are now 85 years out from the last time this was tried by war.

Russia is commemorating this event in various ways.

27 Million Trees

The link here is to a TASS post on Telegram with details of one of those commemorative projects. In this case the planting of 27,000,000 trees. 1 tree is being planted for each Russian death in that war.

But, the day after the Russian day of remembrance, we saw something else happen, also commemorating the 85th anniversary of the start of World War II. Here is the first link I saw in my news stream of what happened the next day.

Britain Attacks Russia

Leaked German Audio

This was the first, formal, overt attack on modern Russia by Britain. The attack was intentionally timed to mark the 85th anniversary of the start of World War II. It was ordered by British PM Starmer as his last act before leaving office. Starmer appeared to have delayed his resignation in order to be able to sign off on this attack, and leave his successor free from guilt. Of course they all work for someone else, perhaps the king, perhaps the king's banker.

Starmer was crying when he gave his farewell speech in front of 10 Downing. Likely those tears were because he knows he just caused the eventual deaths of himself and everyone else he has ever known. He just triggered the eventual retaliation by Russia as recorded in Revelation 18.

The Zionists have set a trap for Putin. If he does not respond he is seen as weak. If he does respond he gets blamed by western media as having started World World III. The Germans leaked some audio that points the finger at Starmer. Someone in Germany knows they also are dead because of this action.

By the end of the week Putin had brushed off the attack, and delegated response to the Russian military. Russia is stepping up operations against Ukraine. The Russia strategy is apparently to conquer Ukraine itself so future attacks must be launched from NATO territory. This would give Putin, or his successor, the moral authority Russia needs to deal with Babel directly. Russia is a moral people unlike anything we know living under Zionist rule.

I should note, that Russia does not get out of this mess without trouble too. We will return to Russia as needed in a future blog.

What I have sketched out here is how to link together all the war fronts going on around most of the world. The capital where this originates is called out in Revelation 18. That capital is fighting wars of conquest all over the edges of the empire. Most of Central and South America has now fallen to the empire. Russia, Iran and China are the 3 big powers not yet subdued. These 3 don't appear to fall before the events of Revelation 18. After the events of Revelation 18, the world as we know it is different. Likely timing for the main events in that chapter starts in early 2029, but can stretch out to 2038. Western leaders are publicly calling out 2030.

Watch Dates

We are continuing to watch 2026-07-13 as the next prophetic date in the current series. We will return to this date as we get closer.

Note that this past weekend there were some meetings held in Lake Lucerne area of Switzerland between the USA, Iran, Pakistan and Qatar. These meetings are attempting to work out a possible agreement beyond the MoU that is currently governing the cease fire with Iran.

These talks involved several points where the Iranians walked out because of Tweets issued by Trump. Is Trump an idiot? Or does he just play one on TV? Most likely he is trapped by Zionists telling him what to say.

There is some oil flowing through Hormuz. There is not enough to prevent tank bottom issues in the USA in the next few weeks. This is expected to be different in different regions of the USA. Gasoline is expected to be easier to find than other fuels like diesel and jet fuel. The west coast is expecting more trouble than the gulf region.

Shop Work

I continue to be focused on getting words into the lexicon. Here are the current stats as of this week.

The lexicon currently has 268 roots. This is going to be double counting certain roots which have mid-word inserted vowels. This is a curious problem for the audit to look at. An example is Qu-Mo. This is the root for "stand" or "rise" and it has 3 other forms with mid word vowels. Those vowels never add anything to English and I would expect the audit to remove them. We'll see.

There are 7149 different inbound word entries spread out under those roots. There are 43,764 still to add to the lexicon.

In terms of manuscript coverage, the lexicon can explain 340,913 inbound words. There are 195,107 words which the lexicon cannot yet explain. This is also a strange count because the lexicon often creates stand alone words in the final manuscript. So final word count is much higher than just adding these numbers together.

In prepping the Paleo Bible for release late this week I did see some situations where words are in the lexicon, but not creating English interlinear entries as expected. This is very raw new code. It will take time to settle down. There are still many bugs.

Headline Review

The following caught my attention this week. This has been mostly a slow news week without much of high interest.

Threats At Belarus

When Trump signed the MoU with Iran in Versailles, there was a group of European leaders who were also at the table. We don't know for sure what was really discussed, but escalation of the war seems to have been the main topic. Starmer's attack came after. So too did Zelensky start escalating against Belarus. The link here is to a post on Telegram with at least some details of that threat.

Again, the west wants to tell its public that the west was attacked. Western leaders want a moral imperative which they do not have. These attacks are trying to create that imperative. So far, Putin has played this game very well. He has a bunch of skilled advisors. The west is just gangsters.

Geofencing American Churches

The link here is to a long post on X detailing how Zionists are geofencing American Christian churches. This is a process of using cell phone tracking data to see who goes to church. As Netanyahu recently boasted, everyone has a piece of Israel in their phones. He should have added, and tracking where you go to church.

Ultimately someone wants to know everyone who regularly goes to church. What evil do they have planned? Debanking? Exploding phones? Flash mobs?

This post also details 1,700 pastors flown to Israel. By this they become Babylonian? Maybe a trip to London would work too. Unbelievable mess we live in. High tech was supposed to make life better. Instead it makes life very dangerous.

Red Heifer

More red heifer stuff. This link suggests Israel now has a domestically bread red heifer, not some Texan import. This makes it more pure. The timeline suggests Persia will issue the authorization to rebuild the temple. I doubt Persia needs such a heifer.

Ford and GM for Weapons

The link here suggests Trump has convinced Ford and GM to build weapons instead of cars, converting factories to build bombs for use against... Russia.

The strange problem here is these companies are no longer that good at making cars. So now they are going to be making missiles? Maybe Ford will open service centers at missile silos? That might be one way to prevent Word War III. (I'm sorry, this is all just so funny. Technically, I am getting jaded, and have fallen into using gallows humor.)

Is Trump an idiot? Or does he just play one on TV?

These already fragile companies now need to be boycotted for participating in genocide. They are on the wrong side of history. One possible answer is for their management to take as much time as possible to produce missiles. Maybe they will naturally take the same time they took to produce interesting EVs?

Running the clock is an interesting strategy for these companies that already regularly run the clock. Stall for 12 years you guys, shouldn't be hard.

Musk risks the same boycott related trouble with Starlink. Perhaps Trump is blackmailing everybody. Musk's problem is different. His companies are talented enough that he cannot use stalling as an excuse.

Venezuela Quakes

The link here is to a Lord Bebo post on Telegram with a video clip reminder that we had a double set of M7+ quakes in Venezuela. This is so large that it will take a few weeks before we know the death toll. Several other videos follow this one in that channel. Much widespread destruction including collapses of various modern towers.

Trump has been stripping Venezuela of resources to fund the empire. This quake should draw resources back to that country in order to support local rebuilding. In any case, not good.

More Later,

Phil

Tone

Phil Stone — Fri, 19 Jun 2026 21:47:58 GMT

This blog deals with ongoing lexicon loading work, including some thoughts on learning difficulty. Before that, more updates to the Qu Map and BRB. Finally, a headline review.

Qu Map

The link here is to the front of the Qu Map app. Ryan has again been busy with this app. He has been working on app wide notes for the various versions of the Qu Map.

This week he added a composite map. You can reach it at the bottom of the pull down menu at the top of the app. This page allows study of how the various maps in the app compare to each other. This ranges across various topics, from the elders to especially main geographic locations in the USA. Very interesting to see the summary.

We had a long discussion about city pairs, especially for the USA map. There are such pairs all over the map following especially the River Pairing system for the alphabet.

Our problem is how to do justice to those pairs since they are best explained by someone who has robust knowledge of localized American history. For now, we are going to leave city pair data out of that app.

BRB

Ryan is generally working on the Story Grid. He is working across the various systems that inform story placement. One of those systems are the 70 books that contain the stories in the grid. There are 2 places in the text where enumerated lists of 70 names can be found. By matching list lengths we know these internal lists of 70 names are in some way related to the list of 70 books.

These 2 internal enumerated lists of 70 name are 1) the names given in the Table of Nations after the flood, and 2) The names of Jacob's heirs that went down to Egypt.

So this week's update to the BRB (and TT) has had attention put into these lists. The text as given by history disputes the number that went down to Egypt. That dispute can be shown to be an edit, 70 is the proper number. So the filter tags are now used for showing the tampering in Jacob's name list.

The formatting of these lists has been changed to make them easier to follow. The lists are now in an outline style format. There are also now list enumerations in order to easily map names from those lists into numbers working down those lists. Those enumeration numbers allow easier mapping across the lists of 70.

Presumably there is some meaningful linkage between the 70 books and these lists of 70 names. These names, in some fashion, are also likely names for years in a 70 year cycle. We also expect the 70 books to be the units used for cipher work. In any case, new mark up makes this easier to study.

For readers who may want to look more closely at this, the Nations name list is Genesis 10. The Jacob heir name list is in Genesis 46.

Lexicon Loading Progress

I am spending most of my time working on loading a Paleo lexicon. This is so interesting I am spending most of my waking hours loading the lexicon. Nearly every day I am learning something new.

I keep wanting to go faster and get this done quickly. Ryan keeps reminding me to take my time and learn as much as I can along the way. There have been several lessons this past week which are interesting enough to share. Let me take you through some interesting new insights that I learned this week.

Fun With Numbers

I was asked recently why Paleo doesn't just use digits. Most modern writing uses digits instead of long form written numbers. Most of the digits we use today with numbers can be shown to be devolved forms of the first letters of the Paleo alphabet. Since digits are fast and easy to read, why would the text not use that system?

There are 2 evident answers to this question. The first is that spelled out words are less likely to be mixed up during manuscript copying. Modern legal documents, like checks and contracts, still spell out numbers for this reason.

For a document written for the purpose of long term transmission this is a good feature. The second evident answer is that long form writing of numbers also allows numbers to play nicely with Paleo grammar, especially the Paleo prefixes and certain suffixes.

The less evident answer is that because the manuscript must survive audit and because it eventually goes through ciphers, the choice of how words are spelled is driven in part by the needs of proofs of inspiration. Long form writing for numbers is presumably better for those aspects of inspired text.

So this week I was able to load most of the words for numbers into the lexicon. As timelines numbers are another important project. This was a particularly fun set of words to get my head around.

It turns out that the system of writing numbers in English appears to be based on the system used in Paleo. So our current modern system of writing numbers has been in use since before Noah. Let me explain the principles.

There are paleo words for each number, one through nine. Then there are paleo words for ten, hundred and thousand.

With those 12 words alone, it is possible to express any number from 1 through 999,999. Pretty good coverage.

Paleo numbers get expressive power by using certain normal grammatical endings, same as English. In English, thirty is just a grammatical form of three.

Numbers in the tens, so teens, are just compound words with the base number's word combined with the word for ten. In this case, Paleo is more rigorous that English and does not misspell ten.

With these rules all numbers to ninety and nine are expressed like in English. The Paleo word for hundred kicks in at that point. To reach multiplies of a hundred the Paleo system just compounds the single digit words with hundred. So the teens does addition in the compounding, the 100s does multiplication.

There are some irregular forms, which look to be dialectic issues that the audit will need to sort through. In particular Ta, so a plus sign, is placed in the middle of a few of the compounded words.

Vocabulary words for numbers are an interesting example of the expressive efficiency that I am seeing across the lexicon. Very few root words are combined with suffixes, and occasionally compounded, in order to create a very expressive language system.

Stephen's Speech

We currently use digits in the BRB, which is nice for numeric studies. But consider Stephen's speech in Acts 7. The link here is to the specific verse 14 where he claims 75 went down to Egypt.

Given the list of 70 names as marked up this week, there appears to be a contradiction. Or, there has been manuscript tampering.

Once you know that the text writes numbers like on a check, the actual Paleo for 75 is going to be "seventy and five." The "and" being a prefix on the word for five.

With digits used in the BRB the likely Ananias edit cannot be easily seen. With written out words, the word "five" must have been added by Ananias in order to hide the use of 70 which has meaning Ananias would want to cover up. So the word five should sit under an FA tag.

Ultimately the use of digits needs to be under option control, where they can be displayed for fast numeric studies, or where the long form can be spelled out for study of possible manuscript tampering.

I am setting up the new Paleo lexicon to cover both forms of writing for numbers so this becomes easy to setup in the future Paleo Bible app and related lexicon.

Prefix Mo

The paleo letter Mo is a picture of water. One of the meanings of water shows up in the standalone word for "from" spelled "Mo-Ne." Water of seed, so it speaks to the water of a womb, where we are all from. Thus for a very long time we have listed "from" as key meaning of "Mo."

So the Mo letter is showing up as a prefix on a limited number of paleo root words. Mo is NOT a common prefix. "From" as an idea in a sentence is usually just Mo-Ne as a stand alone word.

So I have been watching to see if I could figure out the normal but obviously rare grammatical use for Mo.

Frequently, a prefix Mo does not get translated into English at all. It seems to add something that is not needed by the English ear. "From" is important, so our assumed meaning becomes very suspect for this letter.

I finally ran into a example where it was being translated and it finally broke open the conceptual space for this letter in word definitions. It helps to see this problem by stepping through the exact root where this was found, and where Mo creates an important variant to the meaning.

Love: Re-Ha-Mo

The root word that I was entering into the lexicon was "Re-Ha-Mo." The most frequent English translation is some variation on the English word "love."

Depending on how you count, there are perhaps 200+ different variations as found in our reference text. This is an important word because love is an important concept in scripture.

This word is not always translated into English as "love." Selecting of certain other English words was triggered by a "Mo" prefix. As I was searching trough examples of the uses of this word, one of the Mo prefix examples was translated into English as "show love." The "show" being triggered by the "Mo."

In English "show" is the root word for "shower." Of course a shower of rain involves water. These are a concept match that still shows in English. So what does water have to do with our normal English word "show?"

We bathe for various reasons, but the key reason is to become presentable to others. So we can "show" ourselves to others. Thinking of bathing for the purpose of hygiene and health probably comes with germ theory around 200 years ago.

So then I went back to the other English words that were combining Mo with Love. Other than the Mo, these used the normal grammatical suffixes.

On the English side of the translation, adding Mo to love creates either "mercy" or "compassion." These are obviously more technical English language terms than the word "love."

Are mercy and compassion examples of showing love? Yes. Of course.

It looks like we have the solution to the word definition meaning of Mo.

Prefix Mo or Root Mo?

There remains an open question that the audit must solve. Is the Mo at the front of "Re-Ha-Mo" an actual prefix or are we looking at a 4 letter root word which is built upon a 3 letter root for love? If the Mo needs a punctuation before the rest of the root, then "show love" would the correct translation. If there is no punctuation, then "mercy" would be correct.

Audit work comes soon, and will sort this detail out.

As I continue work on loading the lexicon, I will be watching for more examples where this is going on. I don't yet know if this is particular to the word love, or if this is really a general pattern. But, it is explaining the Mo based on the 3d system, so I would expect it to work in similar ways with other root words.

Power of Translators

Ryan and I have known for a long time that translators carry a lot of power over organized church based on how they translate the text. King James himself was involved in the KJV translation because he wanted final say on word selection for that translation team.

History often says he was an ancient language scholar. That is utter nonsense. In reality he was a propagandist of the most vile form. He really did know of secrets in the text which he did not want revealed to his English speaking public. To prevent this class of criminal behavior, English language translations need to be word-for-word whenever possible.

The BRB has been our general platform for experimenting with word choices. In an ideal world we would have a 1 to 1 map between a Paleo root and a matched English root. This cannot be done perfectly because English is irregular. But outside of English language issues, this would be the goal.

Perhaps even better would be to teach everyone to read paleo. The exhibits exist for that purpose. In that case even English irregularity would go away as a problem for learning the inspired text.

My Work Flow

My lexicon loading process is to start with the most frequently occurring whole word found in the inbound text which has not yet been loaded into the lexicon. This is usually a specific combination of prefix letters, a root word and a suffix. My goal is to remove all variations of the root from my inbound list of words not current in the lexicon. In one case there was over 175 different variations on the root. These variations all go into the lexicon as a block under the shared root.

I know the common prefixes. Our shepherd staff work suggests these will always become stand alone, single letter, words. The prefixes almost always get translated exactly as stated. So I am not putting in English for the prefixes. The Du prefix is irregular in English, but I am still not entering specific English for that prefix.

I am quickly learning what are ultimately more complex suffixes. I can recognize all of them. But the English is still strange and hard for me to predict with accuracy.

Then, for each new root, I must look up and figure out what English is typically used. This can be tricky at times because the edges between prefix, root and suffix are not always clear, though this is getting easier.

I also need to be careful of cases where there is more than 1 English word for a given root. So I need to find and check a few different suffixes in order to make sure I understand the typical variety of English. Sometimes I reference our interlinear bible app to see how this has been translated by others.

At this point I have turned this into a game. The most common forms of most new roots either have no suffix, or else have Wa, so "the" as the suffix. So I am usually starting there, and can find the simple English for the root in question.

Then I guess the expected English for the less common suffixes for that root. Then I look up examples of the variant forms to check my guess.

I am playing this game better each day. In most cases I am correctly working the grammatical forms and my guesses are reasonable when coming into English. But I still get tricked.

Paleo roots can also be used for both nouns and verbs. So English may not use a single root for the verb as well as the noun. This is a common problem, but I can deal with that too. This problem is on the English side.

But then I saw an example this week where this principle of 1 to 1 mapping from Paleo to English was being utterly ignored. Something else entirely was going on. This is interesting enough that I need to share it here for the record.

Take: Ne-Sa-Ba

So "Ne-Sa-Ba" is fairly common. It has around 70 different inbound forms. (This including prefixes and suffixes which increase the raw forms.)

As I was checking the English for this root it was apparent that the most common English choice, for stand alone uses of this root, was the English word "take."

I know from earlier work, primarily the commandments, that "Ge-Ne-Ba" is the criminal form of taking. You can see the Ne and Ba are shared. So these are in a similar concept space. "Take" seemed reasonable.

So I played my game. The "Ta" ending on a verbs usually pushes the verb to past tense. So I would guess "Ne-Sa-Ba-Ta" should be the English "took."

I searched my reference, ultimately an Aramaic based translation, and found what I expected. "Ne-Sa-Ba-Ta" was "took" instead of take. All was well.

I was showing that I could anticipate the English. This meant I should be able to guess the other suffix based word forms, "he takes," "they take" "he took" and so on. I did spot checks to make sure I was understanding this root in these other forms. Most of the time my guesses were correct.

But in several places I started finding "receive" as the English for certain uses of this root. Take and receive are opposite sides of the same action, so this made some sense.

So I looked to see if either certain suffixes or perhaps even certain prefixes were changing the meaning. I have seen this many times before. I wanted to know what causes this change in English word choice.

If there is a clear spelling based reason, then I can adjust the lexicon entry for that spelling. I do occasionally need to use different English for different suffixes, this is not all that strange.

Not A Grammar Problem

I also checked some sample sentences. Could the translator have used "take" in English without changing the fundamental meaning of the sentence?

This is an important test because the teaching and learning process is much easier if we agree on the common English meaning for any given Paleo root. I am starting to mentally call this the "flash card problem."

If we can agree on a common English translation for a Paleo root then we can build a deck of flash cards. We can use them to learn to recognize Paleo roots as certain English roots. We can do this as a game. We can play the game collectively. We can learn to recognize Paleo at speed.

It turns out "take" would work in English just as well as "receive" in every example that I surveyed. "Take" would work in all cases that I surveyed, while "receive" would not.

What I found with this example is that the topic of the sentence was being used to change the English word choice. This was being done by translator's theological choice. It was exactly the kind of tampering that King James himself would be proud of.

So when this root shows up in sentences dealing with things like "offering" then the English gets flipped from "take an offering" to "receive an offering."

Because of this translation convention, what nobody reading English knows is that places in the text where this practice is described always seems to use "take" as the verb. The paleo spelling implies a softer form of the criminal form of taking.

Where?

This word game was only being played in sentences surrounding topics of the temple and tabernacle. Otherwise, "take" was the normal translation of this root.

The normal tone for "take" is related to the English word "nab." Taking is some action that is similar to what is done by a thief.

So in places that are priest friendly the translator flipped the English to favor the taker instead of the giver.

Concepts like how it is better to "give than to receive" are now made by the translator to apply to passages which involve "taking." This does not fundamentally involve giving nor receiving. But now, by translator word choice, it looks to involve this higher concept.

This seems to be an example of a translator managing down the tone of the translation. The text appears to tell readers that offerings are something "taken." Offerings are not something "given." Just like "entering the temple" has a verb that shares spelling with "evil," in this case we find strange things going on around the temple.

I assigned this Paleo root the English word "take." As we work through more steps in the recovery process we will see what is actually inspired. We will also look for any other word that actually means "receive." At this point, there is no defensible language reason why this root should not come into English as "take" in various forms.

Garment: Mo-Wa-Ne

The final new vocabulary word that caused some discussion around here this week was Mo-Wa-Ne. This word is commonly translated as "garment." The secondary paleo word definition is "Yo-Ta-The." Hand-Cloth-Wheel. I take cloth as cloth. I take Wheel as when traveling, and Hand as something like mine, as dealing with me. So a rough cut at the Paleo secondary word definition would be "my-cloth-[for]-travel." So a different English word choice would be coat or overcoat or similar. This word is not regular house clothing. It is not underwear.

This term was being translated pretty commonly as "garment." It had all the normal forms, including common plural forms. Most actual forms in the text are plural, which makes sense. All was fine, the word was working normally. It was within my understanding of the grammar and common meaning.

But there were a few places, again especially around religious locations, like the tabernacle and temple, where this was coming out as "vessel."

I should at least note that an overcoat, or raincoat, is a type of vessel for a person. So there is some sense of shared meaning.

But, this variation in English word choice was more like what was going on with the English from the root word for "take." There was no particular reason from the spelling alone to expect such a difference.

Exhibits?

As I surveyed uses, there were a few places where I could have translated "vessel" back to "garment" and in that word choice I could easily think I was reading about the wall hanging exhibits of the Tent of Time. Those exhibits may actually be called out in the text, and called "garments." The skill used to make fancy outer garments would be the same for making wall hangings. So they might be the same vocabulary word.

Finally, this term may have been repurposed to mean vessels, since post Solomon, the gold and silver vessels of the temple may have become important. So far, there are no important "vessels" in the set of exhibits. There are chests, but those have yet another vocabulary word still to be loaded.

There will be chests for the gold and silver series of items, so we have yet another case. Gold and silver to normal readers make no sense as types of garments. But they do make sense as exhibit identifiers. Readers for most of the history of the edited text have no idea what the text might really be about. Gold and silver garments tells me wall hangings for those series of items.

Dialect?

I discussed this with Ryan. He immediately pointed out that my examples of where this word is coming out as "vessel" are are almost certainly not inspired. Even more specifically, he would suggest these examples are from Ezra's era.

If that is true, then we may have a first example of looking at a dialect change. So "garment" came to also mean "vessel" at the hand of some future editor.

Ryan has better working familiarity with the text since he has been working with it for 20 years. He had good reason to think this word came to mean vessel across time. The early uses seem to indicate garment, or precisely coat as the main meaning.

So the meaning for "vessel" probably marks an Ezra era edit. It suggests Ezra was inventing temple service in his day, and adding the references to vessels as part of that editing pass. So seeing a meaning where vessel is the implied meaning in the context of the temple is a give away of a dialectic change at the hand of a later editor.

Notice how we are collecting vocabulary word issues that show up around the temple and tabernacle. These were areas where inspired writers would have not done much writing. But where editors were making stuff up, including repurposing vocabulary.

All of this, of course, waits for audit. But, this week we added yet another reason why an English word for a given Paleo root might not match what would be expected by simple inspection of the simplest grammatical forms that otherwise suggest the English meaning.

Ryan has continued to remind me to take my time on this lexicon loading process. I still don't know what I don't know. I continue to learn important lessons nearly every day. The whole tool chain will get much better once there is a complete lexicon. By putting time in now, the future steps become much easier to work on without needing to come back later and fill in missing lexicon values.

Language Learning Times

The link here is to a recent article on Zero Hedge dealing with the time it takes for English language speakers to learn various other languages from around the world. There is an important graphic that sorts languages by difficulty. The farther down the list, the harder the target language is to learn given a starting point with English.

This was interesting to me because I think about the problem of learning Paleo all the time. Will I be able to do it myself? I am getting old. How hard will it be for others?

The article linked above is in the context of diplomats needing to learn a foreign language, so their skill level needs to be fairly high. In the diplomatic world this means enough skill at writing, or at least reading, international agreements. It also means being able to speak the language with diplomats from other countries.

Inspired scripture would be of that class of document, but our vocabulary word set is going to not include modern technical terms like "phones" and country names and so on. So our language scope is less burdensome.

That article explains the issues that matter to the difficulty involved. Some examples include the set of pronounced sounds, and how different the script/alphabet may be compared to English. We learned to pronounce sounds for English when we were quite young. Learning them as adults is more difficult.

Differences in grammar also matter. A language with a similar grammar to English is obviously easier to learn. For English speakers, other northern European languages are the easiest to learn. This because these languages are similar to English.

In the list given in that article, Hebrew and Greek cluster together around half way down the list. Russian is listed as more difficult, but not that much more time to learn. The languages at the very bottom are the most difficult to learn. Those most difficult languages are Arabic, the 2 main dialects of Chinese, then Japanese and Korean.

These most hard languages vary from English along all the interesting parts that make up human speech. Their sound systems are different. Their script is different and their grammar is different.

What About Paleo?

Paleo has an alphabet that is nearly the Latin alphabet. So there is not really a new script. The only totally new drawn form is the Sha. In terms of pronunciation, only the Oo sound is particularly new.

There is nothing irregular in the sound system of Paleo, so it is fundamentally simpler. Vowels are fixed to the consonants, without any serious variation. Punctuation suppresses vowel sounds, but does not introduce anything tricky. So the Paleo sound system is very much simpler than the easiest languages on that list.

When we first worked out the Paleo keyboard I was basically an instant Paleo touch typist. Paleo really is quite familiar.

In terms of grammar, there are 4 common prefixes which are easy. These become stand alone words which are even easier to learn. Normal vocabulary always starts with roots. Most of these are new. But they often map to known English words.

Then there is the problem of suffixes. Working on the lexicon this past week I came to suspect that several of the long form suffixes will become trailing stand alone words. Certain of the suffixes are now also listed in the Lexicon as stand alone roots. The audit will confirm if suffixes need to be broken up. If so, reading Paleo will get even easier.

Basic Paleo sentence structure is also quite similar to English. We do no see serious change in word order when looking at Paleo with English interlinear. English is capable of a more diverse structure. So someone who knows English is already mostly ready for Paleo sentences.

I would guess that the learning time for Paleo will be less than the times listed at the very top of the chart in that article. It will be easier to learn than any current national language.

Match Dates

We were not expecting significant headlines this week. Most of the common war fronts were more or less back to normal.

At the beginning of the week the USA and Iran announced they had reached agreement on a Memorandum of Understanding. This allowed Trump to boast about ending the war. It allowed the Iranians to boast they were now about to start negotiating with the USA. The 2 sides view this very differently. Trump ultimately admitted the west was running out of oil, so he needed this agreement.

This week's document was a "Memorandum of Understanding." This is a technical term which means it has no legal sanding whatsoever. It is just political theater. Links for the MoU signing are given below. It was signed on Wednesday.

By the end of the week, Iran had declared the USA had violated the MoU by allowing Israel to attack targets in Lebanon. Iran declared Hormuz closed again. All Iran really needs are reasons to keep Hormuz closed in order to starve the USD based financial system of the wealth needed to pay interest. Time is on Iran's side.

Watch Dates

Peeking ahead, the next watch date is 2026-07-13 when we watch the replay of the last year of Joash's life and reign. More on this as we get closer.

Shop Work

This week we did another software update to the search function in the BRB app. There were certain odd cases where the code thought it needed to search again, even though there had been no change in the search string. That bug is now fixed.

It is now possible to run a word search and then move back and forth between the search dialog and the list of answers across various sections in the text. It is a nice new system for searching.

The lexicon now has 227 unique root words. There are 5813 individual word entries in the lexicon. There remains 45,100 unique words in the manuscript which are not yet loaded.

Lexicon Progress

The lexicon can explain 320,623 words in the running text. There remains 215,397 words that cannot yet be looked up in the lexicon.

I am continuing to run this process by hand because I am learning so much as I go along. I have given some examples above. There are some very VERY strange words in this system. I will return to more examples in future blogs.

For reference, when I passed the 200 root point there were 4817 entries in the lexicon, with 46,096 words still to enter. With 200 roots the lexicon could explain 301,882 words, with 234,138 that could not yet be looked up in the lexicon.

Note the exact math changes some from week to week because there are empty words that are being removed as I go. The Aramaic to Paleo conversion process has trouble with strange apparently decorative runs of Aramaic punctuation. I need to do some rewriting of the code for that problem.

There was a conceptual problem with thinking 200 roots are a magical point for coverage. In Greek text books 200 roots are the MOST COMMON roots. I don't yet know that number for Paleo as I am entering roots based on the most common FORMS of roots. The whole Paleo lexicon will need to be loaded before we know with certainty what the 200 most common roots might be.

There are spelling variations on roots that I would expect the audit to drive out. There are, for example, 2 different spellings of the root word for Israel. Currently these 2 forms of Israel count as 2 different roots in the lexicon. One of them is almost certainly a dialectic based difference in spelling. It may also be a scribal mark, so "prisoner speech," where they are telling us they knew a different inspired word lurks at that location.

These are the problems that I am learning. The code for recovery needs to be designed so that it can handle all the problems that lurk in the text.

Headline Review

The following headlines caught my attention this week.

Trump's Brain

Most everyone watching Trump knows something is wrong. An interesting joke captures the idea. Is he stupid? Or does he just play so on TV? In any case, the link above suggests the Iranians had to deal with this problem too, calling in experts to diagnose what might be wrong.

Stopping Land Sales

Seems someone is selling Palestinian land at a secret London expo. 100 lawmakers are trying to get it stopped. What city hosts the current head of the Zionist empire?

Hagia Sophia Construction

This link is to a Youtube video documenting current construction work that is attempting to keep the dome of that church from caving in. This is an important prophetic building, running on the 500 year temple cycle. There is a major project going on to make the building able to stand in an earthquake.

Romeo, Juliet and a Cat

On the same subject as Turkey... Cats are common across Turkey. The clip here is of a stage play where a cat walked on, apparently concerned for one of the actors who was playing dead. These types of videos are on my de-stress list.

Grok Against Iran

The link here is to a long form article on The Cradle dealing with an admission by the US military that they used Grok to help select targets in Iran. AI being used to kill is NOT a good thing. Ultimately, AI is an advanced munition and will not probably be left in the public's hand. On the other hand Grok did not ultimately help the US win. Grok ends up in trouble either way.

Tank Bottom at Cushing

The link here is to a long form Zero Hedge article that details how the Cushing oil storage tank farm is reaching tank bottom. Ryan and I drove that area a few years ago. We saw crews at Cushing building quite a few new tanks. A graph in that article suggests Cushing is drawing down to 2005 levels.

There is a problem with that article. With new tanks at Cushing since 2005, and many more actual tank bottoms, the unrecoverable bottom is much higher than it was in 2005.

That article does graph out new well production in the USA as having buffered some of the impact of the war. That does not appear to be all that meaningful to the overall problems in the USA. Any MoU breaches will transmit into the availability of oil in the USA.

Trump is on record saying the USA runs out of gas in 4 weeks. This is why he signed the MoU with Iran. Just by travel time, Iranian oil is more than 4 weeks from the USA. See the Trump's Brain link above. Trouble with gas station supply will still come in parts of the USA starting in early July.

Integrated chip manufacturing is expected to go offline here soon too because of certain chemicals that only come from the Persian gulf. So supplies of computers and related electronics are also expected to be disrupted here soon. Apple, for example, is raising prices. They say to cover rising supply prices, but in reality to shed demand for Apple products.

2022 Double Cross against Putin

The link here is to a post on Telegram detailing the events in 2022 when Russia pulled out of Kiev. Putin was tricked into thinking the west was agreeing to a peace agreement. Not so.

As the link hints, the European leaders are playing a high stakes religious game. The post, citing sources, indicates it was Israel that wanted the war to continue. This is more strong evidence that there is only 1 war with only 1 aggressor. Russia is just the victim. Eventually, the obedience of the nations is Russia's. See the promises over Russia that begin at Genesis 49:8. The Jews stole the name in order to claim those promises. Jebusites are a better term for Jews.

MoU Details

The link here is to a post on Telegram by The Cradle listing off the 14 points of the MoU with Iran signed on Wednesday, June 17, 2026. By late Thursday, so the following day, the Iranians had cleared airspace and declared the cease fire broken by the western side, this because of bombing in Lebanon.

Trump: 4 Weeks of Oil

This post on Telegram has the clip of Trump saying the USA has 4 weeks of oil stocks remaining. See the first link above on Trump's mental capacity.

Parallels to 1956

The link here is to a post on Telegram were Tucker Carlson catalogs the parallels between the current Iran war and the war in Suez from 1956. I covered this in a recent blog. The USA is now prophetically playing the part of the British. Like the British, the USA is now loosing control of empire.

An exact 70 year offset would want this to happen more severely later this year. But to anyone educated in history, current events so far are enough to draw the prophetic match. Generally speaking, the 70 year offset would expect Israel to be on the loosing side this time around. We haven't really seen that yet.

Versailles Signing

1918 Versailles Treaty

The top link is to Alex Christoforou's daily news briefing for Thursday, June 18, 2026. In the first part of this video he goes into detail of the significance of the location where Trump signed the MoU with Iran. Trump could not have picked a worse place. See the link above on Trump's Brain.

Turns out this is where Germany capitulated at the end of World War I. That treaty set the seeds for World War II. Trump appears to have set the seeds for yet another world war.

This was done while Trump was at a G7 meeting, with most of the other European leaders at the same table at the same time.

The other folks at the table in the room where Trump was seated were planning war with Russia, which is also a very bad parallel. Nazis against Russia both times. This is how obedience of the nations is eventually given to Russia.

Remember, we are on a prophetic replay of Resurrection Day. Joshua demanded a recounting of events from the previous week. The main event, in a prophetic sense, is now known as World War I and World War II. We expect a conceptual replay of those world wars to follow soon. Passion Week will itself be seen again in some prophetic sense on the current timeline in 2028. Then we see Noah in 2029, so we are only just beginning the full war.

A Versailles treating signing by Trump is a strong hint at where we are in a replay of those wars. Future timeline work may moderate this some, but this headline speaks to anyone with a eye to history. Alex Christoforou does a nice job of picking up on the symbolic meaning of what just happened, even if he does not know the prophetic meaning.

The second link above is to the Wikipedia article that covers the details of the June 24, 1918 treaty that was signed in Versailles at the end of World War I.

More Later,

Phil

Qu Map Update

Phil Stone — Fri, 12 Jun 2026 19:03:02 GMT

This week the Qu Map app has been updated to reflect a bunch of changes in our understanding. Before that, some notes on Lexicon work. Finally a headline review.

Lexicon Work

I continue to load words into the lexicon. I suspect another few weeks before this is finished. At some point I may automate entry of the "long tail" of single occurrence inbound words. But, so far, I am still learning tons about how the vocabulary words function within the grammar. Some examples follow below.

As I loaded the 134th unique root word into the lexicon, the lexicon reached the point where it can explain 50 percent of all words in the reference manuscript.

What this means is if someone learns 134 root words, along with all of their grammatical forms, they are theoretically able to read 1/2 of the words in the text as passed by history.

This is encouraging because it suggests there is hope for anyone who wants to learn to read in Paleo.

I have reached the point where I can see some strange vocabulary related patterns that are new to me. This is something that I did not expect to find during this work. It is causing me to want to keep going with manual entry, because I don't know what I don't know.

Roots

I am running down words that have been sorted by frequency. So the most frequent word still not in the lexicon is at the top of my list. I load that word into the lexicon and then scan down the list of remaining words for variant forms which share the same root.

Words which have unusual letters are the easiest to handle. So Ha or Qu or Ze or Jo or Pe in a root word will not collide with grammar related word prefixes nor suffixes.

If such a root has 3 or more letters, I can usually find and load all occurrences. Ha-Yo-Jo, the root for power, is an example of a unique 3 letter string because the Ha and Jo are not used in grammar. This is an example of a word that can be fully loaded into the lexicon all at once.

Other roots are more difficult because sometimes they land within longer words. So it is harder to know when this is a variation based on grammatical form or if this is a different word. I have learned that when in doubt I need to leave words for later, since I keep learning more details about the language system itself which is helping to solve these problems.

There are some interesting patterns in this system that I did not expect when I started this work. Let me give you some examples so you can see what is going on.

Tenses

Paleo, of course is a Semitic language. This means it carries most of its grammatical forms through the endings of words. These endings need to be learned in terms of the complete set. I have loaded enough that I probably have examples of every actual ending used in the text. I still do not yet understand what some of the forms may be doing. I expect there is uninspired dialect in some of these endings.

Sometimes the word ending impacts the English translation in subtle ways.

The most common ending is "Wa" which almost always becomes "the" in English. Another easy example is "Yo", the hand, which is usually "my" in English. The "Fe" ending is usually "his" in English, but English may want "her" or "it" depending on context. The "Ku" is usually "you" in English.

So far so good. There are around a dozen different endings, and then some times the standard endings stack up. So the possible combinations gets large.

The system also has a sense of plurals that we don't use in English. The "Ku" ending is usually "you" or "your" in English. But the ending "Ku-Ve-Ne" is a plural "your" which we do not use in standard English. "y'all" would be a rough match to the English plural for you.

Root Meaning

In this process I am chasing down the common English translation for high frequency words. For a simple example, "Yo-Du" is the paleo word for "hand." The "Yo" letter itself is a model of a hand, so this would be a candidate written name for the letter itself. This is a particularly clean example, and essentially all places in the text this root gets translated into English as "hand." "Yo-Du-Wa" is "the hand." "Yo-Du-Ku" is "your hand." "Yo-Du-Fe" is "his hand" unless English needs a different gender, like "her" or "its."

This particular word was so perfect, without any strange English, that I may eventually use it as a tutorial for the tenses themselves.

Some roots, though, get radically different meaning as the tenses change. I don't know why this would be. This may be a dialectic issue, that the word changed meaning with time. Say because of editors. It may be prison speech, so someone warning about edits. It may also be that there is a profound connection between what in English are radically different terms. This last case may be going on more frequently than I could have imagined before.

Let me start with a simple example.

Evil

The root spelling of the paleo vocabulary word for evil is "Oo-Ve-Lu." The English word is a transliteration into English "E-V-L." This is easy enough to understand. Our English word likely comes from this original Paleo word.

Where this gets strange is that the normal English meaning of this word is only picked up when this root is used in advanced forms. Let me start with those, because you will recognize them.

So "Oo-Ve-Lu-Fe" means "his evil." The trailing Fe defaults to male gender, but English gender would depend on context.

Other examples include "Oo-Ve-Lu-Ku" which would normally translate to "Your Evil." Usually the Ku will pick off a single "you." "Oo-Ve-Lu-Ku-Ve-Ne" would normally mean something like "your evil" where the evil is being ascribed to a group who are evil.

But what is strange here is that the root itself, stand alone, with no other grammatical forms is normally being translated into English as "enter." A survey of examples suggested this was not all that bad of a word choice given the sentences it was used in.

This implies something about the fundamental definition of evil. Evil appears to mean entering a place where someone does not belong. The English word "trespass" might be capturing some of this idea.

We cannot see this conceptual connection in English, but it is very obvious when looking at this word in context across the text.

At this point in the work I am loading the lexicon in order to work audit problems. I need parallel English to track audit code. So I don't really want to go further with word studies in terms of figuring out what might be going on in any particular passage. But, think about a paleo sentence like "Enter the temple." If this turns out to pass audit, there is a strange double meaning with the idea itself. The reader is supposed to ask about if this is an evil act. We have no such concern on the English language side of this. We do on the Paleo side.

Scepter

Another pattern I am seeing is a diversity of English that follows individual paleo words. The word for a shepherd's rod, or staff, comes out into English with a variety of terms. "Scepter" is an example. Note how there is serious emotion implied in English when we use scepter instead of just "rod" or "staff."

English translators look to be putting an emotional spin on stories that simply do not exist in the base text. A scepter is no different than a shepherd's staff.

Also curious about this particular word involves the more complex tenses. English translations shift the meaning from the rod itself to the flock under that rod, so for people this becomes "tribe" in English. This seems to be an intentional component of the design of the Paleo language.

We see this going on in the modern world when we put flags on rods. These become icons for whole people groups. On the paleo side there is always the implication that this is a shepherded group. On the English side we more easily think about flags as marking a territory with some level of government. We often loose track of the shepherding aspect of these groups.

The same word, "rod" is used for discipline. So their is a sense of threat involved. The shepherd carrying a staff can discipline members of the flock.

In any case, these are examples where the root word carries meaning out into different contexts. By using the same root in different contexts the Paleo language reader innately knows these are related concepts. These conceptual relations are totally lost on English readers.

I have given 2 examples here, but this same pattern is going on widely across the lexicon. What I am seeing this week is that readers of English translations are fundamentally illiterate.

Added Vowels

Years ago Ryan and I took a Hebrew class. We were introduced to several concepts. The first is that the spelling of a word implies a fundamental meaning for the concept space of that word. The second idea was to note that vowels had been added across history, especially before vowel points were added into what is now modern Hebrew.

So everything I just mentioned above will get stronger once the letter definitions are integrated into word definitions. Enter, and Evil, for example, have the same 3 letter root. So they will ride on the same concept space.

So in loading the lexicon this week I found my first good example of an added vowel. In this case parts of the text are spelled without an added vowel, and parts are spelled with an added vowel.

Worship

"Sa-Ge-Du" is the paleo root word for "worship." It is a very common word with many occurrences. It has the standard set of endings. There is limited variation in terms of translation. Sometimes, based on context, it will come out as "bow" or "bow down." Usually this word is chosen when worship is to a person. Translator sensibilities are probably in play here.

Modern Protestants don't bow down in worship, but think about the Hajj as a counter example.

There is a variant spelling for this same root. "Sa-Ge-Ve-Du." That Ve letter is a typical example of an added vowel. This word has the same meaning. It looks like this added vowel was added partially. Either this is a dialectic difference, or a subtle meaning difference. But without audit work, this looks like the textbook example of an added vowel.

Finding this word validated what we learned in class. It also creates book keeping complexity for future audit code. That future audit code needs to work both variations in order to see which survives audit. Based on what we learned in class, we would expect the audit to want the "Ve" removed from the long form.

King

The paleo word "Mo-Lu-Ku" translates into English as king. This same spelling is shared with Hebrew. As a memory peg, Martin Luther King was named by his father so his initials would match the Hebrew spelling of "king."

So there is another term, "Mo-Lu-Wa-Ku," typically translated as "angel" which has what looks to be an added vowel. It certainly fits the pattern we were taught in class. It is following the pattern of "worship" that I introduced above. In this case the "Wa" became the A in English, and that alone is a marker for an added vowel.

If the Wa in "angel" is an added vowel, then it reduces to king. A careful read of the text of Revelation might support the idea that there has been some sort of tampering going on. The throne room has 24 thrones around a central throne, the occupants are all wearing crowns, so this implies kings.

So at some point we adjusted angels in the BRB to be just kings. We have used that term for a long time.

This week I found a problem with "angel" related to the paleo grammar.

There is a fundamental paleo root of "Mo-Lu" which is normally translated into English as "word." The Paleo meaning may be something like the "flow of the shepherd." So it is fundamentally tied to something a shepherd like authority may speak or write.

So "word" here is in the English sense of "giving your word." There is an authoritative sense implied. This is not like a "word" as found in a sentence.

This "Mo-Lu" root can gain a "Wa" ending to mean "the word." So "Mo-Lu-Wa" is something like "the word."

Now watch a trick with king. "Ku" as a suffix almost always means "you" or "your" in English. So the root "Mo-Lu" becomes "king" by adding a "Ku."

So "Mo-Lu-Ku" by normal paleo grammar is "your word." But that entire vocabulary word is growing into a specific meaning. It now becomes the authoritative speaker over a group of people. This is why it becomes "king" in English.

Remember, of course, that asking for a king was a national sin carried out in Samuel's day. It is not a good thing, because now someone speaks authoritatively for you. The sin of asking for a king is found in the spelling of king.

Now, where this gets even stranger is the word "angel." It is spelled "Mo-Lu-Wa-Ku." At first glance, the "Wa" looks like an added vowel. It looks like it should collapse back to "king."

But this word is stacking up grammar on top of "Mo-Lu" to form yet another word. The basic root is "Mo-Lu" so an authoritative word. "Mo-Lu-Wa" adds a suffix, "the (authoritative) word." Then it adds yet another suffix. "the (authoritative) word, your." In English we would reorder the words. "Your authoritative word."

But it gets even more complex. We don't usually find "Mo-Lu-Wa-Ku" but we find "Mo-Lu-Wa-Ku-Wa." This is adding yet another suffix, the definitive article, "the" in English. (The stacking of endings is the complex point for learning the word endings at all.)

In this strange stack of letters we get the idea of the carrier of your authoritative word. The angel, or the divine messenger, is the English for this and it is a reasonable English. It is NOT an added vowel inside king.

So years ago when we were first figuring this stuff out, it was wrong of us to think the Wa was a simple added vowel to the root word "king." We were also making a couple of interpretive mistakes out of Revelation.

Elders sit in thrones, not kings. This is a complicating factor with Revelation itself. These are leaders who have mastered the entire text and have mastered all the exhibits and how to use them. This is a skill base we did not even comprehend years ago.

We also did not know that a "crown" is an exhibit item. Wearing a crown has a symbolic meaning. It means that someone can master the flow of history. This is what elders can do because they know all of the exhibits and how to use them. Besides also authoring the text, this is why they have such authority to be mentioned in Revelation.

Fixing King

I figured out this spelling problem with "Mo-Lu-Wa-Ku" one evening this past week after dinner. I was out in the shop. I stopped to tell Ryan about this, that we had a problem with how we had messed up the word "king." It was my intent that this needed to be fixed in the BRB.

Before I could say anything to Ryan, I learned he had been working on the Qu Map app, especially one of the grids. He said to me he was making adjustments to terms in the BRB. He was dropping some uses of the term king for a more correct "elder" and he was going to adjust king back to angel or messenger.

We had both reached the same conclusion in the same day, but by very different means. Let me shift and tell his story for work this week.

House Cleaning

Generally speaking, Ryan has been going through a house cleaning dealing with a large set of research notes that he has carried around for a long time.

Many of those notes go back many years, especially to an era when we were regularly visiting Disneyland. That was the time and place where we first worked out the idea of the Qu Map. So Ryan has been reviewing his old notes and deciding what needs to be brought into the Qu Map app, and what is now old and no longer needs to be kept current.

Qu-Map History

The Qu Map started out as a doodle. I was looking for a way to use the entire alphabet in some sort of icon. Because there are 25 letters and punctuation, and because 5 and 5 are the prime factors of 25, then the only even way to arrange those characters in a boxed form is in a 5x5 grid.

There are only a few possible ways to meaningfully arrange those characters inside of a 5x5 box. Should those 25 be arranged row by row, like woven cloth? Or should they spiral into the middle in some way?

The final form we use now is a spiral from the outside and is following the letter Qu. That letter informs the pattern and it sits center top.

We then found the Qu Map on the ground at Disneyland. The main rides in that park are arranged on the same grid. We later found the Qu map on the ground across the USA. Eventually we found it cross the whole world. Those become the 3 basic examples of ground truth for that map itself.

We looked at several other places for Qu Maps. Those may yet exist, but as far as the Qu Map app is concerned, those 3 maps appear to be the most educational. Finding these maps on the ground establishes a level of "ground truth" for what is otherwise just a theoretical study. It is also rather strange because it means the design of the USA, especially, is following some sort of divine plan.

Internal Mapping

When we work on any sort of project like this, we also look for internal maps. By this I mean we look into the text of scripture and look for maps there. One of the ways we've looked for a Qu Map in the text is by looking for a Qu Map as a map of the places and events in the text.

The problem is that the text does not contain any serious clues as to the exact locations of places of interest in the text. For a Qu Map to be seriously interesting, we'd need 25 locations. We'd need strong clues as to where the general locations in the text are actually found in the ancient world.

These don't seem to exist, at least not in a strong enough way to map them out in a rigorous way. Ryan is dropping this as a goal for the Qu Map app for now. So in terms of ground-truth, only the 3 modern examples are being kept in the app.

The other possible textual map is to look for any other lists that are known to run the alphabet itself. Since the Qu Map is ultimately a run of the alphabet, any other such list would also naturally connect to locations on the Qu Map.

The most interesting such list is the list of 25 likely authors of the text itself. This is so interesting that we need to stop and think about that list of authors relative to recent work involving the Story Grid.

These 25 men will be the "elders" as seen in Revelation. When they leave their seats and travel to earth they become "angels." This is because they wrote the inspired "word" of Joshua. They bring that authoritative word to you. It is defined in the spelling of the vocabulary words themselves.

Layers Of Manuscript Organization

Until this week we have been framing the likely inspired organization of the text around 3 levels, like 3 levels of headings. The highest level are general sections that follow the tribes. More precisely, the manuscript organizes around Jacob's blessings pronounced over the tribes. This also includes a strange comment at the end of those blessings about waiting for Joshua's salvation. That points at Hebrews, the part that Joshua wrote himself.

The next layer down are 70 books. These have names. They map to a 70 year cycle that repeats in history. Those 70 books are mapping out to 70 locations on what will be the crown exhibit. That exhibit is the master timeline. It maps to all of history. The elders wear crowns because their work maps onto the crown.

The next layer down is the 25x25 grid of stories that make up the Story Grid App. This means the text irregularly paces across history. Some times have high amounts of text. Other times have low amounts of text. It is not evenly paced.

OK, so where do the list of 25 authors fit into this list?

It turns out their list of names sits below the tribal sections and above the 70 book list. So instead of thinking about the Testimony as having 3 layers of organization, it has 4. 1) Tribes. 2) Authors. 3) Books. 4) Stories.

By length, this runs ~13, 25, 70, and 625.

That layer of 25 authors is likely to be mapping out to the Qu Map with 1 author aligning to each cell in that map. After long discussion we don't think the authors are in strict writing order. Joshua, for example, wrote the Book of Hebrews. This is the end of the list.

This actual writing was done earlier, so out of order. This seems to be happening in a few other places too. So these 25 authors are a slight change from the order of the books in the manuscript.

This gives freedom to figure out placement on the Qu Map itself. The internal letter pairing systems reinforce final placement on the map.

We don't currently expect this to become actual in order headings in the text itself.

That list of 25 authors/elders has now been updated in the Qu Map app. This is the biggest part of a major overhaul of that app that goes online this week.

Qu Map App

The link here is to the Qu Map. The permanent link is off Paleo.In.

The immediate difference from previous versions is inclusion of a Qu Map visual on the front page of that app. Generally speaking we are working towards having important graphics on the front of our apps. Except for apps that are naturally books, we are looking for graphics on opening pages. The Qu Map is the first to get this change.

There is also prose on the front page. Depending on your device the prose will either follow below the Qu Map graphic, or else it will float to the right.

You can use the drop down to select the "Elder" map in order to look at the throne room kings from Revelation. These are the original inspired authors.

Specific Elders

Let me draw your attention to a couple fun examples.

Tobit is now on the list. He was told to write at the end of his book. His book is the best example of a long form, road trip, angel encounter given anywhere in scripture.

Tobit is landing on the Mo letter, which on the USA map is Los Angeles and Long Beach harbor. Note that Los Angeles is "city of angels." Note that the road trip is like a trip on the freeways. The journey for treasure is like the 1930s migration from the dust bowl to southern California. (Now being reversed, also as per Tobit.)

Elijah is now on the Portland/Seattle areas. Elijah took a ride in a fiery chariot. The biggest such fiery chariots, the 747, was invented by Boeing in Seattle.

Peter is now on Atlanta. The big landmark there is a large rock. Peter, is the stone on which Joshua builds his church.

Paul is sitting on the Mississippi river, but more precisely Natchez Trace. So travel by water and land. Paul was always watching out for shipwrecks and road bandits.

In any case, there are lots of other fun things in that app.

Match Dates

We were not looking for anything in particular this week. The USA has started taking evening pot shots at targets in Iran. The Zionists who rule the USA have no choice but to continue trying to conquer the world.

Iran is responding to each strike, but in limited ways. We reach the next Noah dates at the 150 day mark, we only passed the 100 day mark this week. At the end of another 50 days we may see a 70th anniversary war matched back to the Arab Israeli war in 1956.

I have provided some related links in the headline summary below.

Watch Dates

Peeking ahead, the next watch date is 2026-07-13 for the death of Joash. We will return to this as we get closer.

Shop Work

I am doing lexicon work on the shop desktop computer because I can lay out the problem across multiple monitors. Let me give you current stats for that work.

In terms of full manuscript coverage, the lexicon can currently explain 281,757 words. There still remains 254,021 that are not yet explained by queries against the lexicon. So the lexicon coverage of the inbound manuscript is now beyond the 1/2 way point.

In terms of lexicon progress, there are 162 root word entries in the lexicon. Not all entries are complete. Usually root word entries are missing low frequency forms.

In terms of learning the language, this is encouraging because by learning prefixes, suffixes and only 162 root words, over half the text can now be read.

The lexicon does not yet cover very many important names, nor numbers. Most entries are of very common words.

There are 3892 specific word forms listed in the lexicon. There are 47,021 still to load. More than half of those remaining words only have 1 example in the manuscript itself. A major portion of those are in the Apocrypha which I might never load.

This long list of unique words is because combinations of prefixes and suffixes exist around a much shorter list of roots. Though I cannot select what is inspired, I can tell editors were using uninspired forms that mark their uninspired writing. There are serious dialect issues here.

I expect to automate some of this loading process once I am not learning as I go. This is a profound education that I am in.

This week I began to think that we will need something like a concordance app. The Paleo Bible app is not the right tool for working out the audit. Each root becomes the center of a cluster of audit related questions that spread out to prefixes, suffixes and then adjacent words. Concordances are usually organized around this structure, suggesting this sort of app is needed for the low level audit work.

Headline Review

The following caught my attention this week.

Pope In Spain

With a new, and young, pope he is able to travel. This link is for reference. He was in Spain, in part for dedication of a new church tower. The key point here is an estimated 1,000,000+ people were in the crowd. Huge, irregular, crowds like this can mark something prophetic going on. Unclear if this is such an event.

Xi to North Korea

Chinese leader Xi visited North Korea. First time in 8 years. North Korea may become a source of nukes for Iran. North Korea has also become something of an economic miracle, with Chinese and Russia trade.

Possible Iran Nuke

The link here is to a long form article on X by Pepe Escobar dealing with Pakistani sources indicating Iran may have a nuke. This is dated June 8, 2026. Generally speaking, Iran seems to be giving up on negotiations with the USA.

Crowds Reach 100 Days

The link here is to a Cradle post on Telegram. It has a pic of the crowds in Tehran. June 9, 2026, was day 100. Are these crowds counting to day 150 for the next Noah series date in Iran? Probably.

$3B Cash to Iran?

The link here is to a post on Telegram with one of many reports that cash had been given to Iran to stop bombing Israel. If this is true, Iran should burn the bundle. Probably laced with a bio weapon. The other problem is that the main goal of the war is to get Iran onto the western central banking cartel. This is a another, central, reason for Iran to stay well away from the US dollar in any form.

Legal Fighting at Temple Mount

There continues to be legal fighting over Temple Mount. This one dealing with noise related to the call to prayer. In order to rebuild a temple Israel needs to clear the area. They appear to be arguing about how best to get that done.

Belfast

The link here is to a post by Tass on Telegram dealing with the burning of a bus in Belfast. The crowds are getting angry over the government taking the wrong side in a stabbing. This is yet another expression of Zionism. The European elite (god's people) are against anything with a Christian heritage, including the Irish.

Train Video

If cat videos don't remove stress, then perhaps a train video will do? The UP 4014 is moving east on Norfolk Southern in celebration of the 250th anniversary of the USA. Unlike the 200th anniversary, the public is NOT really into this celebration. The US government has been occupied by foreigners.

US Strikes on Iran

Every few days the USA appears to be striking Iran, calling those strikes self defense. (The USA is not a civilizational state.) For what purpose the US might be doing this remains unclear. Perhaps trying to provoke Iran? The link here has Kellogg calling for a full war, it also has hints to Iran's nuke threat. This is the first time we've seen Iran's nuke threat in normal media.

Hormuz Closed

This link is to a Press TV post on Telegram reminding that Hormuz is now fully closed. This as a result of strikes on Iran this past week. Oil stocks in the USA are continuing to run out. The US west coast is expected to be the first area to reach tank bottom sometime in early July. The Iranians really need the world to run out of oil. This is the ultimate asymmetrical military play. It should help Russia as well with Europe. Iran is playing a waiting game.

Good Progress in Ukraine

The link here covers the current progress of Russia in Eastern Ukraine. This is a slow moving war. Eventually Russia and Europe will fight directly. For now, Russia continues to take territory from Ukraine. Putin is constrained by an election in September, so we would not expect dramatic changes in this venue.

Candace Trip to Russia

Candace Owens is not on my regular list of podcasts, so her content is mostly new to me.

In this video she explains events surrounding her recent vacation to Russia. In particular, one of her American security men had a medical issue that needed emergency surgery while in Russia. She contrasts the Russian medical system with the USA. The USA is a backwards 3rd world country for many more reasons than just health care.

She also covers destruction of Russia by the hand of Jews since the 1880s. This is NEVER covered by people of her stature. I can see why she is so popular. As she explains, she was widely attacked for this trip.

Candace had a remarkable adventure, and this is a very nice review of some very important world history. Russia really matters to the prophetic story of Passion Week. Working out the timelines is still future work for me.

By the way, I learned this week that the Paleo root word for "war" is down translated into English as "approach" when used with individual people. Joshua was frequently "approached" by Jews across Passion Week using this term. This means the inspired writer considered all of Joshua's interaction with Jews to be a low grade form of war.

So fulfillment of those stories as they have replayed across the past 200+ years would always expect headlines where Jews conduct war against Christians.

This point is self evident from the vocabulary words used in the text. But this is a detail that only native paleo readers would ever be able to spot. Candace is giving some Russian history that will eventually turn out to be timed prophecy. Given this week's lexicon work, now we know why.

More Later,

Phil

Lexicon Insights

Phil Stone — Fri, 05 Jun 2026 20:35:44 GMT

This blog covers interesting insights from lexicon work. Before that more updates to the story grid app. Then a headline review.

Story Grid

The link here is to the Story Grid app. The permanent link is off the front of Paleo.In.

This week Ryan has continued to work on the tooling that he needs for working out individual story placement. He has also been making changes in the table itself.

The center pull down menu in that app has a series of reports. There is 1 report for each story in the grid. This week the format of those reports has been cleaned up. Each report is now a page of story tiles. Those tiles are single versions of the same squares as in the main grid.

At the top of each report page there is a copy of the tile from the main grid. Then below that main tile are the tiles that can be reached through all the various row, column and diagonal folding that is known to run on the grid.

These reports do all the hard work of tracking down the story pairing, so regular users don't make mistakes in figuring out all the various pairs.

These report pages are designed for a normal user on a relatively large screen. The main grid naturally wants this. But, the report pages adjust layout for use on small screens. So Phone users have a chance of using that app as well.

Each story popup from the main grid also has a link to the "Report" page for that particular story. This makes it easy to bounce around from stories to their reports then move on to other stories.

The story reports have their own URLs, so they can be linked. Let me give you an example.

Endure Temptation

The link here is to story 525, which is the start of the Book of Jacob. This is where Jacob introduces his work and tells readers he is writing to the 12 tribes of Jacob. This outlines his book, he will run the tribes in order.

On the story report page, on the "Col Vine" pair, so the Column pairing on the vine's vowel pairing, you can see that story 50 will pair with the introduction to Jacob.

On that report page you can tap on the story 50 tile. The app will pop up that story 50 so you can read it.

What you find is a story from the start of the Book of Exodus where Jacob and the sons of Jacob are named.

The Grid wants you to see that the Book of Jacob is providing commentary on the historical story of the Tribes of Jacob as they came out of Egypt.

The Grid does not want readers to see these as just historical events. They are illustrative of life on earth. New Testament readers of the Epistles should not be disconnecting from the lived experiences of the historical books.

More Work

As Ryan gets the grid filled in, there will be meaning found through each of the folding patterns as called out in those reports. Ryan, of course, is still working on determining overall story placement. He has been adjusting the top table rows, and this is an example from his current work.

Note that this app gets rid of the need for reference works like Study Bibles. The woven structure of inspired text will be self interpreting.

Lexicon Loading

I have spent most of my time this past week loading up a new lexicon. This is the key set of data behind auditing the entire manuscript of the Bible.

Lexicons are rather important for translators, but I cannot recall anyone in normal church circles using a lexicon as the basis for, say, a Bible Study. Now I know why. Let me share some examples.

My Process

I have set up some tooling to make building the lexicon as efficient as possible. Code is reading in the entire Bible. It is also reading in the lexicon as it currently stands. For all words that are not in the lexicon, the software produces a list. That file is sorted by the most frequent words. That temporary file is also formatted with lines ready to be copied into the lexicon's master files.

My job is to find the root as well as finding a reasonable English word for that root. For this task I am mostly using the Bauscher Aramaic interlinear. I have discussed that text in previous blogs. Last I checked, it was available for free from Lulu.com.

Once I have my head around the word, I then search down the rest of the unknown words for other forms of the same root. I am learning the grammar, so I don't need to check every word, but I do need to spot check Bauscher for anything where I might be unsure of the English or if I don't clearly recognize the grammatical form.

For short words I need to be especially careful that I am not hitting some sort of special case. I have found a few ambiguous words that cannot be parsed without reading the sentence where they are found.

I don't expect this to be an inspired pattern because we expect prefix letters to become stand alone words. Sentence level audit work is needed to solve this class of riddle.

All the entries for a given root that I actually understand are gathered together and copied into the lexicon. Then I rerun the system.

Code does a set of sanity checks on what I just entered. Then gives me a new list of words that are not yet in the lexicon. At that point I repeat the process again.

One of the Lexicon internal sanity checks is to make sure all entries are alphabetic. This ultimately does not matter to code, but it matters for maintaining the lexicon later. It is much easier to keep everything in alphabetic order from the start than it is to sort it out later.

Progress

As of this blog there are 91 unique root words with 1597 suffix related entries in the lexicon. This means I have processed 1597 raw entries so far. Those now processed entries have the highest number of actual words in the running text. There remains 49,316 unknown inbound words still to process. So I have only just begun. The problem looks daunting.

In terms of manuscript coverage, there are 220,460 words in the manuscript that the lexicon can now explain. There remains 316,009 words in the manuscript that are still to be explained.

Though these numbers still look daunting, you should be able to see that a reader who fully knows well only those 91 unique root words can read about 2/5ths of the entire text. There is some math related magic going on.

I remember taking a Greek class many years ago and the text for that class gave the 200 most frequent Greek language root words in a preface at the front of the book. The student needed to learn those words by rote before going any further. That text then footnoted new words as they were found in the running text.

At the time, this made no sense. Why was this particular list so important to learn? Yes, they were common words. But, nobody could explain the magical math.

Now I know why this approach was taken. We will see what coverage we reach when the Paleo lexicon covers 200 roots. This is probably an important break point, maybe 80 or 90 percent of the words across the entire manuscript can then be explained.

I can easily see setting up a similar system with a Paleo Bible app. There needs to be some fun way to learn 200 Paleo root words. This will already include the single letter prefixes. Then there needs to be a fun way to learn the short list of grammatical forms.

If you are new, then set some options in the Paleo Bible app to flag new roots as they are encountered in the text. You'll be good to read some high percentage of the entire inspired text. You'll get help when you reach new words. If you are paying attention, you should be able to learn essentially the entire vocabulary as you read the entire text.

Unexpected English

There are some strange effects going on with how different endings create meaning that matches unexpected English words. Ha-Yo-Lu is the common Paleo root word for "power." The standard grammar adds a definitive article with a trailing Wa. So by grammar Ha-Yo-Lu-Wa, is "the power."

Sometimes this word form is translated as "the army." Why? Because "The Power" of the king is "the army." This term for army is thus an idiomatic use of the more general word for power.

In Paleo this makes perfect sense. But English readers do not naturally see the connection. In English the army is the arm of the king, not his power.

This is an example of a scenario that needs to be more generally understood after the lexicon is loaded and after the audit is run.

Common Paleo reading of stories may not be all that close to common English reads of the same passages. There looks to be much more deep understanding possible from the Paleo. Armies imply power. Someone with power of any sort is like a king with an army of soldiers.

More Prefixes

For many years we have known the most common prefix letters. These are Ve, Lu and Du. The Ve is a tent peg with ropes. As as prefix it means "and" in English. Lu is a pointing shepherd's staff. As a prefix it means "to" in English.

The Du is a closed purse. It wants to be opened. It means "what" in English, as in the question "what is inside." But English is very irregular, and the English equivalent is based on context. So in English, that Du letter might translate as "who" or "of" or something similar.

My word sorting process based on root words has clearly identified several more prefix letters. Three of those letters operate in the time domain. Those letters are Wa, the inspiring star, Ne, the germinating seed, and Ta the closing/covering cloth.

Bauscher does not translate these in any rigorous way. He was trying to show Aramaic primacy. So he was softening English. He was not trying to be particularly technical. In his work these 3 prefix words show up in his English translation as "shall" and "will."

This caused me to back up and understand these 2 English terms. A nice AI answer told me that modern English only uses "will." This word speaks to the time domain, indicating something "will happen" in future time.

The English word "shall" once implied a moral imperative or even a moral compulsion to do some task in future time.

Since we don't have a moral culture any more, the idea of moral imperative is now lost to everyday speech. "Shall" is still used in special cases. A judge might say, "You shall pay the fine." This means the judge can compel the fine to be paid. The judge means someone has an imperative to pay the fine.

I am currently looking to build the lexicon so it has single English words for each Paleo root that triggers a general meaning. For this round, these words are only intended as memory pegs so the audit work can go forward.

The first goal here is to piece together inspired stories. Softer, more idiomatic, English will come later. I am NOT currently trying to fully translate any sentences. I just need a hint as to what something means. This is what I am currently doing across the lexicon itself.

So what English should go with the prefix letters Wa, Ne and Ta?

We already have a problem that we are looking for a 3rd English term. But let me start by suggesting that the compelled, or morally obligated "shall" would naturally go with the Wa, the star. Then for a strict time domain, the English term "will" should go with the Ta.

After thinking about the problem, I realized there is a Bible story for the Wa letter that appears to be built on the grammatical use of that letter.

Magi Following Star

Adding to this analysis, we have the story of Magi who saw Joshua's star in the east. The link here is to that story in Matthew 2 in the BRB. The Magi saw Joshua's star in the east, and they came to see his birth. They brought gifts.

The idea of a star providing insight into ideas, or plans of work, is still common in our culture. A cartoon might show a light bulb over someone's head in order to indicate they had a "bright idea." In the 1800s such a cartoon was drawn with a flame. Wishing upon a star is a similar motif.

So the Star, as a prefix letter, might imply the action involved has some sort of moral compulsion. So the English word "shall" is a better fit than "will." Making the choice of a default map from Wa to mean "shall" then changes how we see the Magi visit in the birth narrative.

The star in the Magi would now imply they traveled such distance because they were compelled by some sort of obligation to come and see the birth of Joshua. (It did, of course, get their story into the text, which would be a good reason for a star to lead them.)

I am, of course, sketching this in. You might argue me in the details. But look at what is going on. That story of the Magi is many things, but one of them is an illustration (get it?) of how the Wa letter pattern functions in the lives of people.

Even if moral obligation is no longer a thing in wicked American culture, it is still a thing in Joshua's economy.

What about Ne?

So the Ne letter, the seed, is also a prefix. At this phase of the work The English words "shall" and "will" are already used. We are looking for memory peg words that catch a key concept. We are not yet trying to idiomatically carry precision based on use in a sentence. What other English might capture that Ne as a prefix?

The idea with a seed is that something is being "germinated" or "birthed." It has a time domain component just like "shall" and "will." The letter definition implies that the process involved will bring something into existence. There is a creative or building or birthing process involved.

When I see the Ne prefix I mentally think "to birth" but so far, a common simple English word for this one is escaping me.

The letter definitions of the Paleo alphabet appears to imply a high precision in terms of what the text is attempting to say. There will be much more work in this area once we are ready to run audits.

English Divergence

I am not trying to pick on Bauscher's work. He was working the issue of Aramaic primacy. So he is trying to match expectations in terms of what typical English readers might expect to read.

My world is the problem of editors and their heirs who mess with scripture. For centuries the heirs of those editors have remained concerned about "narrative formation." They attempt to nuance meaning in the translations in order to rewrite what was originally there. I am now seeing more games going on than I might have imagined.

So one of the most common words in the text is "Oo-Ba-Du" or simply obd. This can be a verb or a noun. The simplest English for this word is "work." We work, "obd," with our hands, for example. A worker, "obd," would be the one doing the work, "obd." The work, "obd", would also be the finished product, so also "obd."

This word is frequent enough that it has essentially a complete set of all the normal prefixes and suffixes. Should most uses survive under audit, this would be a good candidate word for teaching the grammar.

This word also has a few more prefixes than I have seen in other vocabulary words. So technically "obd" may also be a root word used in other words. So this is a complex word.

The variety of English terms in translation is strange. A worker, "obd," is also a servant, "obd", who is also a bond servant, "obd" or someone in cruel bondage, "obd." Simple grammatical forms on "obd" do not seem to be carrying this nuance in meaning that we see in English.

It feels like the stories of Pharaoh's Egypt have had their English spun up so nobody reading the text in English thinks that our current world is like Pharaoh's world. The base text does not make such a distinction. Pharaoh simply had an army of compelled workers. We might say factory, union, farm or tech workers. The high emotion English words we see in English texts seem to have been selected by modern translators especially for readers so they think Pharaoh's Egypt is different than our world.

It looks like vernacular language translators have long been spinning the story of Pharaoh and his world so current readers cannot see the connection.

This may explain why the timeline sees the time of the Jerusalem kings as the same as Pharaoh's Egypt, but our modern English translations hide the implicit connection found in the vocabulary that is ultimately shared between these 2 times in the written history.

Paleo Dialects?

My setup generates a line of text that is ready to be placed into the master configuration files for the lexicon. That line has the working lexicon data and then a comment that shows the usage count and then the first and last addresses of where that word is found in the manuscript itself.

Later on, software will always run the full list of cites for the word. But as a human comment it quickly indicates if this is in both the old and new testaments. It also hints at how common the word may be. Some words, for example, have first and last occurrences in the Apocrypha, which suggests a word form that was not used by inspired writers.

So the work flow is to find the root, mark any prefix ahead of the root, and then copy that line under a section in the lexicon for that root. This is not particularly hard, it is like a strange paleo video game.

As I am working through this process I am learning more of the grammar. I am also learning about the problems that future audit software will face. Another few weeks of this and I will have learned the various word suffixes, the grammatical forms.

Apocryphal Word Forms

Words that only show up in the Apocrypha are interesting. They draw my attention because I don't have quick access to an interlinear that covers those books.

If I can confidently parse the grammar for what is being said, then I can still enter the word into the lexicon. If I am not sure, I leave these words for later. I figure I will know the grammar better as I work through this learning process.

But I was struck by an idea that I wanted to share here, especially for readers who are following this project closely.

Imagine the late editors, especially the editors after Nebuchadnezzar. He was the king when the Alphabet for Hebrew was invented. So Mordecai, Ezra and Ananias are late editors, working and thinking in perhaps a version of the language that is no longer true to Paleo.

Did they think in the grammar of inspired Paleo? Did they know the same grammar?

Maybe the Wa/Ne/Ta variation for "shall" and "will" is happening because someone was using a variant grammar when they were editing the text?

Take this idea a little further. It is possible that especially late editors did not actually know the same language as the inspired writers.

This might be why the Apocrypha books seem to pick off vocabulary word forms that are not shared with the rest of the text. Some of these Apocrypha books are almost certainly not inspired. And the choice of word forms may be showing the difference between inspiration and regular writing.

I don't yet have full visibility to the grammar of the passages that Ryan is marking as likely to be uninspired, but I would guess at this point that uninspired passages will fail audit not only because word lists don't pass audit, but because grammatical forms of words in those passages are also not inspired.

Work Ahead

This lexicon work is slow but steady. It is creating a very nice set of raw lexicon configuration files that become the basis for a public lexicon.

I am not currently concerned with the audit. But you can imagine that all words in the lexicon itself need to be audited stand alone. Words that fail audit are either not inspired or have had some recoverable change that happened down through history. I can see Bauscher is translating across obvious manuscript spelling errors. Those look easy to find and fix using the audit.

I am currently mostly working roots that have many examples and many grammatical forms found across the text. These tend to be low value grammatical words like "if," "because," "when," "where," and "after." These also include key conceptual terms like "land," "work," "king," "day," "year," and "eternity."

This should be shifting soon to less frequent but still high value words like common names and more normal vocabulary words. I still don't know what surprises might lurk in this system, so I am not looking to automate this process with software, at least not yet.

There is a "long tail" of 1 off words at the bottom of my inbound list. Once most roots are known, those words probably get handled with software. We'll see.

Match Dates

The main headline event we were looking for this week was the replay of the end of the time when the boy king was hiding in the temple from the evil queen Athaliah.

When we tracked this same family of stories in 2002 this involved an IDF standoff at the Church of the Holy Sepulcher in Bethlehem. So I was particularly looking for similar patterns this week. 2 different venues had headlines that generally followed that same theme. Let me review those.

Haredi Protestors

Haredi Protestors at Al-Quds (Temple Mount)

The Israeli military is running out of possible soldiers and so has started drafting Haredi Jews. This community has been "hiding in church." So using their religious standing to stay out of military service. No more. The links above include photos of protests by this community.

In 2002 it was the IDF who was chasing Palestinians. So the IDF was at it again, but this time chasing Haredi Jews for service in the IDF itself. The 2 links above give some examples. The top is blocking traffic, the second is in Jerusalem. The laws in Israel have been changed to compel them to military service.

We are in a season of setting up for a great war involving Israel. So the need for soldiers is far greater than the Haredi. Americans will also be conscripted into this war eventually. Americans will not be able to hide in church either. The headline pointing at that future event also happened this week, with the merger of the US Military with the IDF. Here are the details.

$1.4T, With Israel

Long Form Article

The US Congress passed the laws for merging the US military with that of Israel. There have been many links on this point. The top link is just a short reference to this story. The bottom link is to a long article on Responsible State Craft that details this strange event.

The Zionist goal is a world government at Jerusalem. So that would mean a world military. Might as well form it now. Armies from other countries can be added later, say Europe.

This matters because the prophetic passages in the text deal with the armies that cross the river and head to Israel. If the USA is the same army, then the same must be going on in the USA at the same time. Armies attempting to cross the Mississippi are now a possible fulfillment, not just in the Middle East.

Hajj Timing

The other main "hiding in church" theme this week was related to Hajj pilgrims in Saudi Arabia. That can also be considered an example of hiding in church, or hiding in the temple. The first flights home to Iran for those pilgrims also happened at this same prophetic date.

It is reasonable to think that part of why Iran agreed to a cease fire was to allow Iranian pilgrims to safely participate in this year's Hajj. So there was safety in church in this scenario too.

First Hajj Return

Big Hajj Return

The links here are to Press TV (so Iranian media) posts on Telegram that have the first photos and then crowd photos of Iranians returning from Saudi Arabia from their Hajj related pilgrimages. These are dated from June 1, 2026.

I don't know the number of flights needed to get everyone home, but I would guess a week or more of loaded planes bringing Iranians home.

There is also a large funeral planned for the next few days which may moderate Iranian retaliation for another few days.

Trouble At Al Aqsa

Jordan and Al Aqsa

The links here are to long form articles on The Cradle dealing with Al Aqsa and the administration of Temple Mount. The top deals with settler related terror at that venue. The second details current discussions about ending Jordan's involvement in the management of Temple Mount.

Given current Israeli leadership's planning for a temple, Israel will almost certainly take over that venue at some point. The only question is how soon. We have more dramatic temple related watch dates in the next 2 years. So this may not happen right away. This is at least in the theme for this week.

Cops On Temple Mount

This is a short post on Telegram with a link to a long form article dealing with how Israel is changing the police force on Temple Mount. Another example of something going on there, probably in preparation for a temple.

Iran, China and Nukes

This link is to a video where Larry Johnson and Pepe Escobar are on the first episode of a new Youtube Podcast. This video triggered a firestorm of controversy around Larry Johnson this week because this was apparently an intentional attempt to tell the world that Iran has a nuclear weapon. This changes balance of power dynamics in the Middle East and West Asia.

That video's host is connected to the Pakistan military. He has a bunch of stuff to say about the current situation in and around Iran. He invited these well known guests in order to garner an audience and subscribers.

As this was a first ever episode there were some technical issues, especially at the end. But the key ideas are easy enough to understand: 1) China is working behind the scenes through Pakistan. 2) Iran has access to nuclear weapons via Russia. 3) They (who?) are working to arrange an alliance of nations against Israel. 4) This is also a war against the Petro Dollar which is expected to fail.

This is the first time I have seen an actual reference to real planning in preparation for an alliance that could theoretically perform a ground invasion of Israel.

The link above is worth the time to watch. Again a little rough as this was a first time episode. This will be interesting to watch in the future. Unclear if this new host can be trusted.

Kings of the East

The link here is to Revelation 12:16 in the BRB. This is the cite for the reference for the kings of the east who cross the Euphrates river.

Those nuke discussions with Larry and Pepe draw attention away from the other key points in that podcast. Iran is now aligning with China, Turkey, and a few other GCC countries which would be a setup for this Revelation story. This is now an active prophetic story, rather than a theoretical future prophetic story.

Watch Dates

We are now in the replay of the reign of Joash. Peeking ahead, his last year of reign will replay on 2026-07-13.

Because he spent his early years trapped in hiding in the temple, this next month or so may involve temple related themes.

Headline Review

The following other headlines caught my attention this week.

Iran Funeral Planning

Planning is underway in Iran for the funeral of the late Supreme Leader. The dates are not yet fixed. Expected in another week or so. This may also be like the Hajj, a reason for Iran to delay restart of the war. So this might be yet another example of hiding in church.

Hebron Mosque Closed

The link here is to a post on Telegram detailing the closure of a Mosque in Hebron. No real surprise, the Jews have closed it down. This is part of the Greater Israel, gangster, pattern currently going on across the Zionist world. No one can hide in this one either.

Beaufort Castle

The link here has a pic of the Israeli flag over Beaufort Castle in Lebanon. Another iconic marker for the war against Lebanon. This entire war has been a cease fire violation on the part of the Zionist side in the war against Iran. Who is our man of lawlessness? Unclear. But this is another place where no one can hide.

Donald Trump Jr, Wedding

Getting married is usually a good thing. In this case the President's son is marrying the daughter of the banker of Epstein. Strange world to find such a wife.

Pope, Jesus, Aramaic

The link here is a flashback to 2014 when Netanyahu falsely claimed Jesus spoke Hebrew. The Pope, who was seated with him at the time, corrected this mistake and said Aramaic. Fun. Like Netanyahu, most American Christians would get this wrong too.

Zionist At X

The link here is a follow on to my comments last week about the X algorithm. Seems there really is a Zionist working out the code for the X algorithm. Note that someone is using the Protocols of Zion to hide their use of the protocols of Zion at X. Can't make this stuff up.

Opening of SPIEF

The link here is for reference to record the opening of the Saint Petersburg International Economic Forum. This is an annual gathering. It is a civil alternative to the WEF. These meetings are focused on deals instead of globalist theology. This did hit the June 3 prophetic date.

96 Days

A short post on Telegram, still counting the days of large gatherings in Iran in support of the Zionist war against Iran. This marks 96 days.

Still unclear if we are counting out 150 days of Noah as a match to 5 months in Revelation. These rallies may be the counter. More time needed to figure this out for sure.

More Later,

Phil

Story Grid Updates

Phil Stone — Fri, 29 May 2026 19:29:47 GMT

This week there were more interesting updates to the Story Grid app. Before that, changes to search in the BRB. Then status on Paleo Bible work. After that we turn to Zionist control of X, match dates for this week, watch dates for next week and finally a headline review.

BRB

Most Bible apps have a word search function. Most of those search functions allow users to select what part of the Bible they want to search. Our BRB app, linked above, has been missing that ability for a long time. This week that function has been added to search.

The code to generate the search results word list is particularly messy. It has been around for a very long time. I haven't really wanted to touch that code because of the risk of taking 2 weeks to completely rewrite it.

In preparing last week's blog I was doing word searches in the BRB. I really wanted to search in sections of the BRB instead of the whole thing. I suddenly had a flash. Don't add this feature by rewriting the search code. Instead, make this a function of how the search results are actually displayed.

The hooks in the code to make this go are very minor. The rest is done through the normal option system along with cleaver style sheets. It only took a couple days for Ryan and I to get this worked out.

To play with this new feature, use the BRB to go search for a common word, like Joshua. This occurs over 3700 times. This is the sort of word where you probably want to narrow the scope of the answer. In the search box, you can see new buttons that narrow the results. You can move around in those results by tapping the different buttons.

This is a nice addition to one of our main apps.

TT?

Once this was working we stopped to look at doing the same thing in the TT. In the end, we did not change the TT. There were several reasons. The biggest problem is that there are no generally known sections for the TT like there is for standard Bibles. The other issue is that the TT is a smaller book, so there is less burden from long lists of search results. So the need in the TT is not as pressing as in the BRB.

There is another problem unique to the TT. That app still gets changed as the Story Grid gets adjusted, so any sort of section related search buttons would need to be rethought with each new iteration. At least for now, it seems best to leave the TT search function alone.

While Ryan was looking at the problem of perhaps inventing such sections, he had another major flurry of insight on the Story Grid, which is also updated this week.

Story Grid

The last major change in the Story Grid app was to pull the minor prophets up to the Ha row which sits under the rows dealing with the kings. These prophets provide back stories to the chronological stories that come in the earlier Kings related rows.

That shift puts those minor prophets in a better row in the table, but it upsets some features of the placement of some of the lower rows.

Mid Row Adjustments

At the start of this week, the middle rows of the table were adjusted yet again to balance out some of the interesting row matches that have existed in the past.

The main move was to push Tobit and his friends down to the Mo row, and raise Job up to the Yo row. Job's name starts with Yo. The Yo letter is a hand. The basic protection on Job is that the accuser is not allowed to lay a hand on Job's body. This constraint appears to be the marker that the Book of Job is intended to sit on the Yo, or Hand, row.

Psalms and Proverbs were returned to the middle rows. Psalms is now on the Ku row. Ku is a sprout than can grow into a tree. Psalms 1 uses the example of a tree planted by a stream of water. So the tree reference appears to be indicating the row where Psalms belongs.

Proverbs is now on the Lu row. Lu is a shepherd's staff. Story 300 starts this row. You can read in that story the introduction to Proverbs. That introduction to Proverbs deals with instruction, which is a key idea in shepherding people.

Tobit now starts the Mo row. Tobit was carried captive to Nineveh, which is along the main river system of the Euphrates. So these mid table adjustments seemed to finish off the row placement across the middle of the Story Grid table.

This was the status when we started looking at search.

Sections In The TT

After the Story Grid adjustments mentioned above, Ryan returned to the question of looking for section headings in the TT. He has previously had such headings, but had not looked at them for awhile.

The link given here is to the Contents page in the TT app. That page now has what look to be the inspired section headings for the inspired text. Section names themselves, of course, still subject to change. But, this is most likely the correct and inspired list because there are some important tricks going on. This also starts to firmly establish the row order running down the Story Grid table itself.

If you look at that Table of Contents page, you will see there are 13 sections. (Though Hebrews may linger as a 14th stand alone section. This work is still going on.) Each of these section headings appears limited to whole rows in the Story Grid table.

The trick here is that each section follows the Revelation 7 tribe order. Dan is at the end. Each of the blessings pronounced by Jacob over his sons contains hints at details that map into the same matched sections in the overall flow of inspired scripture.

To get this grid to work correctly, Paul's Epistles probably need to move down so they fall under the tribe of Benjamin. This brings the New Testament into more conventional order. This change in the location of Paul's writings shows up in the TT and Story Grid apps as of this week.

Interested readers can look at that contents page and think about how the various promises by Jacob apply to the sections running down the overall work. Ryan is currently working on his own detailed notes. He is doing this by building a series of additional tables that grid off the books. That work is ongoing, and may change some of how we understand this problem. But, let me survey what looks to be going on.

70 Books

Until this week there had not been any particular goal for the number of books that fall across those sections. But once you see Jacob's 12 sons as models for the sections, then the 70 (or perhaps 75) heirs of Jacob that go down to Egypt may then become a count on the overall number of books.

Note that 70 shows up in various places, such as 1) the table of nations. 2) Jacob's heirs that go to Egypt. 3) The Exodus era elders that went up and had a meal with Joshua. 4) The 70 disciples that Joshua sent out 2 by 2.

These 4 examples, if all inspired, would then hint at a list of 4, which is pointing at ciphers. Each book in the list of 70 may become a unit of text for the cipher system. I digress.

The story of Jacob's heirs becoming 70 is especially hinting that the next level down in the Table of Contents in the TT should be a list of 70 individual books.

If you look at the contents page again, you will now see 70 books listed there, numbered 0 through 69. Ryan has adjusted the list at the most likely locations where book breaks can be deduced. This is still a work in process, but you can see where it currently stands.

Alternative Tables

This number of books has 2 more alternative tables for understanding the books themselves. Joshua sent out his 70 disciples 2 by 2. This is idiom for sending them out in pairs. So the list of 70 books should also have some sort of innate pairing that runs down the list. So a book table that is 2 wide and 35 tall should show some level of content pairing at each row.

The crown 3d exhibit is designed to map out 70 years. So with 70 books we now have an obvious map from books to time.

That Crown exhibit timeline goes around the room 10 times. There are 7 years, or 7 times, for each circuit around the room. This crown pattern is hinted at in Daniel's 70 weeks. In that case the 70 and 7 factors are multiplied instead of divided. Leviticus 26 is also indicating that where ever you may be on that circuit, that you can look up or down by 1 row and find matched or reversed stories.

So if there are 70 books in the overall Testimony then there may be a repeating pattern every 7 books down the list. So there would be 10 such rows of 7 columns if we were building a grid like table. This becomes yet another grid that may inform finding correct book breaks. If it works as we expect, there may also be intended content matches on these cycles of 7 books.

This 7 by 10 table is a current work item for Ryan. He is out to see if he can dial in the overall structure of the inspired Testimony. It looks like this is not going to be all that hard to finish off. But, there are many fine points in the study.

Internal Lists of 12

There are 2 places in the Table of Contents where you can see lists of 12 individual books that sit inside a larger section. These 2 places are the Minor Prophets and the Pauline Epistles.

As these are lists of 12 we would think that these would also follow the tribe list and thus Jacob's blessings. This was perhaps just a hunch before. But now, these lists of 12 books appear to intentionally follow the tribes. This is likely to be the intended way to figure out the inspired order of the books in those 2 sections, especially the order for the Minor Prophets. In the case of Paul, his travel itinerary in Acts helps set the order.

625 Stories

Of course below the 70 books we also find the 625 stories of the Story Grid. These stories do not spread evenly into the 70 books. They are generally placed in the story grid because of the overall design of the Testimony itself. As we start to finally understand the overall design, the stories themselves will continue to settle into place.

This week's changes in understanding of the whole system is shifting the low level stories around in various ways. Some of the hard problems in figuring out the Story Grid now look easier to solve.

Life Diary

Some long time readers here may remember a timeline study that we called the "life diary." The idea was that all humans on earth run through the books of the Bible, in order, at the pace of 1 book per year of life.

We studied this, and we had a friend who tried it against his own life. The result was very promising.

But we were still struggling with book order and did not have strong conviction that we could get good "signal" out of the "noise" to prove this would work for everyone.

Now it looks like the 70 books are going to map out to the 70 "years" that go with the crown exhibit. This would also be the 70 years of Joshua's life. Eventually, this work can be checked against the trunk timeline of the text. If this works for Joshua, then he may be following a pattern that everyone else can theoretically be following.

So now there is a path for internally confirming the Life Diary hypothesis. Once we can do that, it then becomes relatively easy to apply to individual lives.

Over the years we've touched on important prophetic ideas but at the time did not have the tools to fully understand. Life Diaries are yet another such example of something that may turn out to be very important.

Shop Work: Paleo Bible

This week I have continued to work on the tool chain for the Paleo Bible app and manuscript.

Because this is ultimately an audit, the code itself needs to be written in a certain simple style. Anyone who knows basic Javascript should be able to follow the code without anything tricky or clever going on. Just like writing for English as a Second Language readers, I am coding for Javascript as a Second Language programmers.

So this week I tore through everything done so far and made it as simple as possible. Build steps, for example, need to be named as step1, step2 and so on. This makes the order of the steps easy to understand.

Similar code should never be duplicated, as much as possible the code should be shared between steps. Reading and writing the whole Bible, for example, is now a library function. The format between steps is now also always the same, an annotated list of words.

Each step in the process needs to generate a new copy of the Bible stored in the file system with some set of changes. This allows manual inspection of the results of each step in the chain. Each step must also generate statistics for what was done at that step.

In cleaning up these steps I also put in better input sanity checking. There were several places where complex Aramaic punctuation was generating blank Paleo words. The Aramaic to Paleo conversion step now promotes complex punctuation towards single Paleo Colons and Paleo Quads. These fixes changed the overall word count. That count is now reflecting the word definitions that matter to paleo, it is not counting blank spaces between punctuation characters.

As far as the eventual audit is concerned, all inbound punctuation must be treated as a suggestion. So promoting punctuation does not appear to be a serious issue. All of the steps can be run again, so this is not a serious issue.

Lexicon Work

With code cleanup done, I turned my attention to the lexicon. This is the first input to the audit process that comes from outside of the inbound texts. This is the step I have started in the past, but I have never been happy with the results.

This time, I am trying a very different process for creating the lexicon. This has a very different file format. The lexicon configuration files are now organized similarly to what will be shown in the lexicon appendix to the Paleo Bible app. So the categorization process for words going into the lexicon is happening early in this process and being done 1 word at a time.

I have started to load the lexicon with the most common words. This is giving me coverage. But it is also giving me the chance to check the design of the lexicon. I need to make sure the lexicon files can express all the issues that actually occur with real words.

There is also code that refactors the lexicon entries so that they can be easily applied to the running text. That refactoring has never existed in previous attempts at this work.

This format takes more effort to write initially. But, it makes far more sense from the perspective of someone trying to understand the code itself. It will also be much easier to maintain and to extend should that be needed.

The lexicon configuration files are organized strictly around Paleo root words. The actual inbound forms are listed under the root. The first step is to identify prefixes. Then the known root/suffix pairs are listed along with English that should be displayed.

As of this week, the lexicon configuration files currently explain what to do with about 1/4 of all inbound words. (Though to be fair, this is a small fraction of the actual work, it only sounds good.)

Next on deck are more build steps that apply the lexicon to the inbound text and also work the audit system against the text itself. More on this in future weeks.

X Algorithms

For many months, Elon has been boasting that there is no secret stuff going on with the X algorithm. He has claimed that anyone can read the code which is publicly available. So there is an implication that there is no Zionist control behind X. This is patently false as I will get to below.

As a practical matter, most of the large accounts on X have seen a dramatic drop in readership since these changes went online. It does not look like there is any good way, nor reason, to attempt to generate an audience on that platform. The hope that flowed when Elon bought out that platform is now gone.

The link above is to a post on X which explains how the new X algorithm works. It explains why there has been such widespread dramatic drops in readership. You can read through this post in order to get a technical understanding of what is going on.

Protocols of Zion

When I read through that post I realized I was looking at a nearly perfect implementation of the algorithms first described publicly in a book called the "Protocols Of Zion." That book is now around 120 years old. It was a key part of Henry Ford's litigation with bankers, when they tried to take the Ford Motor company from its original founder.

That book explains the strategy for how Zionists cover up crimes committed against the public. Ultimately the goal is to prevent the public from being able to reach consensus on who caused certain classes of crimes. Examples of these crimes include crimes like assassinating President Kennedy, or blowing up the Twin Towers or getting Massie removed from office.

This group of criminals follow the "Protocols" to solve certain problems. The most basic problem is that the truth of their actions is almost always published. Their crimes are almost always correctly documented in media source that is readily available to the public.

So their real problem is how to hide from such truth.

If their strategy was to deny the truth of such crimes they would only attract more attention to themselves. Individual criminals often find themselves in this situation. The Protocols explain various better tricks to hide from the public.

Flooding

The most important, and most common, trick is a strategy called "flooding." They intentionally promote alternative explanations that provide alternative ways of understanding what happened. This is not done with just 1 alternative explanation. This is done with a multitude of alternative explanations. They want to flood all media channels with as many alternative explanations as possible. They don't even need to invent alternatives. They just promote as many alternatives as they can find.

In 1905 this meant flooding in magazines, books and newspapers. By the 1920s this included radio. By the 1950s this included TV. By the late 1990s this included websites. Now this includes social media. Whatever media the public follows, that is where the flooding must happen.

In this way, the public can never reach consensus about what happened.

Examples

Was 911 a bunch of terrorists who learned to fly? Directed energy weapons? Bombs planted in the building? A nuke in the basement? A construction design flaw?

Was Massie outed by big donors buying media? Or by ballot stuffing? Or by voting machine fraud? Or by a change in public favor against Massie?

Was Covid a lab leak? Was it a bio weapon? Did it come from China? Or North Carolina? Or Africa? Was it real at all? Was the vaccine safe and effective? Or was the vaccine the weapon? Was the seasonal flu repurposed?

These are all examples of flooding. Every possible scenario needs to be promoted. So the public cannot ever reach accurate consensus on what happened. So the public cannot fix what happened, nor prevent it from happening again.

This process of flooding is the Zionist playbook. Any algorithm that implements it is following the Zionist playbook.

Immensely accurate prophetic timelines that are found in every church gathering place are likely the antidote to this problem. That won't happen for a long time.

Back to Flooding on X

So now think about the new X algorithms. Several changes have been made to X in order to "flood" readers with spurious content. It is no longer a place where the public who uses X can use that platform for "truth seeking." That function has been removed from the platform by creating a perfect Protocols of Zion system for flooding that media channel. (I would guess the recent Zionist buyouts of other platforms, like Tiktok, are also doing the same.)

By addition of automatic natural language translations, all X users from around the world can now speak to all other users. This is a neat AI trick. Like before the Tower of Babel, we can now all speak to each other, we share the same language. The whole world is now open to write posts for every other user in the world. We can all talk to each other.

But this means that, say native English speakers, who share politics, are now faced with posts from around the world from people who know nothing about the politics of the English speaking world. This is just 1 example of Protocols of Zion flooding on X.

Shifting to Entertainment

X has also been changed to track user interaction. It promotes posts which share content with posts where a user spent dwell time.

Let me give you a practical example. I am on X for news headlines and their commentary. This is at times horribly depressing. I am reading about the prelude to the end of the world, and I know it.

So I usually want to end my time on X with some emotional relief. So I end with non-news stories to reduce my stress. I like cat stories and videos, and these work to calm me down.

These have a format. Someone rescues a cat found in some distressing situation. They bring the cat back to health. Then they adopt the cat. Then the human and the cat live happily ever after. These are furry tail stories.

This can put me to sleep after a rough day of checking otherwise world-ending news. At least with cats there is some humanity in the world, unlike Gaza and Lebanon.

But if I really do fall asleep, my X page is open on cat posts. So the next day, all I see are more cat posts. Why?

Because I gave dwell time to cats. I don't follow any account that has anything to do with cats. That fact doesn't matter. The X system thinks I am there for cats. It wants me to keep interacting with cat content.

So X now promotes little to no actual headline news or commentary.

The Broader Result

Everyone using that platform goes through something similar. X wants to flood your feed with entertainment, not news. It does not want to give user dwell time to any serious matter of the day. It does not want to give dwell time to the accounts that you actually follow.

So I am no longer seeing posts where the public is forming consensus on the crimes of the day. Since Zionists cause nearly every headline these days, X has become a nearly perfect implementation of the Protocols of Zion. Even if the code for that algorithm is open sourced, it still does a fine job of preventing the public from reaching consensus on anything.

There have been quite a few other changes. X no longer has any algorithmic bias towards domain experts. Remember those? The people who figure out crimes? That class of domain expert users has been replaced by entertainers. So world experts on any topic are no longer able to find a following for their content. (Mike Adams, Lord Bebo, and many others have posted about how their readership numbers have seriously fallen. These are domain experts and Zionists are afraid of them.)

Cat videos are more important to X than skill. Elon himself is a world class domain expert. But his posts get promoted because on X he is an entertainer. His politics are just entertainment, not a crime scene investigation. He never touches anything serious. Given his situation in life this is probably wise. But, what is the point?

You will notice that my headline review links that I put at the bottom of these blogs are now more often coming from Telegram. On Telegram every post on every channel I follow shows up in my feed. Nothing is being hidden by a Zionist algorithm.

I do not follow cat channels on Telegram. So to me, there are no cat stories on Telegram. Once I finish scanning Telegram for news, I can return to X (or Youtube) to find cat videos before ending my day.

Presumably Telegram will eventually be taken over by Zionists too, Telegram won't remain this way forever. But, for now, Telegram is a much better platform than X.

Match Dates

This past week we were watching Thursday, 2026-05-28, for the replay of the year of Ahaziah's reign. This was the point of Jehu's wild ride when he did in Ahab's son, Jezebel and many others.

The trick to finding this headline is to remember that Jehu is a Latin form for Yahu. So we should be looking for Natan-yahu doing something like a wild ride. This ride seems to have happened in Tyre as part of the ongoing war in Lebanon.

Tyre Evacuation Zone

The Israelis have ordered the evacuation of the Tyre region in Lebanon. So the people who live in and near Tyre are fleeing north on their own wild ride. They are running from Jehu.

This, of course, is so Netanyahu's men can take over Lebanon as part of their greater Israel project. There have been rumors of Israel's plan to eventually attack all the way to Turkey. So there is ultimately nowhere for the people of Lebanon to run. This is another genocide.

So this is a headline match by name and time. This link includes the map of the evacuation zone. Many other posts are dealing with the sorry situation on the ground. I really need a cat video.

Follow Up On Massie

Last week I mentioned how Massie's loss of his seat in Congress was a match to the story of Naboth loosing his vineyard.

I had assigned that match just because it had interesting details from the Naboth story. At least in Massie's case, so far, he survived with his life. Massie has indicated he will run again in 2028 for his same seat. He is not going to run for President.

As a general rule, I have not been trying to track northern kingdom prophetic stories because they are very hard to time. There are problems in the text with crossing the calendars. So this work waits for audit.

This does not mean the northern kingdom timeline is not actually running.

So this week we see the end of Ahab and Jezebel as part of Jehu's wild ride. So Massie's story about a week ago is correctly timed to be our expected match to Naboth on the actual timeline. That was not just an accidental prophetic match, but a real and expected headline.

Jezebel will turn out to be one of the wealthy female donors to Trump and his crew. She will be the person who got Massie removed from his land, from his seat in congress. Ahab will turn out to be Trump, such a looser.

Hajj Delays

The Hajj itself is functioning like the story that begins on 2026-05-29, where young Joash was hidden in the temple for fear of Athaliah who was on a rampage. Think safety at church but on a grand scale. Links for this in the headline review section below.

Safety for visitors to Saudi Arabia should last about another week.

Putin Travel

Also on 2026-05-28 we saw Russia's president Putin on a trip. This is an almost regular trip. Links on this in the headline section below.

Watch Dates

Next week we are watching 2026-06-03 for the replay of the death of Athaliah. This was the evil queen that ruled while young future king Joash was hidden in the temple. This is the Wednesday after this blog goes out.

The following day, so 2026-06-04, Thursday after this blog goes out, is the start of the reign of Joash.

Temple Mount and Hajj venues in Saudi Arabia remain reasonable venues to watch at this point. If the USA and Israel have been waiting to resume war with Iran because of the Hajj, then these would be reasonable dates for that.

Headline Review

The following caught my attention this week.

Hajj Pilgrims

Estimated 1.5+ million

Vast Crowds

Stoning The Devil

The pilgrims in Saudi Arabia appear to have been the reason that Trump did not start attacking Iran. The links above give some sense of the massive crowds. This is the largest regular gathering of people on earth.

At Temple Mount (Video)

At Temple Mount (Pic)

Similar to the Hajj crowds, there were also massive crowds atop Temple Mount. So far, the Israelis are letting the crowds alone. The top is video which may not play outside of the Telegram app. The bottom is a pic of the same place.

Kiev In Flames

Big Smoke, Kiev

Missile Statistics

About May 22, 2026, saw the Russians retaliate against Kiev for a bombing of a school in Russia. The first link here is some of the damage to Kiev. The second is smoke rising the next morning.

The Russian public is now in support of the war against Ukraine. Most commentators expect the war pace to increase from this point forward. World War III is growing. Will the Nazis win on this second try?

12th Anniversary of Ukraine War

Most western Zionist media place the start of the war in Ukraine at 2022. The war actually started May 26, 2014. We just passed the 12th anniversary. The link here has reminder of the first shots of that war. The Ukrainian Air Force bombed civilian targets in Donetsk. This is matching sunrise on resurrection morning. ~15 years on our modern clock from that point to Noah+7000.

USA Tricks At UN

The United Nations is the international organization that goes with the USA. This is a Bible Tribes study point.

The USA, so the Zionists, play games to manipulate the UN in various ways. The most important is through visa control, preventing UN member delegations from entering the USA.

The link here is but a recent example. In this case the USA stopped a Palestinian from high UN office through visa threats. The UN should be moved to Iran. Noah's first colony.

Bankers Games

Against Iran

The top link here is to a post on Telegram, itself a clip from Tucker, that deals with how western bankers, so Zionists, intentionally work to keep most of the world poor. (I would add, it is the same for people who live in the USA.)

The second link is a post that details the specific goal of the bankers crashing the Iranian economy. These games are as old as Solomon, if not Pharaoh before.

Iran Downs USA Drone

Shooting Resumes

These links to posts on Telegram discuss the first resumed shooting between the USA and Iran. The USA was targeting Iranian positions. The Iranians retaliated, shooting down US drones. The Hajj appears to be limiting the actions of the USA.

Putin in Kazakhstan

Putin arrived in Kazakhstan on 2026-05-27 for a 3 day visit, so across the main watch dates for this week. Putin has been a Moses figure. Kazakhstan seems currently to be an uninteresting place. But this may be a lost tribe of Ishmael and may have a more interesting future.

Merkel: 10 Year War Plan

This link includes video of Germany's Merkel answering questions about the German war plan against Russia. She lets slip this is a war plan with ANOTHER 10 years. The Russians are fighting the German Nazis all over again.

At 12 years from now we reach the end of 430 years of Europeans at Jamestown, Virginia. This would be a dangerous time for the fall of the USA as a prophetic replay of the 430 years in Egypt.

So Merkel's timeline may not be all that messed up. The Russian's have good reason to threaten the EU with nukes. Presumably, the Russian government knows the plan Merkel is citing.

Hajj Schedule

The link here is to an article on Sonar 21 that gives the dates and events for the Hajj rituals this year. They complete on May 29, 2026. The crowd still needs to go home, which would take a few more days. This is lining up with the start of hiding in church. This is a reasonable match to the week to come.

Launch Pad Explosion

The night of May 28, 2026, there was an explosion on the Blue Origin launch pad in Florida. The link here is to a Scott Manley video with an initial report.

The energy release was equivalent to a nuclear weapon. Normally I would not reference an industrial accident as a candidate headline event, but this has all sorts of implications across the American space program, as Scott explains. It may take a year or more to rebuild. If anyone lives in the moon, they may not want guests playing golf on the surface.

More Later,

Phil

Modern Villain Vocabulary

Phil Stone — Fri, 22 May 2026 21:12:18 GMT

This blog looks at modern vocabulary for our standard list of 6 villains. Then we look at Putin's trip to China as the headline match this past week. We also look at watch dates for next week which include Jehu's wild ride. Also, shop work notes and a headline review.

Lawlessness

Since Trump's election the federal government looks to have been taken over by a crime family. Patterns of lawlessness can be seen with nearly everything Trump touches. But Trump is also well connected. He is but a node on a wider criminal network. Europe and the Middle East are also ruled by this same cartel. A few places, like Russia, Iran, China and Cuba sit outside of this same cartel, but even those countries must still fight the cartel in order to survive.

These patterns of criminal behavior are quite old. But, there has been a recent change in the public conversation about this ancient problem. The strange patterns of behavior seen in public figures are now gaining common vocabulary and are being discussed regularly on social media. These vocabulary words then give especially young people the anchor points they need to talk about the problems in the world.

The new patterns of public conversation are ultimately rooted in the nature of life on earth. These conversations are rooted in the scriptural patterns of Egypt. They are embodied in the life works of the 6 manuscript editors, our list of 6 villains.

In this blog I want to run the list of villains and map their stories to the key modern vocabulary that shows up in social media. My purpose is to make it easier to connect the stories in the text with active patterns in the political world.

Ultimately, nothing we see around us today is outside of the text. The only real problem is one of understanding the vocabulary.

#1 Solomon: Capitalism

Solomon was the first editor. Though he is not the first king at Jerusalem, he becomes the most famous, having built the first temple. Ahead of Solomon, there had been no grand public works projects. Then, in Solomon's day, there are 2 such projects, the Temple and the Palace.

What changed that Solomon could pull off such public building projects?

I am selecting "Capitalism" as a marker for Solomon because of 2 general ideas. The first is that kings require a capital as their seat of government. Until the heirs of Jacob asked for a king, they only had an annual meeting at the fields near Shechem. By Solomon's day, Jebus, so Jerusalem, had became established as the capital. This was the seat of the government and the king. This was the capital.

We use the same English language word for the type of economy we currently see in the USA. Capitalism in the financial sense of the word. Most Americans would conflate a free market with capitalism. The heirs of Jacob had a free market in goods that had run for around 500 years before Solomon. Something changed at Solomon. Money was now tied to the activity at a capital.

The text itself does not give any obvious modern key words for the financial change that started with Solomon. But, it does give a list of the financial effects of Solomon's rule. He had imported the ways of Egypt. Solomon was returning his nation to the ways of Egypt, even if he was not physically moving them back to Egypt. The details of his work to this end are found at 1 Kings 10:14-29.

What makes Solomon different is how he started taking "deposits" from the people. This word is mentioned in 1 Kings 10:25 in the BRB. We call deposit taking institutions "banks." Banks, at least traditionally, kept real money assets in a vault. Then they issue claim checks on the vault. Those claim checks can be traded, we now call those claim checks money.

Eventually, more claim checks are issued than there is wealth in the vault to cover all the claim checks. Then, eventually, the vault can be completely removed. This is the multi-step process to modern Capitalism. Solomon had done the same thing.

Empty Vault

This is a financial game that can be played as long as there are assets that can be added to the vault. That 1 Kings 10:25 passage lists many possible things that can be "financialized" or vaulted. That list includes "gold, silver, garments, armor, spices, horses, chariots, and mules."

Spices were not fuel in Solomon's day, but this is the term that would cover oil. "Horses, chariots and mules" would cover all the parts of the transportation industry. Today these are called motorcycles, cars and trucks.

Most of these are purchased and traded using debt. Claim checks outside of a vault are called "titles." These exist as functional equivalents of claim checks against a valuable asset in a vault. Titles themselves are often vaulted in lieu of the item itself.

With the banking system established, Solomon could use claim checks on his vaults in order to raise and pay for an army. The best example is in 1 Kings 5:13-18 where he has perhaps 150,000 laborers who build the Temple and Palace. These men work in shifts. These men are spread around geographically, including in Lebanon. They are building public works for Solomon. In times of war they would be used to fight external battles.

We see massive public works throughout all places with a capitalist financial system. Egypt is always the envy of outsiders. See all the great works? Why don't we have those in our country? The true cost of all of these things, of course, is debt slavery.

Trump's government just approved a similar levy, now called a draft, in order to eventually conscript an army to fight Russia.

Financial systems always need new assets, or their titles, going into the vault. Russia's assets are needed to keep the scheme running. China's assets will be needed too. Iran's assets will be needed as well. This is also why colonizing Mars is so important. Once all of earth's assets are under banker control, then comes Mars.

Capitalist systems are fundamentally unstable because the vault eventually goes empty. There is no more real wealth to settle all debts owed. In US history the current capitalist system began in 1913 when the European central banking family established the US Federal Reserve. This triggered the depression of the 1930s as most wealth had been taken from families in the inflation of the 1920s itself caused by the Federal Reserve Act of 1913.

A similar wave began in 1971 when the US Dollar lost convertability to gold. There was not enough gold in the vault to satisfy all foreign held claim checks. Oil was soon substituted. "Spices" as per the list above. The fight with Iran holds the threat of ending oil as the reserve asset for the USD, which is in part why Iran is such a mortal threat to the west.

#2 Ahab/Jezebel: Lawfare

Ahab and Jezebel are the next villains in our list of editors. Ahab is a northern king and he marries a foreign wife, Jezebel, who brings in Baal worship. (Baal is a word commonly translated as lord.) You can pick up their sorry story at 1 Kings 16:31.

This husband and wife pair has what seems like continuous trouble with true prophets of Joshua. Obadiah, a prophet in his own right, hides groups of prophets in caves. Elijah is found running for his life from these 2. The prophet Micah will eventually attempt to preserve Ahab's life, but is unsuccessful. In many ways Ahab and Jezebel are ultimately fighting against the question of what did god really say? Their life patterns are similar to Adam and Eve in the garden.

But the highlight of this story is the procedure that Ahab and Jezebel use to get Naboth killed. This story begins at 1 Kings 21. Ahab wants Naboth's land, but Naboth refuses to sell.

In previous blogs I have suggested this was the historical location for the vinegar, so the fuser, used for the ink for making copies of inspired scripture. Naboth had good reason for not wanting to let go of that land. It had 600+ years of important scroll making history.

Not only did Ahab and Jezebel not like the spoken words of prophets, they did not like the systems of writing that the prophets used to keep the inspired word of Joshua. They did not like even the source of the main ingredient in ink.

So once Naboth rejects Ahab's offer, Jezebel steps in. She sends a letter in Ahab's name to some secret group who have the power to put on a false trial. That group carries out Jezebel's orders and eventually they stone Naboth.

So who was the group that could answer Jezebel's letter?

The answer is given in the text. They share the same religion as Jezebel. They are the local "Baal worshipers."

What do we call those mostly secret Baal worshiping groups now? These are generally called Kabbalah based religions. The gentile version is called the Masonic Lodge, or just Lodge for short. There is also a Jewish version. Modern American Protestantism, especially certain denominations that spring from the colonial era, are thought to be heavily influenced by this system.

These groups control most of the machinery of the American government. This includes most branches of government, including and especially the courts. This also drives various professions that go along with government, like law and the military.

The story of Jezebel's use of a crooked court is marking how the court system is the most important place for exercising their secret type of public power and control. The legal system is also the ultimate party responsible for the more mundane aspects of modern government, like counting votes. It has been rightfully said, it doesn't matter who votes, but who counts the votes.

The mechanisms of modern lawfare are broad. Joshua himself ended up in such a system at the crucifixion. Many, many others have run into this across history. Ahab and Jezebel are an ultimate scriptural archetype.

#3 Nebuchadnezzar: Hegemony

The next editor in our list is Nebuchadnezzar. He shows up in the story near the end of the line of kings at Jerusalem. You can read it for yourself starting at 2 Kings 24. You can find more details of the inner workings of this villain in the Book of Daniel.

Nebuchadnezzar uses his army to first demand tribute from Jerusalem. After 3 years, that tribute is not paid. The problem? Nebuchadnezzar has a big army. He knows how to use it. He returns and eventually conquers the city and burns it down. He hauls nearly everyone away as slaves to Babylon.

Normally, the nation with the largest army will win a battle. Of course there are exceptions. Geography, skill and divine will sometimes upset the normal patterns. Given enough time, and enough skill, eventually some kingdom, and some army, should be expected to rule the entire world. World dominion is the ultimate goal.

The modern technical term for this pattern is called "Hegemony." It covers both the military patterns of conquest but also the process of getting local rulers to agree to be subject to the greater power. This is what Nebuchadnezzar was trying to setup when he first came to Jerusalem. He wanted the Jerusalem king to be part of the larger kingdom. Nebuchadnezzar was attempting to use his army as a threat.

The patterns of Nebuchadnezzar's hegemony continue all the way to this day. It is ultimately a long term series of fights to determine who rules the entire world.

Hegemony Examples

For current examples, Trump is the Hegemon, so Nebuchadnezzar, against Venezuela, Cuba and Greenland. He has threatened war against Canada. This is regional Hegemony. But the USA is itself a vassal of a larger and older Hegemon. Ultimately the current planetary Hegemon is the 8 or so Jewish families that control the central banking cartel. Catherine Austin Fits recently stated that group of families currently control over 90 percent of all of earth's wealth.

If you have a home mortgage, car loan, student debt or an unpaid credit card balance, then you are part of that 90 percent of earth that is controlled by these 8 families.

All wars against Russia, since Napoleon, have been attempts to bring Russia under this same Jewish family hegemony. Putin's actions are constrained by his Jewish oligarchs, but generally speaking Russia remains outside of that control.

The current war against Iran is yet another example. Iran's oil trade is sanctioned because it does not settle through Zionist banks. Iran's government does not have a Zionist puppet like Trump. The history in Iran for the past 120 or so years is best understood as attempts to bring Iran under Zionist Hegemony. Trump's decapitation strikes and Trump's current blockade are attempts similar to Nebuchadnezzar's war against ancient Jerusalem.

Iran appears to be the ultimate exception to the pattern of Jewish Planetary Hegemony. Revelation 9 appears to explain that exception.

Hegemony Goals

For background, the capstone stories for this world conquering goal start at Ezekiel 43. This is one of the dusty corners of the text. That chapter itself probably has an inspired vision of either the room where exhibits are kept or else a room in Eden. If this is an Eden vision, it matters once the tech exists for reaching Eden. Chemical rockets are probably not good enough.

Starting at Ezekiel 44 and running through the end of the book is a large passage that purports to describe the floor plan for a planetary capital. This is almost certainly an addition. Likely added by Ezra.

This is contradictory to the stories from Samuel's day. Joshua was already king. Asking for a king was a national sin. There has never been any particular reason for an earth based capital building. But, this story does drive the goal for world Hegemony.

The book of Daniel, starting at Daniel 2:34, spells out the end to the goal of building a kingdom over the earth. A stone will strike this statue, this vision, and undo it. The stone, of course, is symbolic of the inspired text. Somehow it prevents planetary Hegemony. Presumably Russia, China and Iran, which want a multi-polar world order, will ultimately get something along the lines of their thinking.

#4 Mordecai: Blackmail

The next editor is Mordecai. His story is the main topic in the Book of Esther. That book is all about Mordecai's successful attempts to pimp for the king and get Esther installed as queen.

This simple explanation also includes a bunch of palace intrigue. Much of Esther contains details about how that intrigue worked in Esther's day. This included palace banquets and the rivalries between various powerful families.

Ultimately, the king ends up going along with the desires of Mordecai. In that example there is less threat than we see in the Epstein files. Presumably certain clients enjoy going along with the crime. It looks like Trump might fall into that category.

The purpose, of course, is to provide wealth and power to the Jews. As I have explained in previous blogs, these are Jebusites who replace Benjamin. Benjamin ends up outside of the tribal promises.

Esther is also a story that creates holidays that are NOT part of the inspired set. Presumably all secular holidays come from this same tradition. The 4th of July holiday in the USA is said to have been selected for Masonic reasons. The founding documents of the USA were not officially signed until later in 1776.

The 2 holidays called out in Esther are not the final 2 inspired holidays. Note the text really wants 1 holiday per tribe, so 12 such holidays across a calendar year. There are 10 earlier holidays. The remaining 2 holidays come from the New Testament. Joshua's birth and crucifixion give rise to the final inspired 2 holidays.

Today, we know the Mordecai process of gaining and keeping power as the work of the Epstein Class. We have only had this vocabulary word for a few years. The general public is only now accepting this pattern of control as being real. The same patterns of sexual blackmail from the text still run in the world today. Nothing has changed.

#5 Ezra: State Religions

Ezra is commissioned by Cyrus the king in order to setup the priestly system at a rebuilt temple in Jerusalem. Ezra's commissioning letter is given starting at Ezra 7:11.

It is very important to note that no such system was needed for around 1000 years between the Exodus and Ezra. This was not needed across the time of Judges. It was not needed by the community of prophets who survived during the time of the kings. The system that Moses had set up, called David's fallen tent in Amos and Acts 15, was better than Ezra.

Ezra was only needed because the king needed a state religion. Truth was now to be imposed. Truth was no longer self evident. This was the last of the Old Testament editors. He was imposing a false text on an unsuspecting public.

State religions have continued since Ezra's day. They provide some level of national cohesion. A state religion allows the public to reason about spiritual issues in some sort of consistent way. This problem exists because the inspired text is not currently known.

Though there are many different state religions around the world, the most common follows as natural heirs to Ezra himself.

The hegemonic governments of the western world all follow some variation on the system setup by Ezra. This would include all the secret and twisted stuff of Solomon, Jezebel, Nebuchadnezzar and Mordecai. It even reaches into modern Christianity.

I recently read about how Thomas Jefferson rejected Christianity as a state religion in the USA. He wanted a stronger, elite, religion that would be shared by members of the Federal Government. He got his desire. We know it as Masonry, the gentile version of a Kabbalah based religion. This is why members of government do not listen to Christian arguments from the public. They have a certain conceit against those who are not in the club.

#6 Ananias: Narrative Formation

The final editor on this list is Ananias. This editor goes off and twists the New Testament narrative. He does this mostly by story duplication while at the same time adjusting various details. This process forms a contradictory narrative. This process forms a narrative which seems to follow the edited Old Testament. It obscures otherwise obvious truths.

The common technical term for Ananias' work appears to be "Narrative Formation." This process works everywhere in the modern world. It takes a given set of facts and twists them around for whatever the day's political purposes might be. It is a process of hiding profound truths that are then intentionally hidden from the public.

This same process is used to cover over criminal behavior by people in power. Ananias was covering the crimes committed against Joshua by other members of Ananias' own family.

Trump himself has many mental faults, but he is particularly good at narrative formation. He is always spinning up what he is saying in order to create a narrative that will distract key details from public understanding.

The modern heirs of Ananias are the main stream media figure heads and well paid social media influencers. Each take basic facts and twist them to their otherwise hidden agenda.

How Long?

This list matches the 6 manuscript villains to 6 areas of power in our modern world. The modern heirs of these villains still run wild in the world.

When will Joshua raise up and end this system of villains?

There are perhaps another few years before the worst of this is over. Each villain appears to have hints about their downfall.

In Solomon's case, David's fallen tent needs to be restored. (Amos 9:11)

Jezebel's case, her time to repent must come to an end. (Revelation 2:18)

In Nebuchadnezzar's case, the stone must strike the great statue. (Daniel 2)

In Mordecai's case, Purim must be reversed. (Esther 9).

In Ezra's case, his temple must fall. (Matthew 24:2)

In Ananias' case, teachers of the inspired gospel must arise. (Mark 6:7)

Match Dates

This week we were watching for the replay of the year of Jehoshaphat's reign on Monday, 2026-05-18 and then the first year of Jehoram's reign on the following day, 2026-05-19.

The most significant headlines appeared to come from Russia's president Putin's visit to China and a summit with Chinese president Xi. This had followed Trump's previous visit to China. But this Putin/Xi summit was on the prophetic date and much more substantive in terms of their engagement and agreements.

Putin Arrives China

Joint Statement

The top link is to an arrival photo establishing the date. Near the end of the summit, Putin and Xi issued a joint statement. The second link here provides a list of points from that joint statement. I have assigned numbers according to the order in the second link and then bunch them into topics in a list below.

These 2 leaders, perhaps more than any others, are the bulwark against the Hegemony of Zionism that has been building since the days of Solomon. Iran is on their side too, but Iran is more isolated than Russia and China.

We are probably looking at the general fault lines for World War III. Russia, China and Iran on one side, the Zionist west on the other.

Putin and Xi are viewing the world from the perspective of the time BEFORE the heirs of Jacob asked for a king. The Zionists appear to be in more trouble before Joshua than Russia and China. Iran seems to have its own favor from Joshua for some future events.

You scan see in the points below how they are working against world Hegemony. They view the alternative as "multi-polarity." The tribes after Moses' time were a multi-polar community. In some sense the world is about to "leave Egypt" and when that happens, the tribal patterns of Moses come back into play.

Points Against Zionism

1) Warned against a return to the “law of the jungle” in global affairs.

2) Stated that there are no “first-class” countries or nations and that hegemony in any form is unacceptable.

3) Opposed forcing sovereign states to abandon neutrality.

4) Stated that all sovereign states have an equal right to security.

6) Are against using human rights as a pretext for interference in the internal affairs of states.

7) Expressed concern over the militarization policies of the United States and its allies.

8) Opposed actions violating the UN Charter in Latin America and the Caribbean.

17) Opposed a return to a world order governed solely by force and defended the authority of the United Nations in international affairs.

16) Expressed concern over confrontational rhetoric from certain countries and called for an end to interference in internal affairs.

19) Described attempts by “certain states” to restrict maritime shipping as a threat to global trade.

20) Are against unilateral sanctions and the discriminatory use of tariffs.

21) Called immunity for heads of state from criminal prosecution a guarantee of stable international relations.

22) Opposed any unilateral sanctions not approved by the UN Security Council.

23) Condemned initiatives involving the blocking, seizure, or confiscation of assets and property belonging to foreign states.

Points On Ukraine

5) Believe it is necessary to address the root causes of the Ukrainian crisis.

Points On Iran/Israel

10) Supported Syria’s sovereignty and territorial integrity while urging the new government to combat terrorism.

11) Stated that US and Israeli strikes on Iran are illegal and undermine stability in the Middle East.

Points On Other Countries

9) Supported Africa’s independence and sovereign development.

12) Are against pressure on North Korea.

14) Described Japan’s accelerated remilitarization course as a threat to peace.

15) Stated that NATO’s presence in the Asia-Pacific region is incompatible with strengthening peace.

Points On Technology

13) Will ensure interoperability between the GLONASS and BeiDou navigation systems.

18) Will deepen cooperation in thermonuclear fusion and fast-neutron reactor technologies.

Notes On Iran

This past week the Iran war remained in a cease fire. There were rumors that there was negotiations going on. Iran did not appear to be standing down on their demands to end the conflict.

Various reasons have been given for why Trump has not restarted. Perhaps the most reasonable was a request by Saudi Arabia to wait until the annual Hajj is over. The Saudis are hosting perhaps 2,000,000 guests. They want the war to remain suspended until those guests are safely out of the country.

Watch Dates

Our next watch date is Tuesday, 2026-05-27, the replay of the last year of Jehoram's reign. This will begin one of the strangest times in the reigns of the kings.

The following day, Wednesday, 2026-05-28, is the replay of the year of Ahaziah's reign. This king was killed by Jehu who had gone on a killing spree. Jehu killed the kings from both the northern and southern kingdoms, including Jezebel, Ahab's family and Ahaziah's relatives in the south.

The next day, so for us Thursday, 2026-05-29, is the replay of the start of Athaliah's reign. She was an evil queen who reigned for 6 years. So for us, her reign will end on Wednesday 2026-06-03. During her reign the future king, Josiah was kept in hiding in the temple.

Previous Headlines

Note this series of stories replayed in April of 2002. The main headline was a siege at the Church of the Nativity in Bethlehem. The IDF was chasing Palestinians who took refuge in the church. Think trapped like the young Joash. That church would remain under siege by the IDF from April 2 until May 10, 2002. So that prophetic replay ran longer than the simple expected 6 day story.

Also curious to note from the 2002 replay, the Queen Mother (in the UK) was buried at the replay of the end of evil queen Athaliah's reign.

Note that we are approaching a temple rebuilding story from 2 Kings 12:6 that replayed in 2002 near the end of the Bethlehem church siege. (That church needed attention, it had been shot up.) This time around we are more interested in temple mount as a possible venue for these stories.

Siege of the Church of the Nativity

The link here is to the Wikipedia article that details the events surrounding that 2002 siege. The IDF had occupied Bethlehem. Some Palestinians fled into the church. That article contains the day-by-day details. Note how the IDF are the villains. The Palestinians are the good Joash.

Shop Work

This week Ryan and I were both working on our laptops. Ryan was booting up new hardware with PopOS 24.04 and copying files over from his old machine.

I also took the plunge and updated my laptop to PopOS 24.04. This was quicker because I did an in place update to a system that was already mostly setup and running.

Reinstalling apps is always a good time to survey the state of our projects. Ryan has been fixing up a bunch of issues across our various projects. He has been reorganizing our git code repositories. Basically a spring cleaning that we usually do every 2 years, but skipped 2 years ago.

Ryan found a bunch of issues that he fixed while working through our list of projects. The biggest fix is to the app names used on install.

Default App Names

As Ryan's setup was completely new, he went through and did a rebuild for all of our apps and websites. Several of them had issues related to the installed name of the apps.

By default, most browsers take the title of the front page of the app as the name for the app itself when installed. That behavior makes sense for websites with a home page of some sort. In some our our apps, that default behavior leads to strange installed app names like "Front Page." Those strange cases have been fixed.

Style System

We began building web apps many years ago when the style system used on web pages was pretty primitive. At that time we starting using a tool called SASS for managing style sheets. This system builds the style sheets used to drive the user interface in all of our apps and websites.

Perhaps the main feature of SASS is the ability to break down the style system into a bunch of smaller files. This allows styling by composing the styles kept in separate files for various parts of the app.

So we are now seeing the current version of SASS throwing a warning. That main feature is now getting a deprecation warning. This means they intend to remove that most fundamental of all features. (Whomever is behind that app is brain dead. Like taking the ++ operator out of C++.)

Since it still runs, this is not a critical bug, but it will stop working at some point in the future. As CSS itself has substantially improved, I took a to-do to adjust our current build environment to handle that CSS file bundling process directly. We already do nearly the same thing with HTML.

Story Grid App

This week Ryan has also gone through the Story Grid app and removed a bunch of old styling related files that worked against old versions of that app. Before the current grid was worked out there was a series of other table forms. Those other table forms had various styling needs. Those files have been removed, so the app only contains the files needed for our current understanding of the story grid. The major version number was also adjusted this week.

Paleo Bible Work

My other task this week was to work on software for the Paleo Bible app. This week was mostly back end work. The process itself takes texts that start as Aramaic which then go through a series of conversion steps to become audited Paleo.

I have been experimenting with file formats and the conversion steps needed to move from the inbound files to the forms which will be seen in a new Paleo Bible app.

Last week I was looking at formats that are based around long single lists of words. This format gets rid of the irregular structures implied by modern chapter and verse breaks. The texts never had that addressing system when they were written. They are modern additions.

As the audit code is eventually looking at the text as a long string of words, it makes sense to switch to an internal format that is just a list of words.

I can now see, from several examples, that this format makes movement through those lists very, very easy to code. This format also makes each step in the conversion process much more easy to inspect and audit.

This week I adjusted the way those files carry around address information. Modern address data is needed for putting each word from those word lists back into a formatted shell ready for use in the Paleo Bible app itself. So I cannot drop address data entirely. The trick is where to keep it.

A week ago I was looking at parallel address data as an "out of band" problem. The address data was carried in a different structure than the list of words. But one step in the pipeline expands the list of words. That expansion needs to be reflected in the address data. This creates a book keeping problem.

This week the code was rewritten to carry the address along with the words themselves. This eliminates any chance of the word list and address list going out of sync. It also allows an immediate human debugging connection back into the word address system of the full manuscripts.

Adjusting The Address System, Again

I also worked through the conceptual problem of word fragments. The inbound files have whole Aramaic words. These get broken down into smaller parts. This happens in an early conversion step which creates even more lists of words.

For an example, an inbound Aramaic word, say Du-Wa-Ba-Re-Fe-Mo is ultimately 2 words. Du, then Wa-Ba-Re-Fe-Mo. There is an issue of punctuation after the Du. There is an audit issue at the sentence level about if Du belongs. Then there is the name Abraham which has its own audit punctuation issues. Each word has different English interlinear data. Each word goes to a different place in the lexicon.

The word address markup in the app will mark the whole original historical inbound words. But internally, it needs yet another layer down in terms of word addressing. This ultimately leads to a 6 level address system for any given word.

So a full cite is something formatted like Genesis 2:3d~5e. This means the 1) The book of Genesis, 2) chapter 2, 3) verse 3, 4) subverse d, 5) word 5, 6) word fragment e. Internally, the short hand is 1.2.3.4.5.6.

In reviewing this, Ryan commented that the letter within the word naturally falls as an additional 7th level of address. Curious.

As inbound historical words get broken up, the address system also changes. This change keeps the inbound address but gains more precision for use in the output side of the conversion pipeline.

Tricky stuff, but progress is happening nearly every day. More later.

Headline Review

Massie's loss of his seat in Congress is what triggered the subject for this week's blog. As I was reading about that election, I kept wondering, what system of Zionist behavior was used against him?

Let me start this headline review by looking at the Massie election and what scripture informs what was going on.

Massie in 2028?

Problem of Turnout and Percentages

Mike Adams on Massie

The top link is to a post on Telegram with a clip of the crowds chanting for a Massie run for President in 2028. The second link highlights problems with turnout and vote percentages. The third post is a comment by Mike Adams that there is no way to vote out of this problem. Many similar posts like these were all over social media at the start of the week.

Massie was calling for the release of the Epstein files, so he was exposing the patterns of #5, Mordecai. But, Massie himself was more like a victim of a theoretical Mordecai, which is of course the world of palace intrigue. So there is some sense of a match to #5. In Esther, as passed by history, Mordecai's opponent appears to be evil. That does not appear to be the pattern here.

But, someone still wanted Massie out of Congress. (Or worse. That "someone" may not be done with Massie. There may be more trouble coming for him.) So, this case is more like villain #2, Ahab/Jezebel. The voting system is a legal system, so it is like a court. This is a broader sense of the story of Naboth.

But just how Massie was removed is also not clear. Some say his seat was bought by Jewish money. This version of the story is told in the sense of buying media in Kentucky. But, there were apparently more ballots cast than registered voters. So turnout for this primary was over 100 percent. This is not a national, money, media, issue, but a local ballot stuffing, voting machine, fraud issue.

So was this election lost because someone like Jezebel, in Ahab's authority, sent a letter to Kentucky to have Massie removed? Did they take his vineyard? Just like Naboth? Looks like it. Yes.

There was also Narrative Formation going on around this case. So #6, Ananias. The media narrative was that money had purchased Massie's seat. This story draws the public's attention away from the real crime. This is just like Ananias' editing of the New Testament. We have been told 1 story, when something else was really going on.

The Narrative Formation side of this story has only been picked up by a few commentators. Mike Adams' post above is an example. If the problem is not purchasing media, but messing with voting procedures then Trump and his team control the voting machinery across the USA. He has no risk of trouble, either in the fall elections later this year, nor in 2028.

So nothing Trump does against Iran will impact the results of upcoming elections. No amount of inflation or oil shortages that he may cause will have any impact on elections either. No amount of criminal behavior will cause the voting public to remove him or his people.

Large Blast In Israel

Better Video

Saturday, May 16, 2026, saw a very large blast at a weapons factory west of Jerusalem in Israel. This may have contributed to delays in strikes against Iran. This was likely a materials handling accident that ignited either bombs or rocket motors made and/or stored at that location. The blast was so large many wondered if we were looking at a suitcase nuke level blast. This was late on the Jewish Sabbath. Workers there may have been preparing weapons for use against Iran. They would normally have no reason to be doing anything at this time of the week.

Strike in UAE

UAE MOD Statement

On Sunday, May 17, 2026, there was a strike by a drone on part of the equipment at a nuclear plant in the UAE. It was immediately called out as from the west, so not from Iran. Later it was said to be from Iraq. Headlines like this do not fit established narratives. It suggests a false flag intended to blame Iran. Links above carry some details.

1500 Drones to Moscow

The pace of the Zionist war against Russia is also increasing. This Military Summary video on Youtube gives some numbers. There have been many warnings from various Russians that NATO is behind these attacks. These warnings also warn this eventually leads to a nuclear retaliation against targets in central and western Europe.

Naphtali Bennett

This is a link to a post on Telegram that shows betting markets suggesting Naphtali Bennett might win in an election against Netanyahu. This is a possible replacement for Netanyahu. Note the pharaoh look.

Athens Ankara Flashpoint

Greece Turkey

Legal Details

The Paisios prophetic warnings about war between Greece and Turkey said we should watch for disputes over the territorial boundaries in the water.

The top link here is to a long article on RT with many of the details. The next link is to an article on The Cradle summarizing recent trouble out of Turkey on this point.

In history, the Turks took Greek territory, but not the Greek islands. So they never conquered territory at sea. Now they are looking for more. The third link has a sea map with more of the legal details.

Paisios' prophetic expects Haggai Sophia to be returned to Greece, but only after Russia's help.

Plague of Gnats

This link is to a post by Alex Jones on X detailing ticks and mosquitoes released in the USA are part of a Gates funded bio weapons program. This is a nearly perfect match to a plague of gnats. Unclear if this is good prophetic timing. Reports like this have been on social media for weeks.

Solar Factories

This link is to a Youtube video by the Electric Viking. He is detailing the scale of the Tesla and SpaceX factories that are being built for making solar panels. Huge. Musk gets the end of fossil fuels. He also needs solar for space based AI.

Trump and sons exempt Forever

Trump Exempt Forever

Trump and his sons have been granted permanent immunity from audits by the IRS. This looks to me as planned. This may be why he was even litigated in the first place. The link here is for the record. The USA now has a royal family.

More Later,

Phil

Story Grid

Phil Stone — Fri, 15 May 2026 19:35:37 GMT

This blog covers more alternative story reading orders added this week to the Story Grid app. For our technical readers, there are notes on various problems of manuscript recovery. Also included this week are Qu-Map notes for a major prophetic land purchase in Louisiana by SpaceX. Finally, watch dates, shop work, war status and a headline review.

Story Grid

The link here is to the Story Grid app. The permanent link is off the front page at Paleo.In. In last week's blog I introduced a new set of pop ups which deal with alternative reading orders for stories along the rows and columns of this app. These alternative story reading orders are following the Vine and River pairing systems of the alphabet itself. Sabbath Reads, which has its own app, are alternatives that read down through the columns.

As a theoretical concept, these alternative reading orders appear to be how the inspired text does not need tooling like we see in modern Study Bibles. Alternative reads bring stories together in ways that naturally provide interpretive context without the need for an expert to force some interpretation.

Diagonal Reads

So what has been added to the Story Grid app this week are a series of pop ups that provide alternative story reading orders that work along the diagonals of the overall Story Grid itself.

Because of the way the Story Grid app is constructed, these alternative reads appear within the new set of pop ups that I introduced last week. So what is happening this week is an expansion of the set of alternative reads. This time, the new reads are along the diagonals of the Story Grid itself.

These new diagonal reads are the most speculative set of otherwise rigorous reading orders that are possible given the basic geometry of the main grid itself. These have been added in order to study how useful diagonal reads might be. Remember, of course, that as of this week the entire grid itself has not yet been fully determined. So this is an ongoing study.

The purpose of diagonal reads is to take lists of stories that are found along the diagonals as found in the Story Grid app. Negative Diagonals go down when moving to the right across the table. Positive diagonals go up when moving to the right across the table.

The 2 most interesting diagonals are the center diagonals. The center negative diagonal moves from the top left to the bottom right. The center positive diagonal moves from the bottom left to the top right. Neither of these diagonals has any wrapping.

Once off the center diagonals, the other diagonals all wrap the table in some way. Conceptually, these diagonal wraps are done as though the Story Grid was rolled. You can study the story numbers in the various reading order lists in the app to see the specifics.

Finding the Diagonal Data

Ryan went through several rounds of experiments this past week in order to find a nice place to put the launch buttons for finding diagonal read data.

In the end, the links to this function are tucked into the Column and Row reading order pop ups already in the app. The pop ups along the top header now include a link for opening negative diagonal related data. The pop ups in the left headers now include links for the positive diagonal related data.

I would recommend playing with the app to see how this works.

Ryan is perhaps the most important user of these various alternative reads. He is using these to help establish the correct set of inspired stories and their correct placement. The center of the Story Grid is perhaps the most difficult area to solve because it is less constrained than the edges.

History

This app has been undergoing changes in the shape of the grid for many years. Originally, we had no idea how many stories there might be, nor what the arrangement of stories might be. While we were working out what the shape might be, that app included alternative grid layouts in order to study the question better.

About a year and a half ago we settled on the 25x25 grid size that you see now in that app. This overall size is remarkably compelling because it causes the alphabet to inform the total number of stories. It allows 3d related design features of the alphabet to inform what is going on across the table. This informs both rows and columns of the table, which is very nice.

At this point we are attempting to find all the ways this story grid might be useful to readers of the inspired text. Alternative reading orders along the major axis of this table appear to be quite useful.

Use of the new diagonal reading orders will ultimately determine if these are also useful to readers of the Testimony. It will become more clear once the final story placement is settled.

Paleo Bible Work

This past week I finally started turning my attention to the manuscript side of the upcoming Paleo Bible app. I am still not sure when this will go live. The basic recovery work flow still needs to be worked out in detail. That work flow is where my attention is currently focused. For the record, I want to share some of what I am learning.

Let me start by saying this is a problem that has been in front of us for a long time. I have started down various parts of the recovery work several times over the past 17 years. This week I have been reviewing our vault of old git projects in order to understand failed attempts at various parts of this problem.

Perhaps the first step we ever took at recovery was working out the Paleo Keyboard layout and related configuration files that we use whenever we need to type Paleo letters. A week ago, when setting up that keyboard on our new PopOS 24.04, I noted those files are dated from 2009. So this has been a long term project.

There are various phases to the recovery work. Let me list those here. Some of these have been tried various times. Some are new.

Inbound Manuscripts

The world of Bible manuscripts is a haphazard mess. Ultimately the texts that matter to us were published in the 1800s. Bible manuscripts must be found and converted into a format that we can use. The NT and OT texts are usually in different sources and normally not in the same file formats.

So we don't go crazy, we have our own custom file format for Bible manuscripts.

At some point years ago we found 1 particular downloadable Bible with a very dense style of markup that we particularly liked. We redefined that format for our own use, but are still keeping the general dense markup approach.

We occasionally add new markup to track new needs from Ryan's ongoing work. Our build environment is now highly configurable and generally knows how to convert that format to HTML for use on web pages. Most new markup just needs HTML fragments added into a specific configuration file in order to know what HTML to use for any given new Bible markup feature.

All of our inbound Bible related files start with conversion into this format. Texts which need advanced formatting features, like the BRB, can then be edited as needed. All of this inbound conversion work is essentially done. We only drop to the format conversion level when we find a new manuscript.

That file format has suited us well for many years. But, this week, I finally gave up on that format for audit work. I have started experimenting with an alternative.

Audit and recovery work needs to view the inbound text as a simple list of words. That is all. Chapter and word breaks as found in all conventional markup just gets in the way. Let me explain.

Tool Chain

Our inbound files are still in our conventional format. Our outbound files must also be in that format. This format gives us access to a huge range of formatting features that are possible in the future Paleo Bible app itself.

But, between the inbound text and the outbound text we need a simple word list format that is easy for code to scan and change as needed through the various steps in the recovery process.

Rethinking File Formats

For a long time I have only used Javascript as a programming language and .json files for data storage. Our apps run in web browsers and this is the natural language for that environment. Our new build environment is in that same language, running on nodejs for those who may care. Passing data around the build steps is easy. Passing data from the build environment to the runtime is also very easy.

In some of the tooling I recently rebuilt for Ryan I started using .json equivalent .js files. This is basically a commented and editable form of .json data but stored in a .js file. Code using these files sees the inbound file as though it were .json data. Since it is a .js file, it is easily handled by text editors which handle syntax highlighting.

Importantly, .js files support comments. So the raw data can be decorated with whatever is needed for human inspection and when needed, human editing. .js files also generate useful error messages if they are human edited and a mistake is made.

These files are also easily saved under revision control, which is good. This general format is basically a simple hierarchical data base file format. This is without the cruft and intellectual overhead of an actual database manager, which is also very nice.

These files are capable of containing code. But, as a convention, we don't put code into these special files. For reference, The Story Grid app's map of stories is built around this format. Ryan regularly uses tools in his text editor to change the layout of the story grid itself. This is not hard. It is easy to understand. Though Ryan is editing .js files, he does not need to know how to code.

Bible Books Into Javascript

So I did some tests this week on extracting raw word lists for those 92 books into this strange .json equivalent .js file format. This converts the Bible text with complex chapter/verse/word addressing into a single long word list. This is the format needed for creating an English interlinear then for audit and then for recovery.

This format is fully commented with address data, so a human can open the file and know exactly where in the Bible any given word is actually located. But, as far a software is concerned, this starts as a simple long list of words.

This format saves all addressing in a separate place in order to know how to restore those word lists back into the highly formatted version for display in the Paleo Bible app at the end of the audit process.

But what matters most, what I saw this week, is how easy it is to load and use Paleo word lists in this format. With only 1 simple load, running at the parser speed of nodejs, the entire Bible becomes immediately available in memory. This is as word lists, ready for whatever task may then be needed.

The final step in this new tool chain is to insert the corrected word lists back into the files that are formatted with all the markup used for presenting Bibles on screen in the apps. The final Paleo Bible app is then technically able to display the same rich coloring and annotation as found in the BRB.

In playing with files in this format this week I saw more changes that are needed. The system needs to track sub-words in order for inbound Paleo words to become more than 1 word on the outbound side. There is an another question about tracking punctuation as a type of sub-word. More testing is needed for this.

I still need to write the code that inserts these word lists back into the outbound files. This does not look all that hard to do. More on this in future blogs.

With simple word lists available for quick loading, it was also possible to play with that format. I wrote some simple apps that can summarize the inbound word lists themselves. Here are some of the data I found this week.

Manuscript Stats

We have a 92 book canon that forms the base text for the Paleo Bible. These books include the 66 books of the standard Protestant canon. Then we add many more books. Basically everything we could find in Aramaic that was included in someone's Bible. It also had to be printed in the 1800s and must now be out of copyright.

This working canon includes Intertestamental works, Additions to Daniel, the Maccabean Revolt, more for Ezra, Manasseh and Psalms. Finally there are a group of books from Early Christianity.

This is the largest set of books we have looked at in terms of recovery. For most of these books we have at least one English to Aramaic interlinear. So we have the resources we need to figure out the English translation for most of the vocabulary words used in the text as passed by history.

So here are some basic stats. Across those 92 books are 536,014 individual inbound Paleo words. I am using a Layer 3 definition, so units of Aramaic grammar. Out of this inbound string of words are 50,907 unique words. These 50,907 words are the inbound data for the lexicon related tooling I am currently planning.

For comparison, a full KJV bible has a little under 15,000 unique words. Of course our canon is a little bigger, so this is not a perfect comparison. But this difference between 15K words in KJV vs. 51K in raw Paleo is mostly the grammatical grouping in Aramaic as compared to English.

We know from the Shepherd's staff work that prefix letters in perfect Paleo always become stand alone single letter words. So this 51K count of unique words will go way down once we have worked out the Lexicon data.

Planning

I have been reviewing the code from past attempts at cracking this riddle to see what, if anything, I could salvage. All I really learned from this review is what not to try again.

It is clear that in past attempts I was mostly worried about getting this problem solved quickly. This was because for years we were running out of money, so time mattered. But "quickly" is not a way to also learn a recovered language. Working quickly is sometimes called the "tyranny of the urgent." It is a trap.

Now that we ran out of money, we find we are still here. Still working. So running out of money didn't really matter.

So now, we are most interested in getting the recovery problem solved as ACCURATELY as possible. We don't really care how long it takes. Ultimately, we still want to be as efficient as possible. If we can stay efficient, then the time it takes is not a real concern.

So, I am being slow when thinking about this code to make sure I have a good recovery plan.

Magic Stats

To crack each of those 536,014 inbound words requires an entry in a lexicon. That lexicon needs to explain what to do with each of 50,907 unique words.

I ran another stat. There are 1379 unique words that occur at least 50 times in the inbound text. Of those, Mo-Ne, the standalone word for "from," is the most common. Mo-Ne has 11,521 copies in the inbound manuscript. Next up is Oo-Lu. This is Paleo for "on" or "upon." This word has 6,234 copies in the inbound manuscript. See the magic?

If we started by loading a new lexicon with those 1379 most common unique words, then the Lexicon could explain what to do with 332,901 of the words from that inbound stream of 536,901 words.

For 1379/50,907 or 2.7% of the work, the lexicon will cover 332,901/536,014 = 62.1% of the inbound text. Magic indeed. I have never been this clever before.

More Magic

Looking more carefully at this problem I could see a few other things going on. Let me start with Abraham. 146 times it is just the stand alone name. Wa-Ba-Re-Fe-Mo, as we expect. 71 times it is a Du then Abraham. So in English usually "of Abraham." 67 times it is Lu then Abraham. So "to Abraham" in English. The other forms are "In Abraham," "And Abraham," "And To Abraham" and then a strange case from the Prayer of Manasseh 8:2 where we find "Who To Abraham."

So 3 of these Abraham entries are over 50 times. So these would be caught in our net for hitting all words which occur above 50 times.

But by adding all 7 entries for Abraham into the lexicon at the same time, we would fully handle all occurrences of Abraham. Not hard. A text editor with reasonable file formats makes this quick and easy.

Let me take the name Joshua. This name has 15 different forms in the inbound string of words. So by hitting 15 entries, the name Joshua is covered across the entire manuscript. 1033 times we find stand alone Joshua. 140 times we find "Of Joshua." 116 times we find "To Joshua." 41 times "In Joshua." 37 times "And Joshua." 14 times "Who In Joshua." (These start at Romans 8:2 and may be in a question.) The other entries are minor, but still very easy to enter into a lexicon using a text editor.

In a few of those forms the name Joshua is buried as part of a more complex name. Joshua is buried in "Abishua" in 1 Chronicles 4-5. (This is a contraction of Father and Joshua. Chronicles is not likely inspired.)

Joshua is also buried in "Melchi Shua." See 1 Samuel 14:49 and 1 Samuel 21:2 for examples. This comes in as a single word, without a word break. So the English translation is hiding how that name is a contraction of "King" and "Joshua."

If Ryan and/or I were actually working these problems, this strange word would cause a stop for conversation.

Should the interlinear in the Paleo Bible read this as the contraction "King-Joshua" in English? Anyone who could read the Paleo would easily see this name as spelled exactly this way. Should we let English readers see it this way too?

There is much work ahead which is full of discovery and trouble. We are about to see through centuries of fraud by scribes who were trying to hide details of the text from generations of readers. They wanted a secret keeping priesthood. They did not want real readers.

Whatever the correct handling of these other forms of "Joshua" might be, our lexicon can be easily updated later if we had a better understanding of how to handle the specific details of each case. We are setting up for an iterative process that gets better with time.

In any case, with 1 quick edit, easy to add into the Lexicon, all of the references to Joshua throughout the inbound text are covered. 1404 inbound words are handled. About 1/2 million still to go.

Shifting Strategy: Problems In The Past

In the past I thought the entire list of unique words needed to be handled like I've described above. As I dove into these lists I got bogged down. I thought I had a technical, tooling related problem. So I changed the tooling, changed file formats, started new projects and tried again.

Looking back on this problem now, I can see I always ground to a halt because the language gets complicated and needs attention from the perspective of the actual words used in actual sentences.

This is especially so with vocabulary words which are rare across the text which then also show up with rare patterns of grammar. For many words it is almost impossible to figure out what to do without also looking at the word in a sentence which is mostly already solved.

Human readers of historical Aramaic must have certain skill in this area that they learned when they were learning to read. Some how, we must move through that same learning process in order to solve this general problem of finding the inspired text.

So this word list view of the problem is not the right way to think about this problem, especially all the way to the bottom. It only comfortably reaches about 60% coverage, as I explained above.

After this 60% level of coverage, the strategy needs to shift. After all the common, often small, words are entered, then the problem shifts to passages and finding the correct spelling of words. So far, we still don't know how to correctly spell anything. All we have done so far is split off grammar.

Shifting Strategy: Solving Passages

Correct outbound word spellings, which is also a function of the lexicon, cannot be known until after words pass audit. Taken alone, many words with added vowels still pass audit, even if added vowels are not inspired. The correct and inspired spelling must be proven by testing of words done inside longer inspired passages.

So once the lexicon has been primed with the very common inbound words, the strategy needs to shift. The next goal is to start getting all the words in certain passages entered into the Lexicon. This allows the audit code to start working on determining inspired spelling and inspired grammar.

Not all passages are created equal. Some parts of the text are better for solving this problem. These are the same passages that now look to be the intended places where young students learn to read.

These natural starting places are Proverbs and Psalms. These appear intended as places for learning the language. These have simple uses of grammar. They have simple vocabulary words. These places look ideal to start attempting sentence level, or story level, audit and recovery. By starting here, we go through the same language learning process for Paleo as native historical Aramaic speakers went through when they learned to read.

So the lexicon loading process shifts from common words, to the words found in Proverbs and Psalms. As all the words from those stories get filled in, the automated audit process can then start to work against long strings of words.

Some inspired sentences in Proverbs and Psalms should now start to pass audit. So the words in those sentences now have known good spelling. Those passages now show inspired grammar.

Reaching Break In

At this point, we reach "break in." We can now start teaching the lexicon the correct outbound spelling of inbound words. Once we reach this point the lexicon now knows how to spell words. The audit code need no longer test all combinations of letters.

Once break in is reached, the system will start an iterative cycle. At first only a few words in the lexicon have known good spelling. Each time another passage passes audit, then additional words are found to pass audit and the lexicon gets updated. That starts slowly but will get faster and faster as more lexicon words have correct spelling.

Passages with uncommon words and/or complex grammar can be skipped and handled later in this process. So once Psalms and Proverbs are mostly covered, then other areas across the text can be worked. Interesting initial passages are still passages with simple grammar. Genealogies, for example, will also make good starting points. Stories that we know must be inspired are also good starting points.

Passages that are almost certainly NOT inspired can be avoided until late in this work. 1 Chronicles, with long lists of strange names, is an example of a place to avoid. This is also why entering all names into the lexicon is not a good way to start.

More Planning

I still need to plan out the code for the audit side of this work. This is deeper into the recovery pipeline. Some divine names, for example, have been changed. Those go into the lexicon as well, but indicate to the system what alternative whole words need to be tested.

This is a tool chain problem that still needs to be worked out. What are the exact files? How are they formatted? What does the code for each step actually do? I need to prototype this process all the way to the bottom.

The audit process will also add audit marks to all the running letter strings that show up in the Paleo Bible app. This pass will determine what might actually be inspired. It will provide the means for anyone to inspect the work.

All this lexicon and audit work happens before the inbound word list is then combined back into the standard Bible format we use around here. I intend this to be an insertion into yet another set of files. These files will not be created from scratch with each iteration in order to preserve overall formatting.

Ultimately, the resulting text can then be carefully formatted while the audit work is still determining correct spelling and inspiration.

Theoretically, the Paleo Bible can be formatted as detailed as the BRB, should we have the need. That work can be done in parallel to the other work.

I still need to convince myself I have a working plan for that side of the recovery process. More prototyping to come. More on this problem in future weeks. I do, though finally have a plan.

Qu Map App

The link here is to our Qu Map app. The permanent link is off the front of Paleo.In. This app shows how the letters of the Paleo Alphabet map to geographic locations. We first saw this at Disneyland in California, but later saw how it maps out to other places in the world. Perhaps the most interesting is across 25 major places in the USA.

Elon Musk has been filling in a couple places on that USA version of the Qu Map. First, he built his main AI data center in Memphis, TN, which is the center of the Qu Map itself. The Qu letter appears to be a brain. The center of that map is Memphis. So an artificial brain at the middle is a reasonable match.

I was working on the computer this week while a live stream of a SpaceX wet dress rehearsal was playing in the background. There was a comment made on that stream of a purchase, or maybe pending purchase, of property in Louisiana by SpaceX. This was not all that interesting until someone said SpaceX was looking to purchase 200+ SQUARE MILES of land from ExxonMobil.

This was reported to be more land than Kennedy Space Center in Florida, which SpaceX shares with many other launch providers. So this would be a huge base for launching rockets. Especially interesting would be rockets launched to polar orbits used for AI data centers.

That wet dress rehearsal went fine. They are expected to make a full launch attempt the Tuesday after this blog goes out. But I wanted to learn more about this land purchase because it would match another part of the Qu Map. Musk already matches the Sa in Texas and the Ba in Florida. So is he about to match the Dot in Louisiana?

Pecan Island

The link here is to a post on X where S.E. Robinson takes his drone and shows the location of potentially future SpaceX property for a launch facility in Louisiana. Robinson already flies over Tesla's factory in Austin.

In this post, Robinson gives more specific details. This is 212 square miles of land, 136,000 acres. In this flight he shows the locks on the inter coastal waterway that you can then find on Google Maps if you want to see more details. This land is currently undeveloped. It was probably oil well territory in the past. There is a small town to the west of where Robinson took his drone.

This is south of I-10 and west of New Orleans. It would have easy access by sea from the current rocket factory in Texas.

Qu Map Interpretation

You can explore the Qu Map app and find New Orleans on the national map for the USA. The king will turn out to be Enoch, the first walk-off. He was taken to heaven because Joshua was pleased with him. Going to heaven is part of his written story. This is VERY rare in the text of scripture, so it is a nearly unique feature to Enoch and this location on the Qu Map.

Within New Orleans itself are the main factories that in the past produced the Saturn 5 rockets for the moon program. They also produced parts for the Shuttle program and now produce parts for the Artemis program. These are all markers on the ground for Enoch.

Shifting the region to producing parts for SpaceX would make canceling the Artemis program easier to do politically. It would provide prophetic continuity for the region from the past to the future.

The Dot letter is seed. New Orleans is a major exporter of American grain, grown up river from that port. You can think of the space program as sowing seed into space. The Star Link constellation is like seeds flying in space.

All of this is interesting because a huge SpaceX facility in this same area would be another prophetic match to that general geographic location.

A final curiosity is that Judah, so Russia, is the tribe that would normally go with this location. It was a failed trip to Russia when Musk decided he needed to make his own rockets. Curious indeed. Maybe once World War III is over, SpaceX should be making rockets in Russia too.

Watch Dates

The next dates we are watching are 2026-05-19 for the replay of the last year of Jehoshaphat. Then 2026-05-20 for the replay of the first year of Jehoram's reign. These are the Tuesday and Wednesday after this blog goes out.

We might see Trump restart war with Iran. Noah's story does not demand this, but a continuation of the war might land on some other timeline. Also watch Ukraine. This is the other active venue for this new World War.

As always, I am speculating as to where to look. Real headlines can come from anywhere.

Shop Work

This week we replaced Ryan's laptop. This machine already had some hardware issues with the keyboard. With external monitor and keyboard on his desk, these were not issues before. These problems become serious when updating to PopOS 24.04. The fix was to just replace this nearly 6 year old machine.

This was an almost identical replacement to my own laptop replaced about a year ago. Prices have gone up considerably for a nearly identical machine.

Serious price increases are something I don't think have happened in my entire adult lifetime of buying computers. Moore's law appears over, at least for Americans buying imported computers.

Ryan is now doing a fresh install of PopOS 24.04. This is not particularly difficult, but the build environment takes some setup for a local copy of the web server.

I will follow Ryan with my own laptop PopOS 24.04 update here soon. One problem at a time.

Iran War Status

This week was relatively quiet in the Iran war because Trump was off to China to visit Xi. Trump seems to have paused the war in order to not get flack from the Chinese during this trip to Beijing. Trump was also waiting out the 60 day War Powers window. He can more easily restart the war after returning to DC at this coming weekend.

There is also growing realization that Trump appears to have some sort of mental disorder. He is widely known to be unable to read status reports. He now also appears able to only track 1 or 2 points at a time. So the Iranian list of items for ending the war is beyond Trump's mental capacity to understand.

Ultimately, Trump's mental incapacity appears as convenient cover for the fact he is a vassal. He does not need to know what is going on. He only needs to read scripts and do a little ad-lib in front of cameras.

On the Iranian side, nightly rallies in support of the Iranian government continued. The Iranians continued to dig out their weapons tunnels. Most everyone on the podcast circuit expects the war to resume once Trump returns to DC. Though nobody appears to want to say so very loudly.

The oil supply shock continues to roll out around the world. "Tank Bottom" is a term rarely voiced in the fuels industry because there are rarely supply shocks strong enough to empty all storage tanks. This time is different.

"Tank Bottom" is expected in the USA around July 4, 2026. Different areas in the USA will have different Tank Bottom dates. July 4 is a consensus date for the USA as a whole. After that point, there will only be oil reaching American refineries as it is pumped from the ground. Oil prices must go much higher at that point in order to shed demand.

Many refineries will not be able to operate continuously after that date. Also worth noting there have been a series of strange explosions at refineries going on around the world. This may be a reporting bias because everyone in social media is watching. In any case, many think this looks planned.

Effects of this oil shock are hard to anticipate because nothing like it has happened in the modern era. The last time something similar happened in the USA was in 1973. This time is different. Even if Trump returned from China and caved to all of Iran's demands, it would be many weeks before fuels started flowing as before.

This looks to be the main fulfillment of the Noah Flood story. That story has 40 days of rain, but then rising waters continued to destroy the world. So the 40 days of war against Iran, even though they stopped shooting, continues to destroy much of the world.

Headline Review

The following caught my attention this week.

Victory Day Parade

The link here is to a post on X by Stanislav Krapivnik. It gives details on the Victory Day parade in Moscow on May 9, 2026. This was the 81st anniversary of the victory over Nazi Germany by the Soviet Union.

There was serious trouble with Ukraine threatening to bomb the parade. This did not happen, but it was a serious risk. Stanislav posted extensively that day about the meaning and impact on modern Russia of that war. We are headed into a replay of that same war, so it is important to understand.

Stalin's Victory Speech

The link here is to a post on Telegram with a copy of Stalin's victory speech at the end of World War II. Another reminder of the World War replay expected as part of the replay of Resurrection Sunday.

Detailed Oil Status

The link here is to a post on X that details the number of days of oil supply remaining. This is listed by major countries. It lists off any major actions by these governments to constrain use or help retail buyers. For many countries in Asia perhaps another 2 weeks before oil is gone.

Aramco CEO Comments

This link is to another post on Telegram citing the Saudi Aramco CEO Amin Nasser. He indicates 100 million barrels of oil each week are currently blocked from the markets. He stated demand would rebound if normal flows were to resume.

Imagine how many people are without fuel because of that shutoff. How many will die of famine because of this?

Timing to Recovery

Another post on X detailing the time needed to refill the oil delivery network. Even if the Strait of Hormuz opened immediately, it could not fully recover before 2027.

Demolitions in Silwan

The link here is to a Cradle Media post on Telegram detailing Israeli destruction of Palestinian neighborhoods in and near Jerusalem. 20,000 houses are said to be under demolition orders. This includes the "City of David." See 2 Samuel 5:7. This is the namesake and heart of Zion, so we would expect the Jews to want to recover this land.

This activity looks to include clearing of the above ground areas south of the walled city of Jerusalem. This is the route of the currently underground tunnels that connect to the pool of Siloam at the bottom of the hill. See John 9:7.

Videos I have previously posted here in the blog showed Israeli officials as not intending to disrupt the above ground areas near those tunnels. This post suggests those claims were a lie. The intent appears to be uncovering the entire area, removing all current above ground housing. Who knows what they might find buried below those structures.

That post indicates these will become "biblical-themed tourist parks." The Israelis probably think of this as preparing pilgrimage locations. What might Joshua think about this? Probably Zacchaeus.

FFmpeg

The link here is to a Youtube video on the Lex Fridman podcast. This is a long episode where Lex deals with the key people and history of FFmpeg.

This is perhaps one of the most important, most widespread, and most difficult, software libraries ever written.

Every reader of this blog has almost certainly used this code. This is ultimately a story about people with passion who want to change the world. Even when there is no money to make it happen. Very inspiring.

BRICS FM Meeting in India

While Trump was in China, the BRICS Foreign Ministers were meeting in India. That BRICS meeting may have been more important. Iran is gaining stature on the world stage and BRICS is one of the venues where this is happening. The video is a clip of the Iran FM at that meeting. This is just for the record to note that meeting.

Changing War in Ukraine

The link here is to a Daniel Davis / Deep Dive video on Youtube. Scott Ritter is the guest. They discuss Russia's changing war strategy as a response to Europe going to war against Russia. The Russians appear to be preparing conventional weapons strikes against European targets to attempt to stop the European war against Russia in Ukraine.

As we are watching for a replay of World War II, this is basically more evidence that such a replay will happen and that preparations are now underway to get it started. As Ritter suggests, the logic in Russia is pretty simple. Since the Nazis are now fighting us again in Ukraine, we need to start taking the war home to Germany and the rest of northern Europe. This will likely start with conventional weapons strikes on military and weapons manufacturing targets in Germany. Europe running out of fuel, expected within a matter of weeks, may slow down their growing Nazism.

Musk's All In Podcast

The link here is to a post on X by Elon Musk. Musk is making huge bets on AI and AI data centers in space. This All In Podcast covers much of the current business case for this. Doing this work in space is far better than on the ground. SpaceX could become one of the most valuable companies ever created.

Trump in China Summary

The link here is to a post on Telegram with a general summary of Trump's trip to China. Trump was there to mostly work business deals. Xi wanted a more substantive meeting, which did not happen. (The USA is run by a criminal gang. China is a civilization.)

Musk In China

The link here is to a post on Telegram with a video of Elon Musk in Trump's group who visited China this week. He is our favorite billionaire for a reason. He pulls out his cell phone and does a 360 video. His peers are worried about decorum. Very nice.

Elon's son in China

Elon brought his son X along for the ride to China. There were some fun photos of that father and son team. This link gives some commentary on Chinese interpretation of those photos of Elon with his son. It speaks of Elon building a family dynasty, which is important in Chinese business relationships.

Tesla Semi Production Begins

This link is to a Youtube video by the Electric Viking detailing how Tesla is beginning full scale production of electric Semis. Full capacity of the factory is 50,000 per year. It will take time to ramp to that number. Customers are already putting in large orders. Congratulations to the rightfully happy Tesla crew who has pulled this off.

50,000 sounds like a big number, but there are just under 50,000 miles of Interstate freeways in the USA. So 1 new Semi per mile of freeway per year is all they can produce.

Ryan and I have driven I-40 across the country. New Mexico is particularly beautiful, with rolling hills where it is possible to see great distances along that road.

We've seen endless streams of nearly bumper to bumper Semis running from horizon to horizon on that freeway. (With cars relegated to the left lane.) It will be many YEARS of production before electric Semis could ever begin to replace the current fleet of Semis.

More Later,

Phil

7 Layers Model

Phil Stone — Fri, 08 May 2026 21:28:41 GMT

This blog covers an important restatement of our 7 layer model of manuscript interpretation. In particular, Layer 4 is being redefined. We also introduce more features in the Story Grid app. Then shop notes deal with software updates and finally a headline review.

The Dream

Back when I was working on the Bible Time and Bible Tribes projects full time, I had a prophetic dream where I was shown a 7 layer model for how to interpret scripture.

That model itself, in some ways, overlays a well known 7 layer ISO model for interpreting computer communications. That ISO model was the framework needed to build the internet as we know it now. At the time, I was already familiar with the ISO model, so there was some affinity from that model to the 7 layer model I was being shown in the dream.

We have used that 7 layer model for interpreting scripture to powerful effect over the years. It has given us a way to categorize various problems presented by the manuscripts that we deal with all the time. I would expect to eventually end up with a 7 Layer model exhibit as part of the family of exhibits that hang on the wall. It is a powerful model.

This past week Ryan and I have reviewed that model in light of our work over the past 25+ years. We have decided to make a conceptual change at layer 4, the middle layer in that model. So in this blog I am reintroducing the 7 layer model but with our best understanding of each layer and how each layer is used.

Background

When I had that first dream about the 7 layer model, neither Ryan nor I were particularly interested in manuscript work. We had not yet taken any Hebrew languages classes. We knew nothing about Paleo. Ryan had not started his early Bible Dots nor Book Order work. So we did not really need to have a 7 layer framework. The dream itself was foreshadowing much of the work which would come in following years.

In the dream, Layer 4 was described as "Idiom." In our discussions this week we now believe that term was a place holder for the real layer 4, which we could not even conceive of at the time.

It is very important to note that sometimes true prophetic must provide fill in for details that cannot yet be understood. None of us can receive prophetic words if the subject of that prophetic word is outside of our understanding. We needed to know about the 7 Layers even if we had no idea of one of the layers.

I am going to step through the layers in order from bottom to top. On an actual wall exhibit, layer 1 is the bottom layer. The exhibit then climbs up, or builds up, across the more abstract layers.

If I was building a primary school curriculum that introduced scripture to new and/or especially young students, that curriculum would have an intentional order that moves from the bottom of the 7 layers up through the top. You will see why as I step through those layers here.

Precursors

The layers of interpretation are dealing with the manuscript of inspired scripture as given to a reader. Before the reader can even start, the precursor lessons naturally involve familiarity with the complete set of 3d models and related exhibits.

Conceptually, these form an exhibit room were students can become familiar with each series of 3d models and the ways those models are displayed.

The silver set, for example, is placed on the vine. Those models are also assembled into a Sower and Reaper.

The gold set is placed on a mountain exhibit. These models assemble into a Silo and Well.

The copper set sits in the table exhibit. It shows off the Qu Map and drawn letter forms for each letter. These models define the meaning of each letter.

The bronze set is placed on a river exhibit. They assemble in various ways into a series of trees that show off the life cycle of plants or more specifically the life cycle of trees.

The centerpiece of the room is the Fig Tree, which combines the gold and silver series. This shows off the conceptual system for the ciphers which are used for more volumes.

Around the walls of the room are a few more major and minor wall hangings. These include, say, Joseph's Robe, the Story Grid, the Tribes, the Scripts and a few others, like the 7 Layers of interpretation, clock and calendar.

There is also an upper room. The primary exhibits there are the Crown and Eden models.

Introductory students must understand the 3d system, at least at a conceptual level. They need to see how the models form a closed system of shapes. They start with infinitely repeating stars. They end with infinitely repeating plants.

With a general introduction to these models, the student can now begin to learn the various systems needed to understand the text. Let me reintroduce those interpretive layers here.

Layer 1: Alphabet

The foundation for all other writing, is the set of symbols used to write the text. These form the inspired alphabet. These shapes are taught with the Table Exhibit. That exhibit holds 25 objects that define each letter as well as 3 glyphs that are used for punctuation. The Sha letter, for example, is a molar tooth. Each of the other letters have a similar model.

Punctuation is also part of the 3d model and part of the alphabet. These will modify the sound system, impacting how vowels are otherwise sounded out.

The vowel system itself is taught on the silver set of models. Shared vowels also impacts the audit system that inspired text must pass.

Students pass this class when they can identify each letter, name the underlying object and can pronounce each letter with that letter's correct vowel. They should also be able to explain where these lessons are found in the 3d system.

Layer 2: Root Words/Spelling

In that dream 25+ years ago I only knew the English versions of scripture. English is unique on earth in that it has lost nearly all tenses. This happened in history in the British Isles when 2 different foreign invaders were speaking with the natives. Collectively, they had 3 different systems of tenses, though they shared many of the same root words. The public could only speak with each other through shared roots. So word order became more important and words were added to English to cover what had been word endings. Through this process, English generally lost most word forms. English still has a few word forms, like past tense, but not many others.

I have seen repeated comments by English speakers trying to learn Russian, that the biggest problem is understanding the Russian language's system of tenses. This is in part because there is no longer any equivalent in English. So learning Russian requires learning a new system of constructing sentence grammar.

I have also seen where speakers who are "English as a Second Language" don't understand there are a few tenses left in English. Nima Alkhorshid on Dialog works still misses a few of those strange English tenses.

I also remember traveling to China. I was taught that the meaning of Chinese sentences can be changed on the fly based on the speaker picking up on social cues from the listener. This is because word order does not strictly define Chinese. Diplomacy involving Chinese is a very high art.

We don't yet have enough audited Paleo sentences, but word order appears to be less fixed than we know in English.

Root Words

This past winter I crawled through the design for a Greek lexicon of a Greek language Bible. In the end, I was really learning how to construct a reasonable Paleo lexicon, which I will be doing here soon. Greek has many more tenses than English. So it was an education in how to organize and explain words in a language system with many tenses. That Greek lexicon was sorted around root words. By looking at many examples, I could finally see why this is important. The learning problem begins by learning how to spell and define the root words.

Every variant form, so every tense, of the root words that exist in the base Greek text were then listed under the Greek root. Those root words are a Layer 2 learning problem. The spelling of common tenses may also be a Layer 2 problem. But combining roots with tenses will be a Layer 3 problem as they appear and only make sense when found within full sentences.

I noticed at least 1 Greek root had maybe 2 dozen forms found across the Greek text of the Bible. So in Greek, for example, there is a huge list of possible variants on the root words. Except for names, most Greek root words have at least a few different forms that show up in the Greek manuscript.

So in the dream 25+ years ago, the name for this layer was just "spelling." To an English speaker this is enough. But in Paleo this should really be the spelling of root words. So the name of this layer should be Root Words, or more simply just Roots.

In Paleo, the spelling of a root ties to the meaning of the word itself. The dictionary meaning of a word comes from the spelling of the root. There are both primary and secondary definitions tied to the letter pairing as found in the silver set, so the Vine exhibit. So each root word has a pair of definitions based on spelling.

Students need to be able to work the word definition system as expressed by the spelling and the associated 3d systems. This is a system that can be easily memorized. Ryan and I have known it for many years. This level of understanding and finding basic word definitions is the job of layer 2.

Layer 3: Sentence/Grammar

So in English, sentences can be thought of as a list of words. 25+ years ago, this was how I understood this layer. The few English words with various tenses, like past tense, or plurals, are contributing to the meaning of the sentence, but not seriously impacting grammar.

But in Paleo, there are more endings than we know in English. The basic grammar is tied to word endings. So the grammar is tied to the tenses of words. So English can be thought of as a simple list of dictionary words, but this is a simplification if used with Paleo. In Paleo sentences, the words are more often modified with forms that match the needs of the sentence grammar.

In Paleo, a sentence has meaning that is found by understanding the forms of the words, not just their order. So the word tense system is tied to the grammar more tightly than we know in English.

In any case, being able to read a sentence for its meaning is the purpose of this 3rd layer of interpretation. Students of the language pass this level in the curriculum when they are able to read a sentence and understand what it says.

Note: ISO Layer 3: Translations

The ISO model of computer communications suggests that changing out network transmission hardware happens just above Layer 3. So changing from twisted pair wired Ethernet to Fiber Optic or Wifi happens at or just above this layer.

Note that translating a Paleo manuscript would also conceptually happen just above layer 3. This is where each sentence forms a unique block of writing, with a matched meaning.

The reader of an English translation will loose the important Paleo word definition system. But, they could at least become familiar with the general stories of inspired text.

Readers of translations from Paleo will also not be able to speak in the native tongue with Kings, nor with they be able to speak with residents of Eden, but I digress.

Layer 4: Story

This is the layer that is getting redefined in this blog post. In the dream this was called idiom. I now believe idiom to have been a place holder for something that we are only now fully understanding.

For many years, Ryan has been studying idiom in the BRB. He has been marking up words with strong idiomatic meaning. There are currently options in the BRB that enable or disable idiomatic highlights.

After many years of searching, these idiomatically important words are very rare. They have not become a very exhaustive list as would be expected for a full interpretive layer.

If idiomatic meaning is tied to root word meanings, Idiom might be considered a function of Layer 2 or even better, a function of the lexicon. Idiom is not a comprehensive system that has meaning across all parts of the text.

So what is the correct system of interpretation which would naturally sit at Layer 4?

Ryan has been putting a huge amount of work into the Story Grid. This has been an ongoing project since we first taped 3x5 cards to the living room wall in Tulsa, just before we moved from there to Colorado in late 2017?

Sentences group together into stories. The overall list of stories is the highest level view of the inspired text itself. There is a massive amount of meaning for each story that is found when that story is paired against other stories using the grid.

So what I am stating here in this blog is that Layer 4 of the layers of interpretation is the Story Grid itself.

Once a reader can understand the simple textual meaning of any given story, then that reader should learn how to compare and contrast that story to the matched stories as found across the Story Grid.

Note that we expect stories to be an inspired system, unlike chapters in modern Bibles. We don't expect book level groupings of stories to be all that important. Current work with the Story Grid is bearing this out. Stories are a very important conceptual layer.

Stories Are Like Addresses

This story layer basically completes the address system for inspired text. Imagine a printed Paleo Testimony. You open it. It is organized into 625 stories. Each story pairs off to other stories. This is the top layer of interpretation with reasonable side annotation in the printed form of the book itself.

Curiously, the Story Grid is organized around the Paleo Alphabet. Story pairs are found through the same systems of letter pairing as used for word definitions and for the trees in the bronze set of 3d models. So the Story Grid is bringing systems learned in the lower layers to bear on the overall design of the entire text.

We have previously considered the Story Grid to be a function of Layer 6. This shift clears out Layer 6 to have a better, simpler, definition. More on that below.

Layer 5: Symbolic

This layer covers all symbolic meaning found cross the text. Symbolic meaning has a series of uses depending on context.

Symbols reward students who have learned the text particularly well. Simple symbolic terms often capture large conceptual frameworks that are explained in detail in various places as found across the text.

Symbols are also used as a sort of "prisoner speech" where a writer can speak in important ways where not all listeners have earned the right to understand. For example, a prisoner might use coded language to speak past a prison guard.

Joshua often speaks in the text in ways that Zionists cannot correctly comprehend. He was particularly fond of this sort of speech when speaking to the Pharisees of Jerusalem in his day.

Symbolic meaning is captured in all of the normal use of lists. A list of 4 deals with ciphered documents. A list of 6 deals with the villains. A list of 12 deals with tribes. A list of 24 deals with both Isaac and Ishmael's tribes as a whole, as well as their match set of 24 heavenly kings.

Symbolic terms used in the text are often just names for the exhibits and/or their functions. Though these are not particularly hard to figure out when a student knows the exhibits, they are often showing up in symbolic stories that involve the exhibits.

Story pairing in Layer 5 can reveal symbolic meaning. Story pairing, at times, makes no sense without knowing the symbolic meaning involved. This has been Ryan's challenge in working out which stories are inspired and where they go in the Story Grid itself.

Note that the symbolic meaning sits in a layer above the stories because symbolic meaning does not make much sense unless the reader is generally familiar with all of the stories found in inspired text.

Layer 6: Prophetic (Time and Place)

In the dream 25+ years ago this layer was defined as following a mapping rule from 1 domain to another. The examples at the time were always given using date related math. "1 day is as 1000 years" is an example from 2 Peter 3:8. If you know this rule, you can map between systems that count days and those that count 1000s of years.

This works internally to the text for building up matched timelines. It also works externally to the text in order to understand events in world history as following stories in the text. This is the interpretive layer that sets us up for applying the text to world, which is Layer 7.

The Qu Map is another example from Layer 6. The rule for Qu Maps is similar. Anything that maps to a letter will also map to a place on the Qu Map.

The Lost Tribes are found using time to find a place, or set of places, that tie people groups in the world back into the text.

Except for the Story Grid, now at Layer 4, we have not found any category of prophetic writing that is NOT tied to time and/or place in some way. There are symbolic names, so layer 5, given to people and places in the modern world. Those parties often get their identities through timeline studies.

We know modern Israel as related to Benjamin in some way because of predicted, dated, events for 1948, 1956, 1967 and 1974. Again, this is a prophetic use of time to learn the identity of a specific place. From that pairing, then various stories from the text can be applied to those places.

We know the other tribes by their seal dates. We know much about Russia because of 1000 years of Christianity in that nation. Again, we connect stories to the world almost exclusively through the use of the timeline.

Once we make those connections, we can then also make prophetic claims about those same nations because we can tie that nation to stories in the text.

There will eventually be an upper room exhibit, called the Crown, which takes this entire category and expresses it in a timeline like form. That exhibit will pick up important repeating cycles that cannot be seen without the exhibit itself.

Layer 7: Application/Sabbath

This is the top layer in the 7 layer model. In the dream the word "Application" was used for this layer. This is the same name as given to Layer 7 in the ISO 7 layer model of computer communications. In that ISO model, the 7th layer means the network made a reliable connection. The computer user is now connected to a remote application. Say a website. The computer user is now concerned with application issues, like watching a video.

In our case, this Layer 7 is where the text takes a rest. The text takes a Sabbath. The text now asks the user to interact with some real world subject itself.

We were not following Sabbath when that dream happened 25+ years ago. So the term Sabbath did not have much lived meaning. Now it does. Sabbath is the day when readers should be interacting with the text itself. This is done in order to apply it to the real world in some way.

The main point of this layer is that it is up to the reader to decide what to do with the text. Are you going to follow Joshua? Or not? Are you going to learn about how the world follows the text? Or not? Are you going to stay away from the teaching of the scribes and pharisees? Or not?

Ciphered Documents

So now there is the question about ciphered documents. We expect cipher work to come after the audit is finished. We expect more documents to cipher out of the based inspired text. We expect some of those ciphered documents to be known to history as ancient, but off-canon, written works. We also expect those off-canon works to have been edited, just like everything else from history.

Where do these additional texts sit in this 7 Layer model?

Here is a way to visualize the answer. Imagine the story grid as a tiled floor. A big floor, in a large room, with 25 tiles by 25 tiles.

Now imagine putting a printed copy of each story on each of the respective tiles.

Next, imagine those stories go through ciphers. Where do you put the resultant ciphered stories?

The answer starts out relatively simple. Just stack each result of the ciphers back on top of the original story from which it was ciphered. So the ciphers sit in the original spot on the story grid along with the base story.

That imaginary floor will stack up with more stories. But they will be arranged in the same way as the base stories already in place. Besides connecting down to the base text, the ciphered stories should also connect to each other just like all the base stories already connect.

The set of content in the ciphered stories becomes available for interpretation through the same 7 Layer model used for the base text. Those ciphered documents are constructed through letters arranged in words which form into sentence. They sit in the story grid, so pair off through the grid like other stories. They will use the same general set of symbols as the base text. (Though they may introduce more.) They will connect to the timeline in various ways. They will finally also apply to the world.

So the 7 Layer model of interpretation will also apply to ciphered stories.

Story Grid

Perhaps in keeping with the Story Grid becoming Layer 4 in our new understanding of the 7 Layer model, the Story Grid app was significantly updated again this week. These new features are worth noting. The link here is to the Story Grid app. The permanent link is on the front of Paleo.In.

The power of this app is that it shows the relations between stories. This has been an important tool for figuring out what stories are inspired. Once our recovery work is complete, this app becomes the functional equivalent of a Study Bible. So it has a permanent place in our app lineup. It is the place for understanding Layer 4 related issues in the inspired text.

Canceling Study Bibles

Study Bibles are traditionally important tools because they allow readers to understand what stories in standard Bibles are thought to mean. I remember when I was young member of a Bible Study. Everyone in that study had a certain specific Study Bible. It was giving us a reference for explaining what the various stories in the Bible are thought to have meant.

I also distinctly remember when the members of our Bible Study felt a particular note in that Study Bible was provably false. Our collective illusion of invincibility and trust had been shattered.

We tried to share what we found with someone at church the following Sunday. They refused to listen. They treated the Study Bible's note AS IF it was inspired text. They were obviously caught in some sort of Study Bible trap. In their mind, it wasn't even theoretically possible to come up with an alternative interpretation. What was printed in the side notes was more trustworthy than truth from other scriptural passages.

When our Bible Study had gathered again, and could speak freely, we were basically done with using Study Bibles at all. We did not like how authority of printed notes overrode basic truth.

The way the notes in Study Bibles were trusted when they should not be trusted was the tip of a very big iceberg. Little did I know at the time that Study Bibles are how the Zionists took Protestant Christians far from traditional Christianity in order to specifically support Israel. We were sitting ducks for evil.

Story Pairs

In the end, interested readers still have a need for a tool for understanding what, exactly, each inspired story is actually about.

The correct way to solve this problem is by comparing story against story. Or by studying alternative runs of stories. This does NOT need a human author to come along and explain how tradition explains a story. All this really needs is a tool for showing which stories pair to other stories. That is the enduring purpose of the Story Grid app.

Grid Headings

The Story Grid app itself is a giant map of the 625 stories. They are arranged on a 25x25 grid. Each square has a 2 letter code that shows the row/column within the grid. Tap any story and a pop up shows the text for that story.

So far, this is just a strange form of a table of contents in a regular copy of the The Testimony. The text in the Story Grid app is ultimately the same as the text in The Testimony. The same stories as found in The Testimony can be easily read in order just by tapping the Story Grid squares in their numeric order.

Where the Story Grid app gets interesting is in the pop ups found in the left and top labels along the sides of the main grid. Those pop ups have been reworked in this week's release of the Story Grid app in an important way.

Those pop ups have always been the place for Ryan's notes as he has been working out the story placements in this grid. Those notes still remain. Some of his notes are complete. Some are yet to be filled in as he continues to work out the inspired form of the overall Story Grid.

Ryan's notes are like the scaffolding used for building refurbishment. They are there to get the place rebuilt. They provide his evidence that the grid is filled in correctly. The audit work should eventually confirm the work Ryan is doing. We'll see. Can audit indicate book order? Maybe. Maybe not.

Variant Reads

What has been added this week are quick links to important variant reads for both the rows and columns. A variant read is an alternative story reading order driven by some known alphabet related system. There are 2 variant reads that come from the 3d system. The first is from the Vine exhibit. The second is from the River exhibit.

Both of these exhibits ultimately arrange the alphabet in specific and unique ways that are NOT the normal alphabetic order. For the Vine exhibit, the variant read story order is found by "climbing the vine." A memory peg is like how Jack climbed the Bean Stalk. For the River exhibit, the variant read story order is found by "floating the river." A memory peg is to imagine floating down the Jordan river on a raft from the Sea of Galilee to the Dead Sea.

In both of these adventures, the goal is to discover new stuff on the journey.

Note that the Quad letter is at the top of the Vine. That letter is also in the Sea of Galilee. So climbing the vine to the Quad story is the turn around point for floating the river.

Quick Access

So this week, the pop ups for the rows and columns have gained quick access to these variant reads for each of the respective rows and columns. So if you want to climb the vine, or float the river, you can do so by just tapping the header pop up and then tapping a choice along the top edge of the pop up itself.

The Sabbath Reads, available in the Sabbath Reads app, are yet another alternative column related read on the Story Grid. So the Sabbath Read variations are also provided in the pop ups for the column headers.

Enough of the Story Grid seems to have come together that it is now possible to see some of the promise of these variant reads. This is all still subject to change, Ryan is still working on this problem, so beware. Let me share an example so you can see what we are seeing and get a sense of the promise of what will come from this.

Vine Read Details

The Vine read starts with the Mo letter. As currently arranged, the Book of Psalms occupies the Mo row on the Story Grid. So Climbing the Vine will always begin with a Psalm.

For the far left column of the Story Grid, climbing the vine will begin with story 325, Psalm 1, about how blessed is the man who does not walk in the way of evil, nor stays in the counsel of sinners, nor sits in the company of mockers... Whatever he begins he accomplishes. It also contrasts this with the wicked, who will be like chaff blown away, not justified in the judgment, who will not sit in the assembly and finally how the wicked will perish.

These are the themes we would expect through the rest of the Vine Read. So we are watching for examples that compare and contrast these ideas.

Staying in this column, the next Vine letter will be the Yo. So story 250. This is currently the start of Tobit. Tobit is perhaps one of the most extreme examples of the ideal described in Psalm 1. The start of Tobit gives us his credentials, and all the things he typically did to help others.

The Vine read then moves to Oo. In this column, story 400, which is Joshua's early years. So Joshua is going to be following Psalm 1 like Tobit does. In this story of Joshua's early life we learn how he was taken to Egypt following direction given to Joseph in a dream. Here baby Joshua and his parents are being protected from evil Herod. Once Herod died, Joseph was free to return his family back to the land of Jacob. The death of Herod can be easily seen as an example from Psalm 1. We are seeing an example about how Joshua often protects those who follow him. In this case by hiding in Egypt.

The Vine read then moves to the Jo. This will be story 175. This is the account of king Joash. The distinctive feature of this story is how Joash is hidden by his nurse while evil queen Athaliah is ruling the land. This is another example of being hidden from evil. That queen is eventually killed by palace guards once the young king is old enough to be brought out in public. This an example of what eventually happens to evil, though it adds how it can take years for that to happen.

Let me skip ahead to the end of this particular Vine read. The vertical Vine read always ends on the Quad row, so the bottom row of the Story Grid. This is usually a story from Revelation. In this case the first column Vine read will end with story 600. This is the introduction to Revelation. It begins with a vision of Joshua coming in the clouds. This is like earlier examples of waiting for deliverance from evil. In this case, the wait is measured in historical time, not personal time.

This final Vine read story continues with details of John's situation. From the earlier stories in the Vine read, we can assume John was on Patmos for some reason related to safety or protection. We can also assume that he was an example of someone whom Joshua favored, like some of the earlier examples in the Vine read itself. In this case, John's is rewarded with what will become a visit to Eden. This is, of course, the main goal of life itself.

The Promise In Alternative Reads

There is enough promise in these reads to think these alternative reading orders are useful and intended as the inspired alternatives to Study Bibles. Just reading the text in ways that show off connections is a much more satisfying way to find deeper meaning in the text.

It will be much more difficult for low cognitive ability readers to confuse Zionist notes with inspired text. This is a nice feature for large groups of people who may assemble together. There will always be a few people with low cognitive ability in any large group of people. Even when they don't really get the story, at least they can learn regular text instead of learning to quote someone's Zionist notes.

Once the entire Story Grid is filled in, this will not depend on the theology nor secrete club membership of famous pastors who set out to write the notes found in modern Study Bibles.

Story Grid Tech Notes

This week I changed some of the tech behind the Story Grid app. Our build system allows for app side rendering of Bible Quotes. This is only needed when an app quotes most of the text of the Bible more than one time. The Story Grid app is now quoting the TT subset of the BRB for something like 5 times. (With more coming, we are not yet showing diagonal reads.)

So this week's update carries the text of the Bible around only 1 time, and in its most dense form. This reduces the installed memory footprint from around 70 megabytes to around 27 megabytes. The original install time and later app update times will all be better. Our server will also take less of a bandwidth hit.

The cost of this change is the Bible's text is filled into quotes only when needed. Some users may see the text flash in when the various pop up choices are made. If this becomes a problem on someone's (probably unusual) hardware, please let me know.

Iran War Notes

At the beginning of this week we were still in a stand off between the Zionist west and Iran. The 2 sides had been exchanging proposals for an end to the war while a tentative cease fire remained.

Technically, Lebanon remained at war with Israel, breaking the agreed cease fire. So Iran was looking weak. Iran was most likely using the time to prepare for resumption of the fighting.

Trump appears to be the first to have blinked. Overnight heading into May 4, 2026, Trump announced his intention to escort ships out from the Persian Gulf through the Strait of Hormuz.

To many observers this looked something like a trap against Iran. If Iran were to shoot first, Trump would blame Iran for restarting the war.

This cat-and-mouse game continued off and on for most of the week. Near the end of the week there were various explosions in the UAE. Western media blamed Iran, who would disavow at least the initial attacks. But this was used as pretext for UAE to start a formal war against Iran.

By Friday of this week it looked like there was ongoing fighting between the UAE as a Zionist proxy and Iran. The Zionist war plan against Iran needs to foment civil war within Iran so as not to use western troops. This is theoretically possible in the south east of Iran as well as the north west. So the UAE as the starting point for a war might provide cover for ground operations in the far south east of Iran.

Watch Dates

Peeking ahead, the next watch date is 2026-05-19, we will return to that in next week's blog.

Shop Work

The shop work this week was a continuation of the hardware upgrade cycle going on with our 2 desktop machines. The old machine, called Flash, was originally purchased in 2017. The new machine, called Cilla was purchased in 2025 to replace Flash. (Flash and Cilla are named after the sloths in the original Zootopia movie.)

Cilla came with a new AMD graphics card. It worked with PopOS, but not with the 3d design software. So that original GPU card was replaced with a spare Nvidia graphics card from Flash, purchased when Flash was new. Everything then worked fine. Cilla, with PopOS and 3d design, has been running fine ever since.

In messing around with the next version of PopOS on Flash we found trouble with support for what is now an obsolete GPU. We don't need 3d design software on Flash, so Cilla's original AMD graphics could be used there. But alas, Flash's old BIOS cannot support the new AMD Graphics. So Flash is probably headed for Ubuntu server, on old graphics, or else Flash gets retired. (Flash is already something like 9 years old.)

Cilla, though is now running a very old GPU. To upgrade PopOS and keep running 3d design software means we need both a newer generation of graphics and an Nvidia Graphics card. I found the simplest new Nvidia card that would work with PopOS. It was available on Amazon and arrived this past week. That new card has new monitor cable plugs and needed new cables for the monitors. Those cables came in yet another Amazon order. All this new hardware on Cilla was swapped in. Cilla was now back in everyday working order, ready for the PopOS upgrade.

That upgrade also happened late this week. The install media offered to replace the existing operating system, but keep user accounts. This is a variation for Linux update that I'd not seen before. It worked pretty much perfectly. It did require reinstalling apps, which is not that hard. This form of upgrade left a pristine system configuration which was very nice. We reconfigure our desktop systems to match the production server configuration so we can test websites. So a clean system configuration after update was nice to have.

We normally update systems every 2 years jumping along using only Long Term Support (LTS) versions of Linux. Because PopOS was late, we have been nearly 4 years on the last LTS version of the OS. So it has been awhile since we did this sort of upgrade.

In all the upgrade work, we found only a minor configuration issue on the Nginx web server software. A change to our build environment fixed that problem. I have brought up copies of all of our websites and apps on Cilla. They are all running fine.

Paleo Keyboards

A major feature is how PopOS 24.04 drops system support for an old graphics system known as X11. We understand this change was done to clean up and speed up display handling across the desktop. The new Cosmic desktop system on PopOS is obviously very fast, much faster than the old system it replaces.

We use a font design tool called Font Forge which is based on X11. Turns out that tool runs fine on the new PopOS. We suspect because that app itself still has an X11 library that adapts, or shims, to the new graphics drivers.

But reports of dropping X11 worried us because we use a custom keyboard layout that lets us type in Paleo letters whenever needed. This is going to become very serious here soon as we start audit work. Updating all this software is happening now so I can keep working audit code.

Our custom Paleo keyboard uses a file format defined for use in X11. So we were worried there was either a new standard for keyboard layouts or that there would be no customization for keyboards.

To our great delight the same steps we first figured out in 2009 for installing this custom paleo keyboard still work now. PopOS did not change the basic keyboard customization file formats that have been around for years. Even though those formats were originally called out for use in X11.

We can now type in Paleo and we are ready to rebuild font files with audit related marginal marks as needed for audit work.

This has been a very nice week. We still need to update our laptops before going ahead with more audit work. More on this later.

Headline Review

The following caught my attention this week.

Fishing For War

This link is to a Health Ranger cartoon showing the status in the Strait of Hormuz. The Zionists need Iran to start shooting. So they are dangling US Navy ships hoping for a bite. So far, the Iranians have not taken the bait.

US Ships Turning Around

This was one of many posts dated May 4, 2026, where the US Navy ships that Trump sent to escort ships through the Strait of Hormuz were fired on and had to turn around. The US side then said they would escort via radio. Strange week.

May 4 Games

Another post on Telegram detailing apparent US attempts to get Iran to shoot first in breaking the cease fire.

Wife's Cake

Cake Closeup Photo

In previous weeks I have been looking at Ben Givr's gallows as a possible match to Haman. He promoted a new Israeli law to use hanging as lawfare against Palestinians. Gallows are very rarely used in the modern world. They are relatively rare in the text. So matching Givr to Haman is worth at least noting in order to follow this story. There are many months before we get to possible replay dates for Esther and Haman.

This week this story got even stranger. His wife baked him a cake with a hangman's noose on the frosting. The links above provide photographic details.

In the text, it is Haman's wife who proposes the use of such a tool. See Esther 5:14. Now we see how Givr's wife is also involved in this strange story. Not good for him to see such matches lining up.

Scofield Bible Scam

This is a to a link on X where Natali Morris discusses the Scofield Bible scam. Should not be news to most readers here. We used the NIV Study Bible, not Scofield. Scofield is the grand-daddy of the genre. I have not read it, and don't intend to read it. But interesting background if you don't know the history and purpose for this first example of the crime.

Crow Feeds Cat

In 1 Kings 17:2-4 is the written account of Elijah being sent into hiding by a brook. Part of that story is how the ravens will feed Elijah. This story begs a question. Is this a symbolic story? So "ravens" are a name of a group of people who will feed the prophet? Or else is this literal, that actual ravens will feed the prophet?

The link above, if real, suggests this family of birds is known to feed others in need. The link here is to a post on X with a story about a crow feeding a sickly cat. Even after the cat was rescued, the crow kept returning each morning. Curious. Elijah probably had actual ravens feeding him, not figurative. Readers familiar with ravens are supposed to just know this.

Remembering Odessa

Memorial Candle

Flowers At The Gate

The links here are to various posts on Telegram that form a reminder that we just passed the 12th anniversary of the Coup in Ukraine that kicked off the current war with Russia.

Now that we know that event as the replay of resurrection morning, it is important to remember details, as this was the formal start for this prophetic day. This was the start of World War III, where the Zionists attacked Russia.

The main violence at that point was broader than Kiev. The worst was in Odessa.

Palestinians Out Of Jerusalem

The link here by the Cradle on Telegram suggests the Israelis are currently removing Palestinians from in and around Jerusalem. This is Ethnic Cleansing, a type of war crime. This is perhaps evidence of big plans for the city of Jerusalem itself.

Nuke Plant Strikes

The Zionists in Ukraine have been striking targets around a Russian nuke plant. This post has some details. Death cults are strange. They kill their own just as easily as others. In this case they will poison their own world. So are the rulers in Kiev locals from Ukraine? Probably not.

Famine Coming

This link is to a Youtube video on Daniel Davis' channel. He interviews Mike Adams. Adams sees ahead better than most. The argument in this video is how Trump has already triggered a global famine. So far, the risk is mostly in parts of the world where food is already scarce. As this gets worse this will reach North America as well. The Zionist death cult is at work.

Professor Jiang on DOAC

In this Youtube video the good professor lays out the basic parameters of World War III. This is a nice easy to understand high level introduction to the war ahead. Prophetic stories will give us more specific details as we go along.

Near the end, Jiang explains the Kabbalah based eschatology behind this war. He has argued in previous videos that the religion of secret societies is really driving war goals around Israel.

Jiang is usually citing official sources. So I don't dispute his report. But the Zionists behind this war don't know the story of Zacchaeus. They don't get the purpose and future of Israel.

More Later,

Phil

Story Grid Updates

Phil Stone — Fri, 01 May 2026 21:30:54 GMT

This blog reviews updates to the Story Grid app. Before that, some reader feedback triggered more study of the Ethiopian Bible. Finally, code status and a headline review.

Could This Be Related to Paleo?

This week started with feedback from last week's blog. I was sent a pic of a random page out of an Amharic language Ethiopian Bible. I was asked if this could be related to Paleo?

The question, and the pic, triggered another discovery in current Paleo related kerning. Let me share the whole story here, and then show what just changed in our work.

I showed the photo to Ryan, so he cold think about this text along with me. This photo was of a random page in the native Amharic script, which is also the modern language for much of Ethiopia. Pages in this script have a certain artistry which was the first thing we noticed. But, there was some important details.

The particular Bible in question had been purchased in Ethiopia. So it was perhaps easier to find in that country. We already have a new copy of the Ethiopian Bible, but translated into in English. We don't have an original language version of that Bible, like we have Bibles in Aramaic, Samaritan, Hebrew and Greek.

Our first instinct was to see if we could find a copy in the original script for sale around here. Amazon does carry it. Our order arrived this week. I'll share some pics on Telegram when this blog goes out.

We also ordered a names dictionary for Amharic. This should be enough to figure out the map to the Paleo alphabet. We still cannot find an electronic copy of the Amharic manuscript, which we would need for serious computer work, but we don't need that for now.

Because this is such an alien Bible, let me cover some key points with links for anyone who may want to learn more. What follows here is the outline of the precursor work before conversion of Amharic back to Paleo.

Geʽez

The original language for scripture in Ethiopia was Geʽez. The link here is to the Wikipedia article for the Geʽez script. There are several secondary articles for readers here who may want to read more.

This particular language is now extinct, but it is still used for liturgical purposes in Ethiopia and Eritrea. It was replaced with Amharic in the 1400s, which is what we see now in printed Bibles. So there was a transformation in the writing system around 500 years ago.

Amharic

The link here is to the Wikipedia article for the Amharic language. This is the language that replaced Geʽez starting in the 1400s. There are very large numbers of people today who use this language. It is the federal language of Ethiopia as well as the language of several areas within Ethiopia.

Protestant Canon

It is also worth noting that on Amazon we could only find an Amharic Bible using a Protestant canon. So a 66 book Bible, not the normal 88 Books of an Ethiopian Bible.

I am starting to identify the handiwork of modern Zionists against Christians as being marked by a 66 book canon. I had a strange prophetic day here recently. I read a post on X that noted the famous 666 reference in Revelation is a reference to the Israeli flag. 6 lines creates 6 triangles forming a 6 pointed star.

I then surged, as I normally do when Joshua wants me to do lots right now. I did those lots and landed on the original 666 Revelation passage itself. Then another lot landed on a passage naming Benjamin. The point? Joshua agrees. 666 is a marker for modern Israel. So as a memory peg, the 66 books of the Protestant Bible is a child of Zionism. Stay away from 66 books when you can. In this case we can't.

Prayer Book Example

The link here is directly to a Wikipedia photo of a 15th century prayer book in this earlier script. This is a little less complex than the modern printed text. In particular, the modern punctuation is more complex.

But, in this photo, you can still see the use of the Paleo Colon as the between word separator. The sentence terminator is harder to make out, because this example was made with both red and black ink.

The photo we were sent was much more clear. The end of sentence marker is a double Paleo Colon. We would print this same shape simply by placing 2 Paleo Colons in succession.

You can imagine the evolution from Paleo. In this Amharic tradition, the single Paleo Dot for a between word separator was duplicated vertically. But then, the Paleo Colon was no longer distinct. So that character was duplicated horizontally for use as the end of sentence marker.

This Amharic example is proving my contention that the Paleo Comma, so 2 dots in succession, is why the Paleo Colon is rotated vertical. This is slightly unclear given the various 3d systems that would inform Paleo Colon placement on the canvas.

Double Paleo Colon?

But, this Amharic example begs a question. Did the inspired Paleo manuscript we are working on recovering, have some use for a double Paleo Colon that was then repurposed in Amharic?

This question suggests Amharic was only repurposing an original, but known, Paleo punctuation.

This question bothered me because I was reworking kerning code this week too, and the kerning tables that are also used in the audit, have room for a double colon.

Like a double Paleo Dot, a double Paleo Colon would audit uniquely. The audit system, and eventually the weaning system for ciphered documents, will show exactly where double Paleo Colons should be placed in running text.

So there is room in the inspired Paleo writing system for a double Paleo Colon just like there is for a double Paleo Dot. But, what would a double colon mean in running Paleo text?

Before answering that question, let me review more interesting details about the Ethiopian Bible.

Abjad

The Ethiopian script is a writing system known as an Abjad. In this type of writing system the vowels have no specific letters, only the consonants.

The link here is to the Wikipedia article that explains the term which was first coined in 1990. Earlier terms used for this same idea included "consonantal alphabets," which is perhaps a less obscure name for the same idea.

Modern academics want specific technical terms so they form an elite club hidden from the public. Consonantal Alphabet is a better term.

In any case, Paleo is an Abjad, a Consonantal Alphabet. Paleo does not need to draw vowels because the student using the alphabet was taught vowels using the 3d system of exhibits. Vowels are on the top side of the silver series of 3d models. That series teaches which consonants share which vowels. That lesson is key to the audit system.

Ezana Stone

The link here is to a Wikipedia article for the Ezana Stone. This is very similar to the more well known Rosetta Stone. In this case the stone is tri-lingual, in Geʽez, Sabaic and Greek. It was carved between the years 350 and 356, which is establishing how Geʽez was in common use by that time in history.

The Ezana stone is located in Axom, or Aksom, Ethiopia. This city is famous as the African location of the Ark of the Covenant. This was likely home for the Queen of Sheba mentioned in 1 Kings 10:1. This is also the likely home for the Ethiopian official that Philip meets starting in Acts 8:26. These visitors are likely coming from one of Ishmael's lost tribes. So Ethiopia is almost certainly going to be one of those tribes.

Note that the Queen of Sheba may have either copied Solomon's ark or Axom became a place for hiding the Ark in Jeremiah's day. Christian churches in Ethiopia still mark that ark heritage on their altars. Solomon's ark may or may not be an actual artifact from the inspired exhibits.

Perhaps there is a special box to carry the stone tablets. Solomon may have created a gold box as part of his false temple construction work. Axom may have received the original pre-Solomon ark from Moses' day, which is also a curious idea. The queen's fascination with Solomon suggests she did not know about the history that came before. She may, though, have learned the language which had not radically changed by Solomon's day.

This is important because Solomon was using the Paleo Alphabet. The Hebrew alphabet of today was invented in Nebuchadnezzar's time, roughly 400 years after Solomon. So there is a strong reason to think the Amharic language tradition branches off from Paleo BEFORE Hebrew. The same is true for Greek.

Computerization

Whenever I look at a new language and/or writing system I usually turn to the Unicode standard. These documents have some conventions that make it easy to understand a complete system of writing. This is ultimately what modern computers are able to express in any given written language or writing system. So the Unicode Standard is normally a complete view of what is possible to write.

Ethiopic Unicode

Ethiopic Unicode Supplement

The 2 links here are to the Unicode standard for Ethiopic. This writing system was added in Unicode 6.0, but then extended with more characters in Unicode standard 17.0. Extensions in the Unicode Standard typically mean the common use of the writing system by early computer users was not as complete as actually exists in writing out in the world.

This happens because someone came along after Unicode 6.0 and tried to computerize some obscure manuscripts from an ancient version of the language. So the supplement was added by someone who cared about computerizing obscure texts. The 2 pages linked here are those which together are specific to the Ethiopic family of writing systems, Amharic being one of those languages.

What matters here, as an introduction to Ethiopic, are the names given to each glyph. These Unicode Standard letter names are always written in Latin letters. This is done so most of the world can at least know some unique name for each possible letter than can be expressed in the computer.

These Unicode Standard pages usually follow someone's simple convention for the map from an original alphabet to Latin or at least Latin sounds. This character naming convention is used in the Unicode standard for nearly all alphabets used in the world.

If we were ever to submit a proposed standard for the Paleo Alphabet, we would use letter names like "PALEO LETTER WA."

Unicode letter names are very rough. They are a first pass guess about how someone thought the letters might map to Latin. From there, we have a start at mapping to other writing systems, like eventually Paleo.

Document Layout

These standards documents always follow the same form. There is a graphical map of the characters with examples. This shows how a certain block of Unicode is covered by characters. A font designer needs this. Then there is a list of the same characters with specific names given in Latin letters.

By looking at the first link above, you can see the first entry, 1200, is ETHIOPIC SYLLABLE HA. This is followed by Unicode values for the Ethiopic syllables for HU, HI, HAA, HEE, HE, HO and HOA.

You can see how a vowel is attached to a root letter, which are really short syllables. In other writing systems these are usually called a "LETTER" of some sort. In this case the Latin H is used to mark the shared consonant across all of these different Ethiopic syllables.

You can look at the drawn form and see these are often similar in terms of shape. Whatever Paleo letter this may be, perhaps a Paleo Ha, we can assume all of these same Unicode characters are coming from the same original Paleo root letter. These syllables are varying by the vowel only. Note that vowels are usually following the consonant. This, too, is like most of Paleo.

Note also that an actual ancient text probably would not use all of these syllables. The spread of vowels comes across time. We would need to survey a real manuscript to see what Unicode values are really used.

Since names in the text, like Abraham, are usually stable across time, these Unicode standards, combined with a names dictionary, should be enough to crack this family of ancient Bible texts and recreate the base Paleo that informed this canon.

Was this originally a lost copy of an inspired text?

Was it a translation into another language?

The story of the Queen of Sheba suggests the Amharic language tradition roots back to the Paleo language history as it existed in Solomon's day.

The Geez version, from which the Amharic was derived, would be more likely to match a Paleo text.

This process, of course, is only needed should we find a computerized version of the Ethiopian Bible text and then had some reason to go further with this study.

Paleo Double Colon

As we were studying samples of Amharic language Bibles we saw that the Paleo Colon is used as the current between word separator. We also saw 2 Paleo Colons used in succession as the sentence terminator.

Other variants of punctuation are also used. Often a colon is combined with 1 or more lines as other marks. Presumably these are the Amharic equivalents of English commas, colons, semicolons and perhaps other word gaps unique to Amharic vocalization.

We could easily see how special punctuation in Amharic is more frequent than in any other script we know. Amharic has a robust family of between word marks.

So this caused us to stop and think about what nuanced meaning these marks may be indicating. Most other written languages don't care about this specific level of detail.

Since this is a double end of sentence marker, presumably there is some special type of end of sentence that inspired writing would want to flag.

What might that be?

The most interesting candidate for this would be a question mark. A double Paleo Colon may very well mark the end of a question. (Or perhaps like Spanish, frame a question or perhaps mark the start of a question.)

I have adjusted the kerning tables to include this case on the expectation that this is how questions are marked. Audit work will uncover if this is actually used in the text.

This does not change anything else in terms of the overall system design. There are no changes to the 3d system needed for this. If a double Paleo Colon is inspired, they will appear as if by magic in the audit work here soon.

Followup To Last Week's Blog

We have been looking at the Iran war for the past several weeks. There is a good chance that this war, or at least this venue, is mentioned in Revelation 9. There is a strange variant in the Aramaic text for one of the key verses in this story. In is important to note for readers here who may also be thinking about this war and these prophetic stories.

Revelation 9:11

The link here is to the troubling verse in our VR app. This app shows off a bunch of different texts in interlinear format. It is designed to show 1 verse at a time.

If you have at least the VSP and any of the Greek based English texts turned on, then you can see the last word in this verse in both Aramaic using Paleo characters and then Greek based translations of the same verse.

This verse is about the king over the bottomless pit. In most texts the last word in that verse is the name of that king, so Apollyon.

In the Aramaic based texts the last word is still a name, but it becomes Sha-Re-Wa in Paleo. This will transliterate into English as Sharia. There is no reference to the name Apollyon in Aramaic. The name of the king over the bottomless pit is "Sharia." The word passes Paleo audit, but the sentence may or may not pass audit. Ask me again in a few weeks.

The war against Iran is by the Zionists. They are attempting to defeat who? The Shia of Iran. What law do they follow? Some variation known as Sharia.

What text we use matters to how we understand the world. More on this strange point once the audit is further along.

Story Grid

The link here is to the Story Grid app. The permanent link is on the front page at Paleo.In. This was previously called the "400" app. It now has 625 theoretical stories on the grid.

This week Ryan has made a significant change in the order of some of the central rows in this app. These changes also show up in The Testimony app and the Sabbath Reads app. Watch for changes to all of the scripture apps as this blog goes out on Friday.

Moving Minor Prophets

The first change is how the row of Minor Prophets has been raised up in the table and now fills the Ha row, starting at story 200. All the other rows in the Old Testament have been shifted down by 1 row. So conceptually, the entire center of the table has been changed.

There is a reference to Amos in the Book of Tobit. Normally, internal book references are against books which have already been written. So Amos must have been ahead of Tobit. This hints the entire set of minor prophets are also ahead of Tobit. So there was reason to push this row up. The question was where?

The current thinking on the Story Grid is that historical narrative runs through the fall of Jerusalem at story 199. This is the far right of the Jo row. Then what follows the historical narrative are the detailed back stories as written by the prophets.

So the minor prophets now come first, landing on the Ha row starting at 200. Then the major prophets, Isaiah and Jeremiah on the The row starting at story 225.

The minor prophets may have all been written before the Assyrian Deportation, but proving this is hard. Isaiah is coincident with that deportation, so may have been written after the minor prophets. Jeremiah is coincident with the Babylonian Captivity, and naturally follows Isaiah.

Moving Tobit

The other change this week has been shifting Tobit to the front of what is now the Yo row. By this change Ryan is suggesting Tobit was chronologically ahead of Esther and Ezra.

All of these changes cause the prophetic writings from Habakkuk to Job to fall in what should be a chronological order. Ezekiel and Daniel are currently left at the end of the Old Testament. This in part because these books, especially Daniel, give timing for the gap and details about the New Testament which starts in Luke.

There is still more work to prove this arrangement. This is at least another step towards solving this riddle.

Thinking About Revelation

With the Iran war there has been many people wondering about Revelation and if this war might be at least a precursor to Armageddon. Last week's blog was on Revelation in part because of these conversations. I only touched on Revelation. My hesitancy is with the problems of finding the inspired stories before trying to apply them to current headlines.

Revelation has a series of difficult riddles, in part because so much editing has happened to that book. Revelation must have been so frightening to Ananias that he had to layer on all sorts of distractions. He must have had good reason to obscure the inspired story.

So, Ryan took last week's blog as inspiration to see if he could settle the story list as found in Revelation.

Shifting the rows in the Story Grid was part of that work. Ryan also crawled through Revelation itself to see if he could spot the expected 24 stories that would fill in the 24 cells at the bottom of the Story Grid.

With the updates to the scripture apps that go out with this blog, Ryan has made a pretty good guess at those likely stories. This is certainly better than anything we've had before. Revelation has strong internal story pairing. These pairs work through both the silver series of simple alphabet folding and through bronze series, so the river exhibit, of letter pairing.

The challenge for reading Revelation is that it uses EVERY symbolic system from the rest of the text. It is like a final exam for advanced readers. It is referencing details from the various 3d exhibits. It is using advanced understanding of the timeline. It is including Ishmael's side of the Lost Tribes. It is folding back in various ways across the Story Grid.

Even deciding if a story in Revelation is a good thing, or bad thing, cannot be done without understanding all back references to other stories in the text.

Revelation assumes readers know the editors and the community in which they live. It explains their eventual destruction. It is the story of victory over the Zionists.

I expect to return to the content in Revelation in future blogs. More on that later. Interested readers here may want to survey this week's cut at Revelation in order to see where we currently stand on that book.

Code Work

I am continuing work on the Paleo Bible project. Still probably a few weeks before this can be released. I have been reworking code from 2024 when I first started looking at a full audit. This week I formally changed the way I am measuring text. Let me explain the problem and what this means for a permanent record.

Mechanical Design

One of the most important lessons when learning how to do mechanical design work is to know how to set the origin for measuring any particular project. Picking the correct origin can have major impact in later steps in a project. A wrong origin usually means measurement and design calculations are more difficult than they otherwise needed to be. Picking a poor origin can also make a design harder for humans to correctly understand.

Origin Principles

The 2 key principles are easy to remember. 1) Watch for symmetry. If a project has natural symmetry, the origin should be the point of reflection in that symmetry. 2) Watch for connection points to other parts. Especially watch for the most major mounting point or a base plate.

Picking the correct origin means the overall design will be easier to comprehend. By using natural symmetry, it will make the design easier to describe using design software.

As an example, think about the origin point for measuring an airplane. Ask yourself, where should zero be in the left/right, up/down, and front/back axis of the overall design.

Later on, individual parts can have their own unique design origins. This question is how should the entire plane be measured.

Airplanes have symmetry in the left/right dimension so the origin in that axis is easy to spot, down the middle of the airplane. Any design project with left/right symmetry should normally have an origin in the middle.

In airplanes, there is less symmetry in the other axis, so here it gets tricky. In the up/down axis, the main body of the airplane itself is a round aluminum tube. So the middle of that circle is a good choice for the origin on the up/down axis. Alternatively, the ground could be used. The ground is effectively a mount point or base plate for the entire airplane. But, the landing gear and tires causes the distance to the ground to be variable. So the ground is not a good choice for the origin in the up/down direction.

But what about the front/back axis? There is no symmetry between the cockpit and tail. So symmetry does not explain where to put the origin. In this case, there are 2 or 3 other choices.

There is a balance point, typically near the wings, that could be the origin. The balance point, though is an aerodynamic concern, not really a mechanical concern. So the balance point is not that interesting for the mechanical design.

Most airplanes also have an assembly point just behind the wings. The 2 parts come together during assembly. This could work as a mount point style origin. But that assembly point is not natural, and does not exist on all airplanes.

The tip of the nose is another possible origin. The nose is a "leading edge" origin, similar to a mount point. It is where the airplane first touches air. So this is like a base plate origin, but peculiar to an airplane's purpose.

With the nose as the origin, every other measurement back through the plane has a real world meaning. It is the distance from the front. This is a human proxy for the distance from the cockpit and pilot.

3d Model Origins

The 2d drawn shapes showing up on the writing canvas are projections from 3d objects. The alphabet itself is on the silver and copper series of "birds." All of the birds have origin points in the center of the 3d space that surrounds those birds. This also includes the bird cages, which are symmetric along all 3 axis. Mount points for support threads break symmetry in the final parts, so final parts are not exactly symmetric.

Birds are using a variation on the symmetry rule for setting the origin. Though most of the birds are not exactly symmetric, their measurement system is based on distances out from a center point. The space around the birds, including the bird cages, is symmetric. So there is good reason to set the origin in the middle of all of these parts.

2d Drawn Form Origins

So when I first set the 2d system for drawn letter forms, I set the origin point for the 2 forms to be in the middle of a square. This was basically a 2d projection from the side of a 3d bird cage.

There are also a set of 3d models of the 2d letters which are essentially designed this way. These letters are used on the dogs under the Table Exhibit. So using the center as the origin for letter design seemed reasonable when I first starting working audit code in 2024.

As I was working on code this week I saw that there is actually a hidden mount point that is NOT the center. By shifting the origin to that mount point, most of the calculations involving the drawn forms of the letters gets simpler. Let me explain.

Writing Surface

The 2d letters are placed on the writing surface. That surface is a long series of audit squares. The first letter, placed on the first square, will align the left edge of the letter with the left edge of the first square.

All successive letters are placed on the writing surface by aligning the left edge of the next letter with the right edge of the letter already placed on the canvas. This is called kerning. Notice how kerning does not care about the center. It does care about the left edge of the next letter and cares about current letter shape.

Eventually the line of text fills, and we move to the next line, starting the process over again.

If we want to check audit, the audit marks are on the canvas cells and those cells have a repeating pattern which starts again at each left edge of the underlying line of audit squares.

If the system is always based on left edge, the absolute left edge of any letter in a line can be run through a simple modulus 6 division to learn the cell location within an audit cell where the letter begins.

No Use of Centers

Nowhere in this process is the center of the letter all that interesting. The geometric center is at least 1 calculation away from the left edge. We must look up the width, and then calculate the center, so 2 steps of work. Depending on why, we may then need to repeat the process again for a target.

Properly set origins will, in the general case, reduce the amount of calculation needed when dealing with any object. The proper origin for 2d drawn letter forms looks to be the left edge, NOT the center. Left edge based calculations are obviously better and match the theory of why setting origins is so important.

In the very rare cases when a center is needed, half the width is used to find the center. The only case where this matters so far is for general exhibits when showing a 2d drawn form on a square drawing canvas. This is only done when pointing back at the 3d exhibits. This is not used in normal writing.

Shifting Left

Once I could see this problem, I stopped and went through all the basic geometry and a set of other useful values and shifted origins to be the left edge, so the leading edge, or the nose cone, of each letter.

It was tedious work, but the results were very nice to see. We will eventually be running the entire manuscripts through audit code, and keeping the code as clean as possible is very important, for speed, and for trusting the answers.

Refactoring Code

I am also adjusting the files to put all geometry and audit related code into a separate library. This so it can be used for 1) manuscript wide audits, 2) build related specialized pages and also 3) in the app for generating detailed lexicon reports on the fly for specific words.

I don't normally worry to much about heavy notes. But this code may eventually get reviewed by others, so I am paying more attention than normal.

Specialized Fonts

The current work is generating blocks of SVG that can be displayed in web pages. This will become an appendix in the Paleo Bible. It will be used to show off all of the internal data surrounding every letter, audit pattern and all the related kerning pairs. That appendix becomes a visual way to test the code and verify all the design decisions used across the audit process.

I am also working out marginal notations, so subscript and superscript marks, that indicate how base words pass and/or fail audit. Those marks first show up in the appendix, so will be drawn along with large size letter and kerning related artwork using simple SVG.

For the main running text, SVG is not the best tooling. In that case we plan on extending our base Paleo font. That font work can only start once I am happy that the letter related audit marks work as needed to explain the nuances of the audit. More on this in future blogs.

Match Dates

This week we were watching for the replay of the last year of Asa and the first year of Jehoshaphat's reign. Asa was done on the 24th and then Jehoshaphat's reign started on 2026-04-25. The best headline at that point seemed to be out of Ukraine. Here is the link.

NATO Air Battle Against Russia

The link here is to a Military Summary channel video on Youtube. This is dated 2026-04-25. This particular video covers the details of a UK fighter jet operating over Ukraine territory very near Romania. Apparently that jet had taken off from a base in Romania. It was targeting Russian drones in the very south western corner of Ukraine. Unclear what the Russians were specifically targeting, nor why the UK would be fighting back.

This video dwells on this event because this appears to be the first formal attack by NATO forces against Russia. Nearly everything so far is NATO using Ukraine as a proxy. Not here.

As we now see Kiev as the venue for the start of Resurrection Sunday headlines following World War II, this venue appears more important than before. This may have been related to whatever reason the king visited Trump. Links on that below. Presumably European Zionists see fuel and funding running out with the closure of the Strait of Hormuz. So they need to act now. These 2 war fronts are the same, as Revelation might also suggest.

Iran War

The world has remained on edge over the possibility of a restart of the Zionist war against Iran. The Zionist war against Lebanon has continued from Israel without interruption. Trump was never able to get Israel to stop shooting. So the possibility of this being a 5 month war as matching Revelation still remains open. The Zionists have not stopped shooting the Shia.

The Iranian Foreign Minister visited Moscow. Iranians have been threatening to restart if the Zionists don't lift their blockade. Iranians have opened new supply lines on the ground via Pakistan. For ethical reasons they may wait until Trump shoots first, before firing back.

The nightly rallies in Iranian cities have continued non stop since this began on February 28, 2026. These rallies might be another way for counting the time for a 5 month war. We will see. It is still too early to know for sure.

As this blog goes out there are several strong rumors of a Trump order to restart war against Iran, either on Friday or Saturday, so by May 2, 2026. There are also reports that Trump waited until now to restart the war so his 60 day war powers clock that he has used for the first round is reset starting this weekend.

Zionists have no choice but to restart at some point. They need to control oil to pay for their empire. They cannot have an Iran government that they do not control via Zionist puppets like Trump himself.

Watch Dates

Peeking ahead, the next date from the king's series is 2026-05-19 with the replay of the last year of Jehoshaphat's reign. We will return to this as we get closer.

Peeking way ahead, the Assyrian Deportation will replay on or near 2026-11-09. This was the most important near term story in the general history of the kings.

Headline Review

The following caught my attention this week.

Trump's Assassination Attempt

The link here is to a Youtube video that details issues with the Butler assassination attempt against Trump during his campaign.

Nobody trusts Trump anymore. Suspecting secret games in public events has become a popular spectator sport. This link just for the record.

Other reports indicate this was an intentional ceremony anointing Trump as Aaron. See Exodus 29:20 and Leviticus 8:23. If staged, then this was an intentional Epstein class human sacrifice for Trump as a type of high priest. It was made to look like a miracle saved Trump. Instead it was another Epstein Class human sacrifice of someone in the crowd.

Will Be Shots Fired

Staged

The top link has a clip of Karoline Leavitt's remarks at the hotel ahead of the White House Correspondents’ dinner when there was yet another assassination attempt. This is called a "Freudian slip" and suggests she knew something was planned. Political theater to garner sympathy? Trump used this to defend the need for a ballroom, really the roof for some sort of AI control project at the White House.

The second link cites Larry Johnson's claim this was a staged event. He had multiple reasons, Larry was on the podcast circuit with more details.

Tehran Airport Reopens

The link here has a photo of the flight board at Tehran airport dated April 25, 2026. Flights have resumed, so Iran is returning to normal. Other reports suggest life in Tehran is mostly normal. Schools remain on remote learning for fear of surprise attacks by Zionists.

Lavrov: War On Russia

This link is to an Alex Christoforou daily news brief with details on Lavrov indicating the EU has declared war on Russia. This is an obvious truth. The point is the Russian government is now saying so explicitly. This would match the UK fighters working in Ukraine airspace. Watch for fireworks later.

Population Shift In Israel

This link is to a post on Telegram detailing the population shift in Israel. This is one of many sources covering this point. European Jews are leaving because of the war. The population is now majority Egyptian Jews. (They transliterate Mizrahim to just Eastern Jews, but we know better. This is the word for Egypt.)

UAE Out of OPEC

OPEC is located in Vienna, Austria. This is the international organization for the lost tribe of Jacob's side of Asher. Want to buy a tanker of oil? In person? Usually, you want to travel to Vienna for that. The reference for this is Deuteronomy 33:24, where Asher's feet will be bathed in oil.

OPEC is a cartel that limits supply in order to drive up price. In the real world, without a cartel, the price of products generally matches the "marginal cost of reproduction." This is a technical term from Masters Degree level Economics.

This means, amongst other things, that left to its own devices, the oil markets in the world should not generate excessive wealth because the price should approach the cost of oil coming out of the ground.

OPEC breaks economic theory in order to fund ultimately the entire Zionist western world. This is what Iran must accomplish, they must break OPEC. There are several different possible strategies for this. We will see what they ultimately do.

King Charles In DC

White House Beehive

This is a link to a short clip dated April 28, 2026. This is just a reminder for the record that the king visited Trump on this date. His speech was fun. But why did he feel the need to visit Trump at this time?

Most likely, this is a European Zionist meeting to deal with future strategy. Some high level issue that could not be handled any other way. Like Netanyahu's visits to Trump, the king is probably giving orders for war to break out with Russia here soon. Perhaps the king is replacing Netanyahu as Trump's handler.

The second link is the king with Trump and wives at the newly unveiled White House beehive. Hive is the symbol for the Hivite, or the serpent in the garden. This probably has some occluded meaning beyond the obvious textual references.

Iran War Strategy, 2019

The link here is to a full translation of a speech by Martyr Qassem Soleimani, months before his assassination, in May 2019.

The key point is the Iranian war strategy is to close the Strait of Hormuz as a way to bring down the west. This is a type of warfare aimed at bringing down the financial structure of the western world.

Oil profits are essentially captured by western bankers in order to fund the Zionist empire. No oil, or no oil cartel, means there are no excess profits available to fund the west. This is the way Iran can bring down the west. They have known it for a long time.

The UAE leaving OPEC, linked above, means they will price oil at or very near their own cost of production. Note this means very thin profits, so no excess funds to pay for the Zionist war machine.

Chinese Public Support for Iran

The link here is to a post on Telegram with a short video showing a crowd in support of an Iranian sports team in a Chinese stadium. The public around the world is on Iran's side. The Revelation passage related to Iran suggests the world will cheer when Babel is defeated. This link is an example of what will happen.

Merging Militaries

There is a bill floating around in the US Congress (HR8445) that would cover US Citizens serving in the IDF as though they were serving in the US Military.

This is starting to formally connect the genocide in Palestine to the US Congress, as if there weren't already enough ways to do that. This impacts how we think about stories in Revelation. Babel falls in various ways, including across the seas.

More Later,

Phil