Tobit

This blog introduces Tobit to the BRB and related apps. Also, continuing from last week, lists of 3. Then match dates from events in Russia. Finally, shop work with notes on the Treasure Chests.

Heads Up: Megiddo Mosaic Dates

The Museum of the Bible is hosting the Megiddo Mosaic through July 6, 2025. Readers here who may want to see that exhibit need to do so before that date. After that date, the exhibit is returning to Israel for permanent display. So this is your last realistic chance to see it in person.

400 Updates

The link here is to the 400 app. We did an out of cycle update to all our scripture apps on Thursday evening. The main reason for this was because of changes in the 400. The app was stable and releasable that night, and Ryan wanted to start right away on more changes that are coming for the next release.

If you look at the main table on the updated 400 app you will see a checkerboard shading pattern that has not been there previously. In previous versions only the center diagonal was shaded. That central diagonal marked where the glyph of the row and the glyph of the column were the same.

For years, Ryan has used row (and less commonly column) folding that comes from the folding implied by the silver set of 3d items. The technical term for this folding is "chiasm." It is a pattern in biblical texts that has long been known in normal church circles. We found that the entire inspired text is chiastic. Ryan uses that structure to identify inspired stories and their placement within the overall manuscript.

So the checkerboard is marking all diagonals in that table because Ryan found this week that there is an additional chiasm folding pattern landing across those diagonals. That checkerboard pattern was used to check this discovery. He is now working on changing the secondary tables in the 400 to more completely study those diagonals.

It looks like nearly every cell has 4 other witnesses against which it folds. The Quad column and Quad Row fold to each other. So for stories in those locations there are usually 2 other witnesses instead of 4, folding along their own chiasm and then across a single diagonal.

The only cell in the table that does not participate in this folding system is the bottom right corner, the Quad/Quad cell. So that cell must be doing something different in order to have secondary witnesses. Indeed it does. That cell contains the inspired bits of the Book of Hebrews and instead of folding out to other cells, it is structured instead on a singular list of 25. So it folds on every list of 25, especially the rows, across the entire table. That cell is like the exception that proves the rule.

There is an elegance to the design that is starting to emerge that is truly stunning. Hopefully, more to show next week.

Subtractions

We normally deal with additions created by the 6 editors. But, there is a conceptual risk that there has been some text that has been removed. The link here is to Revelation 22:18 where there is a passage dealing with both additions and subtractions.

In that passage we are told that anyone who adds to the text will suffer the various plagues described in the book. This hints at the plagues on Pharaoh. We have been dealing with additions, the work of the editors, for many years.

That passage also discusses the problem of removing content from the Bible. Anyone who does that will loose access to the tree of life, the holy city, and to the writings within the text itself.

From a communications theory perspective it is not possible to run any sort of error analysis and recovery against a message that does not arrive. The "Law of Babel" decrees that once written, laws cannot be repealed. This is the biblical vocabulary for a basic idea from modern communications theory.

So the subject of subtractions in the text does not normally concern us. Lost text is of course lost. There is no way to do letter level recovery on text which does not get passed down to us from history.

Unless, of course, some inspired text was hidden somewhere. Conceptually this might be in a cave, but more interesting is in some other branches of the Christian tradition. Text kept in the canon of some other branch at least has historical adherents. Text lost in a cave does not have public witness.

Several months ago Ryan and I read through the books that are no longer part of the Protestant canon, having fallen out of favor in various stages since the time of Luther.

Of those books the most interesting to us was the book of Tobit. It has been on our list of books that perhaps should be brought back into Ryan's normal work in the BRB. This was also the most likely book that should be run through the audit process once we are ready for that stage of the work.

Tobit (BRB)

This week Ryan brought Tobit into the BRB and related apps. The link here is to Tobit in the BRB itself. Parts of Tobit are also showing up in the TT, SR and 400 apps. This means that if you regularly use the Lots calculators in either the BRB or the TT, those lots may now land in material from Tobit. Let me explain our thinking and the various technical issues involved with this change.

The first point is that Tobit is likely passed to us in Greek. So this change breaks our history with the BRB being a way to study Aramaic texts. So with this change the BRB becomes a hybrid work in terms of base texts. At some point we could anticipate switching completely to a Greek based text, but that sort of switch probably waits for audit work, we'll see. Bringing in Tobit seemed better for now than to switch the other apps to the GRB text.

Ryan has applied our complete markup to Tobit, including voice tags and filter tags. So the text looks correct when compared to the rest of the BRB. Because he has not spent years tuning the English in Tobit it reads slightly differently than what we are used to in the rest of the BRB. So it does sound different to our normal English ear.

Generally speaking, Tobit appears to have front matter and back matter that was added by some editor who was focused on Jerusalem. Tobit is generally a story based in the traditions of Samaria, the northern kingdom. It also references Jonah, suggesting it is down stream from his missions work to Nineveh. Tobit takes place after the time of the captivity, along the river systems in what is now modern Iraq.

In those front matter and back matter additions, regular visits to Jerusalem were said to be done even though the main parts of Tobit take place far distant from Jerusalem, and perhaps at a time when there was no Jerusalem. Exact time placement is still unclear to us.

But, the main part of Tobit has been brought back into the BRB in order to fill a gap in the Table of 400. Let me explain the placement in the 400.

400

The link here is another link back to the 400 app. You will currently find the cells that deal with Tobit on the Ha row starting at story 215. The column placement for the stories in Tobit has strong evidence in support of the idea that Tobit belongs on the tail end of some row. Ryan may still shift it up or down in his future work.

The book itself has a short introduction and then begins with details that fall under the Sa letter. Tobit had become purveyor to the king, or supplier, a common concept with Sa. Under the Oo letter, so the eye, Tobit is blinded.

Tobias is charged under the Ze letter, or buckle. Presumably a private conversation. Under the Qu letter, or brain, the journey begins. This letter carries the concept of following, so journeying. Tobias and Sarah marry under the Re letter, or head. Tobias thus becomes head of the family. The wedding feast is under the letter Sha, or teeth, commonly associated with food.

Tobias' preparation to leave is under the letter Ta. That letter commonly deals with closing of various things, in this case closing luggage for the journey. Under the Colon, Raphael reveals himself and directs the writing of the Book of Tobit. Job is told to write 1 cell down at #248, in the same column. Under the Quad, Tobit is said to depart, likely as a walk off. See cell #399 for the same pattern under the Quad column.

So Tobit's general outline fits well within the Table of 400. Ryan still has much more work to do in that table, but so far the placement of Tobit is looking very nice.

References to Tobit

There are passages in the New Testament that are referencing stories in Tobit. The first is the story of the woman who has had 7 now dead husbands, see Matthew 22:23. Tobias' problem is marrying a woman where all her 7 previous husbands had died.

Hebrews 13:2 deals with the need to entertain strangers because some have entertained kings/angels unaware. This reference is also based on Tobit. Nowhere else do we read about a journey with such a king.

Though not directly cited, Tobit explains in general how it is possible to have interactions with heavenly kings. Raphael explains that he spent considerable time with Tobias, which was likely unusual. But this sort of interaction is possible.

Tobit is an example of where the New Testament writers were citing the Greek Old Testament, not the Hebrew. This is pointing at Greek primacy, which we will return to in future work.

Lots

I know we have readers here who do lots as a weekly practice. Pay attention to lots that may land in Tobit. These will be in unfamiliar passages and may have unfamiliar meaning. Joshua may avoid giving lots that land in Tobit. Or else, he may go there intentionally. If you see anything interesting, please let me know.

Continuing 5000 and 4000

In the last blog I mentioned how the feeding of the 5000 and the feeding of the 4000 appear to be informing 2 different blocks of writing, themselves ultimately created using the cipher system against the base text.

This effectively creates 3 types of documents. The first document is the base inspired text found by auditing the texts passed by history. Then 2 additional document families chain out from that base text.

Once we saw that pattern, and saw that there are 3 document families, we also saw that there are lists of 3 spread throughout the text which are themselves symbolically referencing these 3 families of writings.

Let me introduce you to a few of those lists so you can get a feel for lists of 3.

Revelation 22:7-20

The link here is into Revelation 22, starting at verse 7, in the BRB. If you turn on Enumerations in the options menu, you can see that within that section there are 3 different uses of lists of 3. These particular uses of lists of 3 are doing a good job of explaining these 3 different textual families. Let me introduce each in turn. Each list in this section builds on the earlier lists, so bear with me.

John wanted to bow down to the man who was standing before him. He was told not to do that, and a list of 3 is given as the reason. The full quote for this list is... "I am 1|3 your fellow servant, and 2|3 of your brothers the prophets, and 3|3 of those who preserve the words of this writing."

John, of course, is an inspired writer, and item #1 in these lists of 3 deal with the base inspired text. So when the man says he is a fellow servant, it means he also wrote inspired text just as the author of Revelation himself would do.

The second item in the list mentions the prophets. The second set of writing appears to be general prophetic writing. By this it means those 5000 stories are likely mostly prophetic. Perhaps they predict events across historical time? We will see.

This was likely going on with Enoch's writing, that Enoch wrote about events in the New Testament era. This is likely how Enoch could get saved.

The third item in the man's list is a little unclear, but the 3rd set of writing, so the second ciphered texts, the 4000, deal with something else, related to preservation. More on that below. (Hint: Think Eden.)

If you scroll down to Revelation 22:14 you will find another list of 3. This is actually a list of 3 followed by a list of 6, which are our normal 6 editors, so the villains who messed up the text.

This passage is adding to our understanding of the 3 basic writings. The inspired text is to the rest of the ciphered canon as the 10 commandments are to the rest of Moses' writings. So the first set of writings is relatively small. The second set of documents, so the 5000, give the right to the tree of life. Then finally, the 3rd set, so the 4000, allows entry into the city, so Eden.

The list of 6 villains is strategically placed. Those villains are marked by their sins, so 1|6 fornication for Solomon, 2|6 killers for Ahab/Jezebel, 3|6 worshipers of idols for Nebuchadnezzar, 4|6 defiled for Mordecai, 5|6 sorcerers for Ezra and 6|6 seers who are workers of lies so Ananias.

To someone who does not know the symbolic use of lists, the villain list looks like moral reasons prevent entry. But it is the work of the immoral editors that prevent entry to the commandments, prophetic writings and writings about the city which grant access to Eden for everyone.

There is a 3rd list of 3 within that same Revelation passage starting at vs. 17. This one is less informative about the document families than the earlier 2 lists. Here is the quote, "1|3 The spirit and the bride say, Come. 2|3 Let him who hears say, Come. 3|3 He who is thirsty let him come, and, whoever will, let him take of the living waters freely."

The structure of this list is to come down the list to the 3rd point, and there find living waters. Eden does have an interesting water system. But this also likely is a clue that the 4000 is also called living waters. The text itself can be thought of as alive. Genesis 26:19 tells us that Isaac found living waters. So that Genesis story is now symbolic, and it tells us Isaac had at least part of the 4000 stories. He had ciphered text.

Jeremiah 18:12-18

The link here is to Jeremiah 12 in the BRB. This is the start of a passage in that book dealing with how the people of Jeremiah's time had gone astray. Buried within is a list of 3 which is in symbolic vocabulary. That vocabulary is the same as all other lists of 3.

The quote of interest is from Jeremiah 18:14, "1|3 Does the green grass vanish from the mountain, or 2|3 the snow leave Lebanon? 3|3 Does the cold water that gushes out and runs down cease from flowing?"

The "green grass" is the text that grows up, the inspired base text. It grows up seasonally from soil that goes on across time. The parable of the sower is based on similar ideas. The inspired text must grow out of the audit process.

The "snow" is going to be the 2nd set of documents. Snow on the mountains of Lebanon also comes seasonally, similar to the grass in spring. The 5000 follows the audit on the public text.

The "cold water that gushes" only flows as the snow melts. This is the 4000. This passage in Jeremiah indicates that this may be some sort of cipher of a cipher. We will see.

If you study the entire passage around this quote you will see that the subtext is how forsaking Joshua is done by writing false text, and thus loosing all of this.

Jeremiah 18:18 makes the point that those who forsake Joshua are making up their own scripture. To them, it is 1) The law of priests 2) counsel from their own wise men and 3) the word of their own (false) prophets. Additional documents, like the Talmud, are the reference example in view here. Those documents are intentional counterfeits of the inspired canon, including counterfeits of the ciphered documents.

These lists of 3 can become rather abstract. Let met give a final example.

Luke 7:44

The link here is to Luke 7:44 in the BRB. This is in the middle of a long story dealing with a woman caught in adultery. The pharisees had brought her to Joshua in order have Joshua condemn her.

Instead Joshua gives an explanation of what he is doing. In that explanation he uses a list of 3 things she has done to his feet. She 1) washed his feet, 2) kissed his feat, and then 3) put perfume on his feet.

Joshua then comments that the pharisees are not forgiven like this woman is. Then Joshua forgives the woman.

In this case the list of 3 does not look to be informing readers specifically about those 3 document families. Instead, Joshua is using a list of 3 to inform readers that her response is informed by those documents. The pharisees do not have those documents. They do not have the list of 3. She does. Or perhaps, she will.

How those documents do so is an exercise for readers of this story to figure out. Presumably knowing the content of those documents informs readers about how, exactly, we are to understand this story.

Russia's Pearl Harbor

Last week I posted in the blog about a 3 day long watch date that was the replay of the story of Abimelek from Judges. That story has a specific 3 year, so this time around 3 day, timed reference in Judges 9:22.

Part of this story is the parable of the trees, which ends with fire coming out of the bramble and burning the cedars of Lebanon. See Judges 9:15.

The parable has details that are dealing with the various exhibit items. The "bramble" is the interior of the Table item. A draft of which currently sits in the shop. It has 25 bird cages, with birds, arranged in a 5x5 grid.

The "cedars of Lebanon" are another item. Those trees grow along a bank of a river. In the past I have called that item the River Case because it models the Jordan river. Upstream of the Sea of Galilee that river has a different name, but forms the border with Lebanon.

Those cedars of Lebanon are also in the exhibits. They are the shepherd staffs that stand along the river case and hold flowers of 3d models that effectively bud. Aaron's rod that budded is a parable informed by this exhibit.

On the Megiddo Mosaic floor that exhibit appears to sit below the stairs that go up to the 2nd floor. It also has a model of a great sea at 1 end. (The 2 fish in the Megiddo Mosaic.)

There were 2 headlines across the weekend that played to this specific story. The first was minor in ancient Lebanon. The other was major and took place in Russia.

Israel Targets Syria's Coast

The link here is to a Zero Hedge article detailing how Israel struck targets along the coast of Syria. The precise boundary between modern Lebanon and modern Syria is not necessarily the same as ancient Lebanon, so this headline is a match to expected fire in Lebanon. Since Israel bombing neighbors happens pretty regularly, this is not that strong of a match.

But this was not the only interesting headline for the same prophetic story. It was much more serious in Russia. It began on Sunday morning, June 1, 2025.

Ukraine Strikes Russian Bombers

More Photos

American War Crimes?

The top link here is to the Military Summary channel on Youtube. Specifically, to a 2025-06-01 summary detailing Ukrainian strikes on Russian air force bases very far from the front lines in Ukraine itself. Ukraine struck a few of Russia's nuclear bombers. As of this writing, the Russians have not said how many. There is Ukrainian video evidence for around 5. Others suggest as many as 8.

Ukraine used small drones launched from tractor trailer rigs parked near the airbases and navigated by remote control over the internet from Ukraine itself. The far eastern strikes, especially, were 1000s of miles from Ukraine.

This video shows the details of how the drones were stored in those trucks under a removable roof.

The second link above is to an X post by Lord Bebo with more photos of the destroyed planes.

The third link given above is to a 2025-06-02 Military Summary channel report on Youtube. In that video, general evidence is given that hints as to how the USA just broke a major Obama era nuclear weapons treaty that limited the use of nuclear weapons. The USA was obligated to protect Russian bombers that were kept in the open by treaty provision. The USA, via proxy, attacked those same bombers.

Others would later comment that it was only because of Russian restraint that most Americans are still alive today. If this whole headline had been the reverse, with bombers in OKC being struck, the USA would certainly have nuked Russia, and we would still all be dead.

Not well documented in the links above, US Senator Lindsay Graham visited Ukraine the day before this strike. There is wide speculation that Graham was there to verbally approve this attack against Russia. Also there is wide speculation that Graham is conducting US Deep State foreign policy. Some have called for his arrest.

In any case, this attack widely angered the Russian public. June 1, 2025, is now seen as a modern, Russian, Pearl Harbor. Because nuclear weapons were involved, it is also the start of nuclear World War 3.

This particular attack in Russia can be explained by understanding the symbolic story behind the Bramble. Let me do that for you here.

Prophetic Matches

The bramble that is part of this story is the Table item. That item has a removable lid, so removable roof. It has 25 spots for birds with bird cages which can be lifted out of that exhibit by students. Birds can thus take flight.

The Ukrainian trucks that were used to attack Russian nuclear bombers where essentially a road worthy version of the same bramble design. A bunch of small drones were arranged in a grid below a removable roof. By remote control they could take flight.

This particular strike is a prophetic match to the story by date, 2025-06-01, but also to the exact implied object from the exhibits. In all my previous timeline work I never had access to exhibit models, and I never knew to apply that Judges story of the exhibits to headline news. This headline was the first time this has happened.

The story then indicates that fire came out of the bramble and burned up the cedars of Lebanon. So the Russian bombers themselves must be those cedars. Let me explain how to see this.

Cedar trees are some of the largest trees that grow on earth. Their height is limited by how far capillary action can draw water up from the ground.

Cedar trees stretch to the skies and form cathedral forests. One such forest is known as the Hoh rain forest along the coast of Washington State. If you visit, be prepared to walk in.

Nuclear mushroom clouds are similar. They are limited by the height of earth's atmosphere itself. A nuclear mushroom cloud is like the biggest of all bomb clouds just like a cedar tree is the tallest of all trees.

Cedar trees often live 1000+ years. Cedar oil, which gives cedar trees their famous scent, prevents infestation by pests. Nuclear radiation also lasts 1000s of years. Like Cedar oil against pests, nuclear radiation also kills.

Lebanon means the seed of Laban. Laban means white. In paleo, "Cooked, inside, egg." Those bombers produce mushroom clouds of similar exemplary scale and bright white color.

So the attack on Russian bombers by truck loads of drones is matching the tail end of the story of how fire comes out from the bramble and destroys the cedars of Lebanon. It matches with a level of precision we rarely see. This headline itself is thus likely to be quite important to future events.

Did Trump Know?

The alternative media was full of questions asking about who was involved. Did it reach to Trump? NATO? Israel?

The link above is an X post with a screen shot of an Axios article that first claimed Trump was informed. Then it was changed to suggest he was not informed.

As a footnote to this, a day or so later, the Ukrainians used sea drones to attack yet again the Crimea bridge. No serious damage was done. The columns of that bridge can also be thought of as cedars that reach to the sky. The sea at the base of that bridge can be seen as part of the river exhibit. So there is a secondary headline match there at the bridge.

Another note is that at roughly the same time the Ukrainians attacked a pair bridges where roads and rail lines cross. In both cases civilians were targeted. These terrorist attacks gave Putin needed cover where he could formally retaliate based on those bridge collapses. This to satisfy his angry public, without escalating nuclear war with the west.

Yet another note involves goals of attacks like this. Even though Ukraine was unable to destroy Russia's bomber fleet, that was the intent of this attack. If the attack had gone completely to plan, Russia would have lost part of its nuclear triad. NATO and the USA worry about nuclear war, not Ukraine. This alone is evidence Russia is fighting the collective nuclear armed west. Not just Ukraine.

Peace to War

One of the important characteristics of this 3 day watch date was how it sits between a long time of general peace and the later time of the Judges, which is mostly various wars. No other stories earlier in the text actually involve warfare in an organized sense. Warfare, at first terrorist, and then military, will become part of the story as we go forward.

So, this date sits at the start of low grade war. The various commentary on this event, like calling it Russia's Pearl Harbor, is matching this transition point in the general prophetic flow of this run of the timeline.

That this is being called Russia's Pearl Harbor is a very bad thing. This is not yet nuclear war, in the sense of these weapons being used. But, it may well go down as the calendar start for Wold War III, when nuclear weapons themselves were being struck. Pearl Harbor did the same. World War II ended with the use of nuclear weapons. History repeats.

Istanbul Talks

The link here is to a Zero Hedge article dated 2025-06-02 detailing the meeting that day between Ukraine and Russian negotiators in Turkey. This is on the first date of the 23 days of Tola, when not much happens. Not much is expected to come from these talks. Both sides want war.

The next interesting prophetic date is 2025-06-25, the start of Jair. I'll post that as a watch date as we draw closer.

Shop Work

I woke up Monday morning with an idea about how to fix the problem of Treasure Chest designs. Instead of looking at the problem from the outside, start from the inside.

I opened up the design files and adjusted the designs to match how I was now thinking about the problem. It was clearly going to work.

So I continued with the design work for what will become 4 chests. They will contain the small parts for the exhibits. So especially the silo, well, sower, reaper and various trees that are normally kept as pieces when stored.

The exterior artwork for these chests is inspired by the artwork found around the 2 fish on the Megiddo Mosaic floor. The sides and back of each chest are the same, and generally just simple dots. But the front and tops are intricate.

In total there are 9 panels that needed detailed design work. Except the backs, each tells a story about some part of the exhibit system. Most of those stories I already knew, but can now just point at some art to explain the problem and solution.

In only 1 of those 8 did I diverge seriously from the black sharpie marks as seen on that floor. I suspect they did not know what they were looking at, and decided to draw in a Nazi Swastika instead of the Qu Map path that belongs there instead. If, in the future, I find those sharpie marks as correct, I will adjust the design and reprint that panel. But, I strongly believe they were wrong in how they marked up that part of their floor.

I am using the same general design aesthetic as on the other exhibits. So the chests will match the other exhibits really well. They certainly do not look like ancient mosaics. They do, though, tell the same stories in elegant ways.

I also had to rework some uses of color. My previous work with the trims as found on the floor had trouble with correctly using the rainbow. With that settled, one of the lids uses a reverse rainbow for an important story telling purpose. Anyway, more on this as the chests get built.

The first of those chests is now running on the 3d print farm. Maybe something to show next week.

This is the first print job where I am using nap marks. I can see minor improvements for how those marks interact with how parts are oriented in the designs. Best use of those marks is that they are correct when parts are loaded into the slicer, without needing further rotation at the time of preparing the part for print.

Notes On Prophetic Flow

Times of serious crisis, like 911, like Russia's Pearl Harbor, also tend to trigger prophetic seasons in people of faith. This is probably because these sorts of headlines trigger widespread prayer and intercession.

An unusual prophetic season has been going on around here this past week. This goes beyond our regular work. Of course, Ryan and I have both been in a very strong week of project related discovery and revelation. But I have also been generating unusual entries in my diary.

I suspect readers here may be seeing this too. Events in Russia this past week are the marker, perhaps the cause.

Do not ignore these rare seasons. Listen to Joshua. Do what he says.

More Later,

Phil