400 App Changes
This blog goes over today's updates to the 400 app, dropping many tables in favor of a new one. Also, a more detailed look at the story of Deborah. Then watch dates for next week. Then finally shop notes.
400 App
2 weeks ago Ryan started a set of revisions to the 400 app. Today, those updates were put online. The link is above.
The main changes to the app include double lettering for the cells in the main table and dropping all of the secondary tables in that app in favor of a single secondary table. Let me explain the details.
2 Letter Address Codes
By using 2 paleo glyphs in each table cell, those letters become unique identifiers. They operate similar to the normal cell number. The first letter is the row. The second letter is the column. So the letter pairs give advanced users an immediate sense of where in the table the cell is located. Like coordinates on a map.
I would imagine that once this work finishes, that serious readers of the text will memorize stories by either their base 10 cell number, or else by their paleo letter pair. Many people, using regular bibles, memorize stories by address. So this is not an unknown technique. But by using these 2 letter codes there is meaning that becomes interesting.
Not only does the 2 letter code indicate the basic location on the overall table, it provides a way to learn the location of at least some of the matched stories.
New Chiasm Table
The 400 app now has a single secondary table. This table is designed to drill down on each individual square in the main table. This new table has 1 row for each individual square from the main table. For each such main square, the new chiasm table lists off all of the other paired stories that go with that square.
This means there are 625 rows in that new Chiasm Table. So it is quite long. There are secondary menu choices in the drop down menu to make moving around easier.
Just like the main table, clicking on any cell in the new Chiasm Table will pop up the scripture passage behind that square.
This is a powerful and simplifying change to the 400 app itself.
Chiastic Folding
Long time readers here know that stories fold against each other following a chiastic structure. Studying the text using chiasm has long been known to Bible scholars, Ryan learned about it in Bible College. We found that this pattern also exists across long runs of inspired stories.
The folding pattern for inspired stories is following the same way the Paleo alphabet folds against itself. This pairing often shows itself in the text where content in the folded stories both reflects the meaning of the letters at the address and by matched content in the story pairs.
This is easiest to see in the finished rows in the main table, say the Gospel of Mark. I assume most readers here already understand this pattern.
The alphabet has an odd number of glyphs so in any given set of 25 stories, the first 24 of those stories fold together forming 12 pairs. The final story floats alone.
This pattern is very helpful for finding inspired stories because when this folding pattern is not seen, there is usually an edit somewhere that is messing up the fold. For the New Testament this has usually meant there is an out of place copy of a story that belongs somewhere else. In the Old Testament there are many more whole cloth additions, making the riddle harder to solve.
Defeating Study Bibles
This folding is not only useful to us, but these folding patterns are the inspired system which abrogates the need for works like Study Bibles. The text itself is written so anyone who knows the folds can find the interpretive parallel passages that exist for any given inspired passage.
For our current recovery work, finding these folded pairs helps considerably with identifying which stories are likely to be inspired. The folding pattern makes this level of the problem into something like an advanced biblical jigsaw puzzle.
Diagonal Chiasm
For many months the cells along the negative diagonal have been highlighted with a slight gray shading. Those cells are conceptually interesting because only in those cells does the Paleo letter for the column also match the Paleo letter for the row. With double letter addressing it becomes much more obvious this is a special feature of that negative diagonal.
These cells should be special in some way because of this quality. So this highlight allowed study of the question. Of course, out in the middle, the correct stories are very uncertain. So learning the secrets of the diagonal has been hard to do.
Of course that diagonal is a run of the alphabet. So the obvious question, Does that diagonal fold on itself?
Said differently, Is there some sort of diagonal chiasm?
The simple answer is that there must be such folding as all runs of the alphabet similarly fold.
With as the early stories and as the late stories came together, checks against the diagonal stories seemed to support the idea of diagonal chiasm along that central negative diagonal.
But is that diagonal line of stories hinting at chiasm along other diagonal runs of stories?
This is not an easy question to answer because off from the center negative diagonal the alphabet letters do not assign cleanly, orderly, to the cells. Even inspecting the diagonals was not easy to do accurately.
The release of the 400 app 2 weeks ago had a change where instead of just highlighting the negative diagonal, that highlighting was now a complete checkerboard pattern. So any diagonal could be tracked by eye across the table. Both along the negative diagonals, but also along the positive diagonals.
Ryan used that checkerboard pattern to spot check other diagonal lines to see if stories were still doing any alphabet related chiastic folding. There were enough examples to think this might be going on. So he set out to make more changes, those released today, to make this easier to study in the future.
Diagonal Chiasm Promises
Let me stop here and discuss the power of this change. Assuming the text actually works this way in the end, and no mistakes are being made with the math, and we're not looking at shadows, then something interesting may be found in these diagonals.
The Quad Column and Quad Row on the main table are not part of most of the Chiastic folds. Save those as special.
For all the other stories off of the main negative diagonal, for any given story, there were 2 different stories that matched by chiastic folding. The first was somewhere along the row. The second somewhere along the column.
With diagonal chiasm, for most stories, now there are potentially other stories that match along the diagonals as well. More witnesses mean easier recovery and more witnesses mean more places where future readers can go to interpret passages.
But Tricks
Outside of the center negative diagonal, the other diagonals have a more irregular structure. Just conceptually, there is some sort of wrapping needed for the other diagonals in order to get them to complete.
Ryan has worked out that wrapping so each diagonal has a complete set.
In the normal horizontal chiasm, the reading order is following the alphabetic order of the folded stories. For vertical chiasm this is also true, but skipping many stories in order to be complete.
For diagonal chiasm the reading order still wants to start at the top of the table, this so the stories are in chronological order. But the letters those chronological stories touch are not in strict alphabetic order. So the folding pattern is not as obvious either.
The Chiasm Table
The design goal for that new table is to list the 625 stories from the main 25x25 table on the front page of the app. They are listed by number. They are listed in chronological order as found in the main table.
For each story, that table lists off the other stories where there is some expected match by chiastic story folding.
In that table you will see the normal row and column folding. You will also see folding by both row and column. This is a diagonal move that forms the far point of a square formed by the row and column folds. It is reflexive through the very center of the table, but not normally on an actual diagonal.
You will also see river pairing. The normal pairing we've been using is based on the Vine exhibit. But the River exhibit also pairs letters. So there is now a way to study that pairing too, both for rows and columns.
Sometimes the river pairs are the same as the vine pairs. In that case, the river pair cells are darkened to warn that the cell exists by the river pairing rules but that the river pair does not add anything new to the system.
Finally, there are also 2 diagonal pairings that are formed along the diagonals of the table itself. These diagonal pairs are given both along the negative and positive diagonals spreading out from each cell.
The math behind those diagonal folds makes some assumptions about how those diagonals wrap around the edges of the table. So that data is less obviously correct from first principles. But, if it works out, then this provides yet another way to check stories.
Ryan and I spent quite a bit of time discussing the theoretically possible ways the main table might fold against itself. This new table is near the limit of what is possible. Going forward, all possibilities can be tested across the weeks to come. We may or may not trim it back in the future.
Cipher Keys?
The cipher disk prototypes that I worked out a couple years ago are keyed by 2 letter codes. Basically, those codes mark how to setup each possible cipher. Worst case, there are 625 possible different ciphers in the system. 25 possible settings up 1 side of the fig tree. Then another 25 settings up the other side of the fig tree.
Until this past week we've never had any idea about how to select the correct ciphers for use in any given story in the text. Now we at least have a hint as to where to look.
So, the 2 letter codes spread across each row in the new Chiasm Table may also be the legal cipher settings for individual stories.
Deborah
Last week I mentioned that when Trump told us he gave Iran 60 days to surrender he was also giving us the original prophetic story for events still underway in Israel and Iran. Trump was pointing us to the start of Judges 4, linked above in the BRB.
Let me paraphrase the story here. There was an evil king living in Canaan, Sisera by name. He had 900 chariots of iron. The people of the land had been sold to this evil king. The people cried out in prayer to end this oppression.
Deborah the prophetess judged at that time. She sent for Barak, from Naphtali, and basically told him to take an army of men from Naphtali and Zebulun and to deliver the other tribes from this evil king.
Barak was reluctant, and wanted Deborah to go with him. Because of this lack of faith, she agrees, but warns that victory will eventually go to a woman. There is a long song about that deliverance at the end of the passage. That song is currently filtered in the BRB, so marked as having disputable inspiration.
A 900 Chariot Mercy Delay
But, the actual 60 day offset that Trump himself used to time this attack on Iran is not expressly given in that prophetic story. What we are usually looking for in the text is a "mercy delay" usually timed by the use of a count of something. Those detailed counts tell readers like us when this prophetic story eventually fulfills or finishes up in some way.
Mercy delays are what we call time references that shift prophetic stories from their location in the base historical timeline to future dates when they complete but not with the same historical pacing.
The actual mercy delay within the general story of Deborah is the count of
the iron chariots, which is 900. So 900 days. So 30 months of 30 days. So
2.5 Paleo calendar years. So Trump's 60 days to the start of his attack on
Iran is just the first 2 of 30 such months.
Remember, we are running a day-for-a-year replay of the Old Testament
chronology because it informs the 2000th anniversary of the life of Joshua.
We are actually running the New Testament chronology with a 2000 year offset.
So the trick is to see if those 900 days hits anything interesting in the
New Testament, in the life of Joshua himself.
It comes very close, within the time of the watch date window itself.
The easiest way to see this is by looking at the main dates of Joshua's
public ministry. There is a page on Bible Time which does this. Here is the
link.
That article goes through the basic math and then gives date reports for
his baptism, public reading of the Isaiah scroll, crucifixion, and then
Resurrection Sunday.
These, of course, are 2000 years ago. To find the modern anniversaries,
just add 2000 to the year number given in the left column of the various
date reports. Then those modern paleo dates need to be converted using the
calendar app to a modern Gregorian date.
Of that set of dates, Joshua reading the Isaiah scroll turns out to be
the best match. The modern anniversary is 13018-09-08 (2027-09-02) a Wednesday.
That date starts a 390 day Jubilee year which itself leads up to the anniversaries
of Passion Week late in 2028.
If we back up 900 days from there, we get 13016-08-08 (2025-04-05) a
Saturday. This was 1 week ahead of Trump's 60 day warning. This is sitting
within the watch date for Deborah just fine.
Remember that when Joshua read the Isaiah scroll he ended his quote
mid sentence. The year of favor is all he quoted. But the cite continues and
mentions the day of vengeance. That idea would generally match the end of
the story of Deborah, so that visit to Nazareth is a potential match to the
first set of 900 days.
But, we don't get the end of Deborah's story until we have gone out past
another set of 900 days. If we are to be very precise about this, we need to
use both references to 900 chariots within that story of Deborah.
So the first 900 days run out to the Isaiah Scroll date, and then another 900
days to some other event.
Generally speaking those additional 900 days, against the historical timeline,
lands near the prophetic replay of the breakup of Rome into East and West.
That would be just about 5 years from now in the middle of 2030. This is over
a year after expected nuclear war dates in early 2029. To those who survive
it, nuclear war is not the end of the world. But, it may be the end of NATO
and the EU.
Let me deal with more of the prophetic parts of this story, and answer
some questions that were raised by last week's blog.
As the headlines were unfolding as I wrote up last week's blog, I did not
want to be very precise about who, on the ground, matches who in the text.
The first issue is who is the evil king in Canaan who is oppressing all
of the tribes? Why are they said to be sold into the hand of that king?
The obvious answer is that the Canaanite king will turn out to be Netanyahu.
He obviously forced Trump to heel, like a lap dog. The USA will do Netanyahu's
bidding. Even if Trump looses all political credibility. This is what
AIPAC is for, it give Israel power over most politicians. By watching silliness
in European politicians, I would strongly suspect Europe has something similar.
Israel's main, historical, industry was international banking, similar
to central banking. Everyone who is a borrower in the western world is in debt
to his various agents. So being sold to this king means being sold into debt
slavery, probably fractional as we see with modern debt. So we are matching
up the prophetic story to events on the ground. But it is 5 years before this
is over.
The reluctant warrior who is called by Deborah to defeat that Canaanite king
would thus be Iran. More precisely this may be the supreme leader of Iran who
is very reluctant to take on Israel directly.
Barak wants Deborah to go with him, and so we are also looking for a prophetic
Deborah.
The tribal maps of the earth break Joseph into the west, precisely Manasseh
in the USA, and to the east, Judah, into Russia.
Overlaid on this planetary view of the tribes is the Garden of Eden
story and the creation of Adam and Eve. Adam will become symbolic of the
USA and Eve will become symbolic of Russia.
The motherland references used by the Russians themselves point at their
own country as feminine. The USA using "Uncle Sam" to refer to the USA is
another such reference, but the masculine.
Deborah, as the female heroine who eventually goes along with Barak will
thus turn out to be Russia. A parallel lesson for this story is how Judah
could defeat Benjamin in the last 3 chapters of Judges, while no other tribe
could do this. But also note that Putin recently said that Iran currently
wants to deal with Israel on its own. So the woman has not yet entered the
active side of this story.
Deborah's story also references Naphtali and Zebulun. In last week's
blog I cited the name Iran, as being a match to Aryan, so Germany in 1935.
I also cited Tobit, who was from Naphtali and hauled away towards Iran early
in the Book of Tobit.
There are at least 2 more important details for assigning Iran as part
of Naphtali. Let me add those here for the record.
In answer to a question on the Duran, Alexander Mercourisreal corrected
a question from a live stream chat. The American public often thinks of
Iranians as being a branch of the Arabs.
To concretely dispel that idea, he said that the Farsi language is closer
to English than it is to Arabic. So Iranians have a language history closer
to Europe than they do to the Arabian Peninsula.
Why would that be?
Because Farsi must come from the same language root as English. Ultimately,
that language root will be what we call Paleo. Both the English and Persians
once spoke the same language when they were once both living in Canaan.
There are also other important references in Tobit that link back to Naphtali.
With Tobit being added back to our canon only recently, I don't have the Tobit
story generally memorized. But, regularly doing lots is a good thing. This
week, Joshua took me to the passages that matter.
In Tobit 14:4 and later in Tobit 14:14 we learn that Tobit's family moves all
the way into Media. This in part because it would be safer there. They expected
Jonah's prophetic words over Nineveh's destruction to yet come true. They also
expected Jerusalem to be destroyed.
In any case, the text of Tobit is giving a complete vector from Naphtali into
modern Iran that is supported by the same modern details that link Iran to
Europeans and especially to the Germans.
So when Deborah is calling Naphtali to defeat the evil king in Canaan, we
can expect that Iran is in the center of that when it replays in our day.
Germany could also step up to help, though at this point they appear hopelessly
lost to the Zionists. Of course saying westerners are controlled by Zionists
is just a modern way of saying they are being oppressed by the king in Canaan.
If you have not seen it, search for Tucker's interview of Ted Cruz for
a fine example of a US Senator oppressed (more like deluded) by the king of
Canaan.
Judges 4:6 gives us the precise instructions to Barak. He was to take
10,000 men from Naphtali and from Zebulun, in order to defeat the evil king
in Canaan. So this isn't going to be from Iran alone. There is some other
party that will also be involved.
We normally identify modern Greece as Zebulun. We do this by seal date
math as given on BibleTribes.org. Greece is not a country with a modern
set of colonies. But, the Greek language and culture once stretched across
most of the middle east in the more distant past because of Alexander the Great.
So in some sense we could be seeing a general reference to the Greek heritage
across much of that part of the world.
We have 900, or 1800, days to figure this out for sure. So we are
not in any rush. But there are other possibilities.
The first possibility is how Zebulun is called out as a haven for ships in
Genesis 49:13. So outside of Greece, is there another Zebulun hiding near Iran?
Qatar and Bahrain are basically islands, and may yet end up supporting Iran in
some way we cannot yet see. Both of those countries are proxies of the Zionists,
but perhaps they come around and become prophetic Zebulun.
A similar possibility is that Iran, alone, also has the ability to control
tanker ship traffic through the strait of Hormuz. Closing that route for oil
may be able to wreck the western banking cartel by messing up the western
economy. The war against Russia is in part to recapitalize western banks using
$75T in natural resources in Russia. So the reverse of that, pulling natural
resources out of the west, would presumably also work in reverse.
Loss of the use of the oil wealth around the Persian Gulf would work to
de-capitalize western banks. So dislodge the US Dollar and defeat
the king from Canaan.
Yet another possibility is that there may be another nation lurking as part
of Zebulun that we've not yet identified. That nation might be Turkey. In
reading the language history of Greece it became obvious that at least part
of the peoples that make up modern Greece migrated there through Turkey. Turkey
still remains strong enough to participate in a war against modern Israel.
So whatever just started when Israel attacked Iran is not going to end any
time soon. It now becomes a background set of battles that may or may not
pop on the prophetic schedule that would be active 2.5 years from now or 5
years from now.
It is highly unlikely to remain a shooting war for all of this time. Israel
still passes across temple building dates in early 2026. We will also pass
the 2nd temple building dates further up the timeline. In the case of
the replay of the 2nd temple dates, we need to remember that a Persian king
authorizes the 2nd temple construction.
All of this is interesting to speculate about. But we just need to stay
focused week by week. Real history is usually hard to accurately predict
given just the prophetic stories. All of this will make more sense as we get
closer.
For readers who may be new here, we are currently tracking a replay of
the trunk timeline of the Bible. This replay is running 1 modern day to the
ancient year. It is offset by 2000 years from the life of Joshua, which itself
was a rerun of the Bible's trunk timeline.
2025-06-24, Wednesday, is the replay of the last day of the time when Tola
Judges. There is no story to this time and the Israeli attack on Iran is the
likely event within Tola's time which started June 2, 2025.
2025-06-25, so the Wednesday after this blog goes out, is the replay of
the first year when Jair judges. His total time judging, 22 years, is given in
Judges 10:3. The last day of this 22 day interval is 2025-07-16.
We know almost nothing about this judge. He had 30 sons riding on 30 colts.
They had 30 cities. Presumably he ran a freight service, package delivery
service, or postal service of some sort. This would normally trigger a 90 day
mercy delay. But, since there is no other details, it is unclear what the
fulfillment might be.
Within this prophetic interval is the start of oppression as mentioned in
Judges 10:8. This was 18 years of oppression from the Philistines and Ammon.
It begins on 2025-06-29, Sunday. This interval floats loose and could start
as much as 7 days earlier, so it could start as early as Sunday, 2025-06-22.
Trump's itchy trigger finger could slip as early as the Sunday after this
blog goes out and then reach that story.
This was a busy week in the shop. The 2nd batch of filament samples were
printed out as sample chips. This included a few that are variations in
material, there are now 79 chips in the set. Of particular interest was
better coverage in greens suitable for leaves on the various trees. One
particular olive green is obvious for the olive tree.
In this set of colors were found terracotta and brick. When we need clay
pots we have the HTPLA color for that.
There were also a couple of gray carbon fiber infused filaments that might
be interesting for strength. A ceiling version of the star field comes to mind
for that filament.
This sample building work makes selecting colors much more precise than ever
before. The areas that use the rainbow colors will all be very much better
than ever before.
I am still using regular PLA for first prints, this to force an iterative
design process. But as the work progresses, those designs will go through
a final fabrication with precise colors and heat resistance.
The treasure chests include a liner design and then decorative surfaces
with art. The first full liner finished 3d printing this week, in particular
the parts needed for the 4 high sides.
The first of what will be 4 treasure chest lids was also printed and assembled.
The original design for this lid had been faithful to floor geometry from the
mosaic itself. But once I saw it on the bench I needed to adjust it to precisely
match the other exhibits in the set. The original mosaic builder does not
seem to have been real precise, having scaled his art slightly. Lack of
precision generally bugs me, and once it was in hand it needed to be brought
into agreement with the other exhibits.
So the second copy of that first lid came off the 3d printers and it now
looks really good. It is a head turner it is so beautiful.
I used matte black for the background on that lid, which is an interesting
experiment. The mechanical assembly went together well.
But, the current design still uses some superglue for the inlays.
In doing the assembly, I saw how this could be made a fully bolt-together
item, so it will eventually get revised. I want to leave this first copy
alone for awhile in case there are other issues I don't yet see.
The first of what will be 4 different chest fronts also came off the 3d
printers this week. That front is also using matte black, but without the
need for glue. Watch for photos on Telegram.
The wiring needed to support the new filament feeder was added to the
Voron where the feeder will be attached. The feeder had an idler problem,
which was also fixed. The firmware for the filament feeder was flashed. Next
up is belt tensioning and then software calibration. This printer is being
setup for printing multi-color tree limbs.
The link here is to Scott Manley explaining a recent explosion during
static firing of Starship 36 in Texas.
Musk would later post on X that the first failure was of a COPV containing
nitrogen that failed below its design pressure. The PV in that acronym means
Pressure Vessel. Think a high tech, plastic, version of your hot water tank.
Musk did not say if this was a commercial off the shelf part, or a custom
SpaceX part. That detail really matters.
SpaceX is on a tight schedule to meet the next Mars transfer window and
setbacks like this do not help them to meet this schedule. Mars may end up
waiting until after a world war.
I was watching the live stream and noticed many comments in the chat that
asked if this failure was caused by a sniper. The ship broke apart up near
the top, and not down near the engines where this would be expected. So the
real question is did Musk attract unwanted attention from the Deep State who
are now stopping SpaceX? A sniper's bullet into that COPV would easily explain
this failure. Especially if it was a tested commercial part from some outside
supplier who makes many of these things and certifies them.
We have a watch date coming up near the end of July dealing with Elon
the judge. I wonder if our modern Elon may be part of that modern replay.
We'll see.
Larry just released a 59 minute Youtube video of a conversation he had with
Alastair Crooke on the situation between Israel and Iran. Alastair is perhaps
the best man in the world for reading the geopolitical landscape of the world.
Larry is in the same league. Israel, and especially the Trump administration,
is in a world of trouble, as they explain.
More Later,
Phil
Simple Checks
Jesus' Ministry Dates
The Evil King of Canaan
The Reluctant Barak
Naphtali Links
Zebulun Links
Watch Dates
Shop Work
Treasure Chest Prints
Printer Upgrades
Star Ship Explosion
Larry Johnson and Alastair Crooke