Arise!

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