Lexicon Insights

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