Story Grid Updates

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?

Telegram

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