Trump

This blog looks closely at Trump's Big Beautiful Bombing. It looks like he is Jephthah. We also look at the NATO summit, a double header week. Before that, more updates to the 400 app. Finally more shop status and a couple interesting tech related headlines.

400 App

Ryan has continued to update the 400 app this week. Last week he had dropped the secondary tables in favor of a single long table that listed parallel data for each of the stories in the app itself.

In diving into that view of the problem he found several additional bits of data that he wanted to track for each of the 625 stories in that new secondary table. There is now a total of 18 additional bits of data for each cell, usually expressed as references to other cells.

This additional data comes in part because he is using the Vine exhibit which stands in the shop. That exhibit indicates that all stories of the same vowel should be expected to have some affinity. By inspection in the finished rows of the main table, it looks like they do.

This additional data was blowing out the user interface for use on small devices like phones. It was also causing trouble in terms of the manual book keeping needed to keep that table current.

So this week those problems were fixed by busting out each cell from the main table into a set of secondary report pages. There is now one report page per main table cell. So 625 pages have been added into that app.

This gives the freedom to use a whole page for whatever data and notes that may be needed for each story. It gives each story a unique page, which makes them each a unique URL, so those pages can now be linked from other apps.

The text for each story remains in popups. There is 1 popup for each story. But since stories are showing up all over, worst case, there is something like 625 * 18 = 11,250 squares spread across those report pages that trigger popups. With this new setup, each reference to a story doesn't need to contain the whole story, over and over again. They just call out the story popup.

Each story popup links both to the cell in the main table and to the report for the popup. So the whole experience is fluid and easy to move around.

Most data is still not loaded, but you can play with the app and get a feel for where it is going. Use the link above to see for yourself.

Internal Tooling

In order to manage the data complexity Ryan has also configured his main template tool to handle this problem. The other scripture apps, in particular, are data driven. He has a set of master configuration files that are used to populate HTML pages that show up in all the various apps. In those other apps this means he has what is called "Single Point of Truth" for the entire layout of what stories constitute the TT and related apps. That is now going on for the 400 as well. This is all very much easier to handle and should allow him to focus on solving the riddle and not getting bogged down in maintaining the app itself.

There is still a bunch of hard manuscript work still needed for solving the problem of finding the inspired set of stories. But at least the tooling needed to solve this problem is now in place and not getting in the way.

Trump's Big Beautiful Bombing

Late on Saturday, June 21, 2025, US President Trump bombed 3 nuclear targets in Iran. This was the near term end of what currently looks like 12 days of fighting between Israel and Iran. Israel having started the war with a sneak attack on soft targets in Iran. This was originally a decapitation strike, intended to overthrow the Iranian government, but by the time those 12 days were over, the message was changed to a problem of nuclear weapons. This change in purpose of the war was so the western public would go along with American involvement.

Important to note, Israel's initial attack in Iran came a day after a no confidence vote in the Knesset against Netanyahu, little Pharaoh. Netanyahu survived by 2 votes. But he seemed to have wanted a new external war to take attention off of himself, maybe to earn some political points with the hard liners in Israel. Netanyahu has publicly called for the bombing of Iran since the early 1980s. Iran is the 7th and final country listed since the early 1990s that Israel has wanted to topple. Planning for this attack had been going on for many months.

Netanyahu seems to have underestimated the Iranian ability to retaliate. Across those 12 days Iran successfully damaged many military targets across Israel itself, especially targets in Tel Aviv and Haifa. The Iron Dome was not working very well. Iran could target their missiles anywhere in Israel at will. Israel was unable to put a stop to Iran using its own means and needed American help. This is where Trump stepped in.

Escalation Dominance

Professor John Mearsheimer has long explained that the strategy for small countries going to war is to try and drag a larger country into the fight. Escalation Dominance is the term. Israel put up a good fight, but was not able to take down Iran as they may have hoped.

Israel escalated up to the USA in order to get Israel out of the mess. They may have hoped the USA would join the war to topple Iran. That appears to be for a later time.

In any case, Trump stepped in and stopped the war, at least for now.

Iran, whom we've already identified as prophetic Barak, did not keep pressing the war. This is a mistake the Russian's have not made in Ukraine. This is probably why Iran does not eventually win this war outright, but gets help from the woman.

So, What Happened?

Alternative media has had a very difficult time determining exactly what happened. The problem is finding any external verification. The story goes that Trump bombed 3 nuclear sites in Iran so that Iran would not be able to build nuclear weapons. Never mind that those sites were regularly visited by international weapons inspectors who reported no such weapons grade material.

Also, never mind, that the type of materials was of the wrong sort for missile grade bombs. Also never mind those targets were empty. Also never mind that Israel wants a change in government in Iran. They want the Shah back as he is a Zionist puppet. Never mind Iran's central bank is not part of the normal network of Zionist controlled banks. Nuclear targets have little or nothing to do with the Zionist dream of ruling the world.

Then there was the Iranian bombing of an evacuated American base in Qatar. That bombing then became a cease fire. Each side had something they could use to declare victory to their domestic audiences so they could walk away.

Everything about the weekend seemed strangely staged. As alternative media started figuring this out, they generally went silent, as the only thing clear was that something fishy was going on. Trump did put an end to the shooting, but using some sort of staged political theater.

The American public loved it, and Trump's approval rating climbed once the public saw the shooting between Israel and Iran had basically stopped.

That late Saturday bombing by Trump was basically on the earliest possible prophetic date for the story from Judges 10:8, which calls out 18 years, so now days, of oppression. I had listed that Sunday as a watch date for the start of oppression in last week's blog. Israel's day break is at sunset, so it was already Sunday in Israel.

Trump's Big Beautiful Bombing was basically a direct timed match. Let me explore that story a little more closely because it includes interesting details. This bombing basically identifies Trump as a modern Jephthah.

Jephthah

The link here is to Judges 11 in the BRB. This is just beyond the 10:8 reference that gets us the date for Trump's Big Beautiful Bombing.

This chapter explains the biography of the ruler who was chosen to stop the war. This is essentially what Trump just did. Let me scan down through that biography and you can see some of the parallels to Trump.

Judges 11:3 is where we learn that Jephthah had to flee, and in that place gathered worthless men to himself. Trump, of course, famously fled the White House for Florida, and there gathered to himself a new administration and a new set of supporters. They are described in the text as worthless men.

Judges 11:6 explains he was brought back in order to fight. The Zionists appear to have selected Trump so that he could help with Israel's wars. They may have felt they needed his forceful style in order to handle the wars they expect in this term. We have probably only just begun.

Judges 11:13 sets out the dispute. The king of Ammon is fighting to capture all the land that was occupied when the heirs of Jacob came out of Egypt. This, of course, is today called Greater Israel. It is Netanyahu who is currently fighting to occupy that land, trying to increase beyond the internationally recognized 1967 borders.

So here we see a strange prophetic reversal. This is typical in prophetic stories like this. These reversals are what makes these prophetic stories so difficult to use in a predictive way. They are just descriptive for what is going on in the modern world. We've previously seen how Netanyahu is like a Canaanite king, and not an heir of Jacob. Here we see it again.

These reversals may actually exist because the modern nation of Israel is seen as Jebusite, and not under covenant. This is not perfectly true, but it is mostly true. Strange twists like this may continue as we move up the timeline.

The Judges 11 passage then continues and there is a written dispute about what actually happened in history. As a symbolic story on the problems of edited manuscripts it points at the problem that the Hebrew texts have been seriously edited. This, of course, by the same people trying to occupy the land.

Judges 11:33 is where we see there is a defeat against Ammon, who is attempting to take the land. 20 cities are taken. In some sense this may be describing the damage done across modern Israel. We have not seen such damage in Israel itself since perhaps the 1973 war. Iran had similar damage, but I am tending to focus on Israel. Hal Turner has a report up that estimates Israel's cost for this war against Iran as something around $18B. Even if the Iranian costs were similar, Israel must spread that cost over a much smaller population.

Mercy Delays

But these 20 cities are also a flag for a mercy delay. All counts in prophetic stories, no matter what else they may be are also references to time. So this suggests looking forward for future parts to this story. To start with, maybe 20 days. More on that below.

Iran is not particularly attempting to take back the land of modern Israel. Indeed, they were the ones Israel bombed 12 days earlier. That bombing was part of the general Zionist goal of conquering the world to setup a world capital at Jerusalem. So I am hesitant here to assign Ammon to Iran. The modern nation of Jordan, where Ammon is now the capital, also appears to be inactive in this set of headlines.

As we continue to scan down the story of Jephthah, we also find that he has made a stupid vow that will fulfill against Jephthah's daughter. In Judges 11:37, 11:38 and 11:39 we find 3 more mercy delay style time references that are each 2 months long.

So this entire story has a cumulative mercy delay of 20 + 60 + 60 + 60 = 200 days. This is nearly 7 months. It ends 13016-12-15 (2026-01-07). This is during the replay of the reign of David, about 10 days ahead of the simple replay of the start of the building of Solomon's temple.

Something that happened here, with Trump stepping in to help Israel with a fight it could not handle on its own, appears to matter again very early next year. Indeed, that future date may be more important than what we just witnessed.

Keeping Notes

When I first tracked this set of prophetic stories in 2001 I had no idea what I should be looking for. Like even knowing what sort of headlines might be interesting. Bombings and fires of various types were easy to spot. Political intrigue was not so easy. I did not know enough about the world to reason like I do now. I accepted the Bible as fully inspired. Oh, how things have changed.

I also had no idea of mercy delays. The idea of mercy delays as a concept were discovered as valid only after reviewing the events surrounding 911. We have not reached that replay yet this time around.

I have also never had a good software system for tracking these minor time offsets. They have always been just random notes. They do not draw very well on timelines as long parallel lines occupy page space without adding much value.

In an actual circular room dedicated to this problem, these delays could become lines, even strings, stretched across the ceiling, up out of the way. They would cross each other but no 2 such lines would be at the same angle, so they would not be hard to follow. Maybe arcs on a drawn timeline would be the graphical equivalent? Now there is an idea.

This problem of story delays is still an open question that applies to how the crown exhibit should be designed, even conceptually, to show this in an obvious way.

I have opened a tracking file for these various offsets that we are seeing as we are running through this set of stories again. I will use those notes to track the times when we are at the end of these various mercy delays. This will at least give a better sense of how important these are to understanding fulfillment headlines.

Trump On the Temple?

In this case of Jephthah, this particular delay, is landing just ahead of the replay for when Solomon started building his temple. So by identifying Jephthah as Trump, and by looking at the timing of this mercy delay, we can speculate a little here.

Trump, of course, was a property developer before becoming US President. So building stuff is up his alley. Perhaps Trump is going to help Israel set out to build a Big, Beautiful, Building, somewhere near Temple Mount in Jerusalem? I joked about this earlier. Now there is some timeline support.

What would be a better monument for Trump's legacy than a Jewish temple?

This Jephthah timeline pointing out into early next year also marks the end of Jephthah's daughter, whatever that may be in headline news. So this may not be that pretty. In any case, the notes are ready for when we reach those dates.

NATO Summit

The link here is to the Wikipedia article for the 2025 NATO summit. It was held at the Hague, itself in the Netherlands. This was the first time this country had hosted the summit. The Netherlands is the lost tribe of Dan.

This summit was held June 24 and 25, 2025. This was a match to the last year of Tola Judging, on 2025-06-24 and the first year of Jair judging, 2025-06-25. The second of these dates I called out in last week's blog.

There are no specific textually based prophetic details of interest with these kings. The focus simply appears to be on NATO itself. This is the western side of the military grouping which is out to satisfy their own national debts by conquering Russia.

Topics to note from this meeting was Ukraine's Zelensky was there, even though Ukraine is not a member of NATO. He was wearing a suit, which is very rare. He is now a defacto member of NATO, meaning NATO has no intention of reaching a peace agreement with Russia over Ukraine.

The summit was also working to get a commitment from NATO members that by 2035, they will each provide 5 percent of national GDP directed towards making war. This is a request by the USA, but the 10 year time frame is basically in the infinite future. Spain was the only country that seemed to object to this 5 percent number.

Of note, the passage on Jair references 30 sons on 30 colts with 30 cities. As a mercy delay this ends 13016-08-29 (2025-09-23) which is also marked on the calendar as Incarnation Day. I have made a note so we can return to it in late September.

Beware a Restart

Nobody aware of what happened in this 12 day war expects the cease fire to hold for long. Israel, especially, is not agreement capable. Think Gaza and Lebanon.

Martin Armstrong took to the podcast circuit on this point. His software suggests a resumption of this war in August of 2025. We will track watch dates across that time as usual to see how this may pick up.

Armstrong also said that his software also suggests a major war in 2026. He said his system has not predicted such a major war for 40 years. He is usually pretty good at spotting trouble, so I would not dismiss him.

If that war is in the middle east, involving Israel, then the timeline we are following might give the dates. The civil war and split kingdom stories hit late February, 2026. The Assyrian Deportation was more serious and it replays in November of 2026.

Either of these could be what Armstrong's system is picking up. Remember, his system uses financial market data to predict the future. The men who plan wars also move money around to both avoid loss from their wars and to profit from the wars they create. (This is the ultimate in insider trading.)

Shop Work

I have been thinking through the list of exhibits and planning out what is needed to get them designed and fabricated. My working goal is to get a 3d print for all parts of a first draft of all of the exhibits.

This goal will then let me do an exhibit wide iteration based on whatever I might learn across that first draft. If I iterate early, I use up 3d printer time and I risk never finishing, just spinning in iterations.

To get this done as soon as possible I need all the 3d printers running as much of the time as possible working on new stuff. So I spent this week mostly in the shop with the goal of getting all the new Voron's up and running.

The oldest of the Voron's, v7, had belt and racking issues corrected. It was calibrated from scratch for use with PLA plastics. It was finally moved off the bench back to its stand in the farm. It produced its first real exhibit part this week, an excellent achievement.

I looked at the software configuration for the Box Turtle filament feeder. I should have started there. It currently requires the use of a fork of the main software used for running the Vorons. This is like needing a fork of Linux in order to run MS Office. I am not going to do that, at least not now, so I set that filament feeder aside. Another year and maybe that software will be ready for prime time. I ordered that hardware on a lark, and should have been more cautious.

I started printing out a few minor mods for all 3 Vorons. The first is basically the same setup I'm using with the Prusa's to support several top mounted filament spool holders. Vorons normally have side mounted filament spools that do not fit well in the shop. Their standard setup also binds the filament. Most of the parts I am currently running need filament changes. I have been doing most of those changes by hand recently and need to do the same with parts 3d printed on the Vorons.

Another minor Voron mod allows routing more than 1 filament into the enclosure. Copies of that mod have been 3d printed this week. Why this is not the standard design, I do not know. In any case, the Vorons will be setup for manual filament changes.

Treasure Chest Status

The designs for the 4 Treasure Chests ultimately include 12 different panels. There are 4 tops, 4 fronts, and then 4 simple sides. I am out to 3d print 1 copy of each, and then assemble them into 2 actual chests. I will build out 4 full chests in a future iteration. This time around I am checking mechanical design and the story told by each panel.

The 6th of those 12 designs was 3d printed late this week. The first of the 2 chests was also fully assembled this week.

There have been numerous minor design changes during this process, including adding an indent to the back of the lids so they align when stacked. I also added a footer to the chests to make them easy to lift. The footer is also designed to stack together with the trims on the lids so all of these items can be easily stacked. This design also protects the various reliefs that are designed into each panel.

Watch for pics on Telegram.

Dye Lot Tricks

I found a way to fix dye lot issues with 3d filaments. This became evident as I started printing out the parts for the chests. It is possible to do a filament change a few layers ahead of the final top of most parts. This can be used for various reasons, but one use is to stretch out a single spool of plastic across the facing surface of a huge number of parts.

I am regularly using this trick to stretch the use of exotic colors. But it can also be used with common colors to make the top surface always come from a single spool.

So imagine 2 spools of white, but which are possibly from different dye lots. Use one spool for the hidden lower layers, and then deliberately switch to a reference spool for the top, final, public surface of the finished part.

Each spool can be the same color from the same manufacturer, say white. But they do not need to be the same dye lot, which cannot be determined by inspection of the spools in any case. Once 3d printed, only 1 spool created the top visible surface, so the dye lot is the same.

By doing this trick, the die lot problem goes away.

Robotaxi Launch

The link here is to a video on Joe Tegtmeyer's Youtube channel. He was there for the opening day of Tesla's taxi service in Austin. This was Sunday, June 22, 2025. Lost, perhaps, in the shadow of headlines out of Israel. But, it was an important day.

Tesla has been working for about 10 years to get a vision only, Ai driven, self driving software stack worked out. This was the day that software went public. This software is currently using stock Tesla cars. There will eventually be a car model without a steering wheel. That should come next year.

Watch the video to see cars driving around with nobody sitting in the driver's seat. There are still Tesla minders in the front passenger seat just to make sure everything is working as it should.

Congratulations to Elon Musk and the entire Tesla team for an amazing milestone.

Vera Rubin Telescope

The link here is to a Scott Manley video on Youtube dealing with the largest telescope in the world. It is located in Chile. I have previously mentioned it in the blog. It is on the planetary Qu map at the Oo, or eye, location.

That telescope is now starting to produce images, and Scott goes through some early samples. He is explaining how this machine works, which is very different than most telescopes in the world. Instead of looking out deep into space with a narrow field of vision, it looks broadly across the sky.

It will end up regularly passing across the whole sky, making it easy to find things that move. It has already found an astonishing number of new asteroids. Scott suggests it may ultimately find millions of new asteroids.

The data is being published openly, so anyone with the skill can write analysis software to see what they can find. The public no longer needs their own telescope in order to study the sky.

Of course, there are always issues with such a statement. Near the end of that video, Scott explains how the data stream is run through a government office who can then change it to hide anything they want.

Who might want to do that? Never mind. We live in an empire of lies.

More fun technology, in any case, coming from the prophetic map of the earth.

More Later,

Phil