Book of Job

This blog looks again at the Book of Job. Before that, more updates to the 400. Then some watch dates, importantly, we are approaching Samson. Also, match dates, shop work and a headline review.

400 App

This week saw several updates to the 400 app that I need to note here in the blog. The most obvious is resetting the rows in the middle of the table. Previously these had mostly been dropped in. This week, the order of those rows is changed based on at least some evidence. Let me step you through the bottom half of the Old Testament material, those central rows, so you can understand our current thinking for this material.

Jo Row, From Story 175

This row has not changed location. For reference, it is the last row in the historical chronology of the Old Testament material. It covers the Assyrian Deportation and the Babylonian Deportation.

Ha Row, From Story 200

This row now contains Isaiah and Jeremiah. These are major prophets. They lived through and write about both of the deportations in the previous row. So this is basically providing commentary for why the heirs of Jacob were removed from the land.

The Row, From Story 225

The The letter is a wheel. Time and Travel are 2 main concepts from this letter. This row's books have not changed this week. But the row does carry Esther, Ezra, Nehemiah and Tobit.

Tobit still seems out of place in that it references the Assyrian deportation, but the Book of Tobit still seems to fall later in time. This time shift may be explained by the references at the end that go forward from Tobit's and Tobias' stories. So the book itself may be considered canonized later in time.

Yo Row, From Story 250

This is also still the book of Job. This has not moved from last week. The first letter of Job is the Yo, mispronounced in English with a J sound. The letter itself deals with all work of the hands, but most importantly the work of writing. This is important to Job. More on Job below.

Ku Row, From Story 275

As of this week Proverbs is now placed on this row. The Ku letter is a sprout. Like a sprout of wheat in a field. Key ideas are young and growing. Also, young enough to mostly be all alike. The introduction to Proverbs discusses how this material is for children and boys. The material of the center of Proverbs itself does not have much distinction, also similar to Ku. This material may have been compiled by Job as part of his work, which is in part why it is located here. Again, more on Job below.

Lu Row, From Story 300

The 12 minor prophets are now placed on this row. The Lu is the 12th letter and is likely calling out the count of the 12 minor prophets. The Lu is a shepherd's staff. Amos, the earliest, was of the herdsman of the children of Tekoa, a match to the Lu.

Previously, we have considered these writers to be coincident to each other, likely members of the place at the Jordan built in Elisha's day. We are now at least debating if these might be a family lineage of some sort. This would imply there is a prophetic family line from Samuel perhaps all the way to Joshua.

Mo Row, From Story 325

Psalms is now placed on this Mo row. Mo is water. The ink that folds back to the Yo, the hand, in writing. Psalms 1 provides an introduction to this row and discusses being planted by a stream of water. We take this to be identifying why the Psalms belong on this row.

Ne Row, From Story 350

The prophets Ezekiel and Daniel are on this Ne row. This is the last of row of Old Testament material. These prophets have not changed rows this week. Ezekiel is providing many visions of the exhibits which Joshua himself will rebuild in order to provide the basis for the New Testament era ministries, both Joshua's own, and the later generations up through Paul.

Daniel is providing the timing for the events in the New Testament which begin on the following row. Daniel is also providing general stories dealing with the flow of history going forward, down even to our day.

Both of these prophets are located in history soon after the fall of Jerusalem to Babylon. So these prophets are resetting to the place of Jerusalem and the timeline that stretches out from Jerusalem, the ultimate stage for history to continue.

The remaining rows in the Table of 400 have not changed this week. The New Testament material is starting to feel more stable.

The other major change to the 400 app this week was the inclusion of diagonal matches in the individual story reports. Let me review that change here.

Diagonal Reports

Each story in the 400 app has a report page that shows where that story has matched pairs. To find the report, click on a square to pull up the story text itself. Then in the header of that popup is a link to the report. Click that to go to the report page for the story.

Each report shows all of the story folding that comes from the Vine and River exhibits. That folding shows which stories match along the row, and match along column, and also match along an opposite square. This is driven by the pairing naturally found in the 3d systems of the Vine and River.

This week we have added underlying code and display for folding along the positive and negative diagonals out from any given square. This has been hunched for several weeks, but there were various possible formulas for determining the matching diagonal stories. Fundamentally, should the column identifier or row identifier be used for calculating the fold?

After getting Genesis figured out it was possible to see some actual working examples of folding along these diagonals. It turns out to be using the column letter of each square for calculating the diagonal folds.

The column is folded through either the Vine or River as usual. The resulting column from that fold is then used to find a square where that new column intersects the diagonal out from the original square. This is done for both positive and negative diagonals.

This causes various weaving patterns that spread out across the table in various ways. It makes the resulting set of stories more tightly connected. Most rows have at least 1 cell that folds this way to at least 1 cell in most of the other rows.

Rethinking Job

Anyone else reading through the Sabbath Reads app this past weekend will have noticed a substantial section from the Book of Job. When Ryan and I read through that material it caused a long discussion about the Book of Job and its purpose.

As part of that discussion, we decided first that Job's friends must be real friends. Any sort of attack on Job from any of his 4 visitors is likely an attack at the hands of an editor. The editor of Job did not like the original story line, and attacked him by adding verbal attacks from his friends.

Ultimately, those 4 friends were likely originally Job's students, who had returned to understand what had happened. Joshua God had surely been protecting those exhibits, but for some reason did not do so. As those exhibits are the heart of faith, this was a serious problem. As this happens at various times in history, it is important to explain what is going on when this happens.

Answering their concern is ultimately the purpose of the book. It ultimately explains why the exhibits and additional volumes are lost at various times to history.

I will explain more below, but as a part of this past weekend's discussions, we had to rethink and expand our understanding of additional volumes.

Additional Volumes

In previous blogs I have interpreted the Feeding of the 5000 and the Feeding of the 4000 as parables about how the base text can be ciphered into addition families of documents. The base, inspired, stories multiply and provide food for many. It does so using ciphers, themselves discovered using the Fig Tree. This is an exhibit still to be fabricated in the shop.

The 625 cells in the base manuscript, multiplied by 8, yields the 5000. So 8 different ciphers against the base text gets us 5000 total stories.

But then there is another parable of feeding 4000. We originally thought this was an editor's botched copy of the feeding of the 5000. This because it is not exactly an even number up from 625. But we later decided we needed to include that feeding of the 4000. It implies yet another cipher round. Producing 4000 more stories. This is not an even number, but we will figure out why later. Left over counts may have something to do with this.

So far we have a base text, then 2 sets of ciphered stories. A set of 3 as I have explained in previous blogs. But, are there more? Is this an under count of additional volumes?

We stopped to review the New Testament material to see if there are still more cipher rounds. Joshua himself fed the 5000 and then the 4000. So he ciphered 2 times.

But then Joshua chides his disciples about feeding others in the same way as Joshua did with the 5000 and with the 4000. See Mark 8:20-21. What is it that the disciples still do not understand? They must finish the cipher work and feed thousands themselves.

Joshua is indicating that there are still other cipher rounds like when he fed the 5000 and when he fed the 4000. The references to left overs in those earlier stories may be the actual hints to this. Joshua did it 2 times, maybe his disciples should do the same 2 more times using left overs? So maybe 4 cipher rounds? So a base text and 4 more? Job and 4 visitors?

Job As Allegory

We have previously understood that the events at the front of the book caused the destruction of a set of Tent of Time exhibits that Job was responsible for keeping. His task after that point was to start from scratch and rebuild everything, including ciphering of additional volumes from a base text. The English word "job" may come from Job because Job had quite a job to do.

As we looked again at the Book of Job we started to see that entire book as an allegory of the text itself. Job, the man, is the base inspired text. From that insight we can learn a bunch more about the text itself.

Job's Doubled Substance

Notice that once Job is restored, his substance will be doubled. If Job, the man, wrote Job and Proverbs, he wrote and finished off through the middle of the entire ultimate set of inspired core documents.

By this logic, after Job's writing, then the inspired text is doubled.

The Lu row down through the Colon row in the table is that doubled text. The Quad row, at the bottom, is simply an extra portion which is typical. So, doubling is evident in the text and still stands even with the Quad at the last row.

So by Job's placement in the canon, he marks half of the work. So we are not far off in thinking he is matching the text. Job is currently on the Yo row, and we are giving him credit for Ku. A variant that would still keep with Job at half way would be to move him down by 1 row.

But now, think about his friends. 3 friends and a young man, so 4 come to visit. Who or what are they? They each look to represent a set of ciphered documents. Let me explain.

Job's Cipher Counts

At the start of Job, a count is given for his substance. Job 1:3 "His substance was 7,000 sheep and 3,000 camels and 500 yoke of oxen and 500 she-donkeys and a very great house, so that this man was the greatest of all the men of the east."

Job himself is the base text. Job's great house is going to be his copy of Moses's tent of time, so all of the exhibits. Job's other substance is presumably the additional documents indicated by cipher counts through what would be Job's work. So half way through the text.

7,000 + 3,000 + (2 * 500) + 500 = 11,500 is the counts at the front of the book of Job, so down through his books in the canon.

Job 42:12 may then be giving the total count. "The Master blessed the end of Job more than his beginning, for he had 14,000 sheep and 6,000 camels and 1,000 yoke of oxen and 1,000 she-donkeys."

14,000 + 6,000 + (2 * 1,000) + 1,000 = 23,000, the total count of ciphered stories.

Note how there are 4 parts to this equation. The 4 who came to visit him. Those 4 are symbolic of ciphered document sets. Each set has a different personality, and a different count.

So the 5,000 + 4,000 = 9,000 from Joshua's multiplication stories are the same as a part of Job's story. 6,000 + 2 * 1000 + 1000 = 9,000 as per Job.

The difference, so 14,000, may be what the disciples actually had to cipher on their own. This was why they may not have wanted to wait tables. This may be the young man, the 4th, in Job.

I am showing the general math here, but there is added complexity. The New Testament writers would finish the base text and then it would be run through the ciphers. So how all this works out is still to be determined when we get to this work later. (3d modeling and Ryan's Table of 400/625 must be mostly finished first.)

Job's Boils

Backing up to the front of Job. There is a long setup about how the decision for the disaster that befalls Job was made in heaven.

Job 1:6-12 discusses Job's first test. Everything is to be taken away from him, but nothing is to happen to his body. As an allegory for the text, this means it was reduced to only the original inspired public manuscript. Everything else was removed. His family and house, so the exhibits, were removed. All additional volumes were removed.

Job 2:1-10 discusses Job's second test. Here the accuser is allowed to touch his body. The only limit in this test is that Job's life may not be taken. Job ends up covered in boils, including in his brain.

As an allegory, this is the editing process that the base text also went through. The editors were allowed to touch the inspired document. The limit which prevented the death of Job is indicating that the text must always remain recoverable. It must always remain alive. That limit cannot be crossed. But additions, so boils, were allowed.

The manuscript lives in this state now. This is what we are faced with fixing in our day. The manuscript is not dead, but it is seriously sick.

Job's Restoration

Job 42:10-11 deals with the restoration of Job. My paraphrase... "The Master restored to Job all that he had lost... The Master also gave Job twice as much as he had before. All his brothers and all his sisters and all those who had been of his acquaintance before came to him and ate bread with him in his house, for they had been in distress over him and they comforted him for all the hardships that the Master had brought on him."

This, of course, is the end of the allegory. The manuscript and the additional volumes are restored at the end. So is Job's house, which means all of the exhibits that are normally part of the entire bundle that proves inspiration.

We seem to be in a time in history when that restoration process is going to happen again. But, oh, such a strange task.

Watch Dates

We are continuing to roll through the time of the Judges. This next week we have yet another transition between minor judges. The last year of Ibzan replays on 2025-07-29, which is the Tuesday after this blog goes out. Ibzan had 30 sons and 30 daughters and sent out his 30 daughters and brought in 30 wives for his sons. This is a typical mercy delay so we would not expect anything in this reign. In this case 4 months of 30 days each, so 120 days, as a mercy delay.

The first year of Elon replays on 2025-07-30, so the Wednesday after this blog goes out. Elon judged 10 years, so the last day of the replay is 2025-08-08. All we know of this Biblical Elon is that he was from Zebulun.

The strange problem with this Biblical Elon is that we also have a modern famous Elon, who runs SpaceX, Tesla and several other companies. Our modern Elon has been in a feud with Trump, but for the last few weeks, modern Elon has been back to normal work and otherwise behaving himself. Perhaps he will do something curious during these 10 days?

Looking Ahead To Samson

Finally, there is another interesting date to note. This is a loose date, so hard to definitively chart. But there is a 40 year time of oppression given in Judges 13:1. This story also includes the story of the birth of Samson, which itself includes a fiery offering on a rock.

When I charted this 25+ years ago I set those 40 years of oppression to end at the death of Samson. So basically I used that as 40 years of Samson's age when he died pushing over 2 columns in temple Dagon. These days I see this timing as having been graphed more strictly than perhaps it should have been. In this case, though, it is hard to wiggle.

In any case, for reference, those 40 years of a possible life span of Samson would begin on 2025-07-28, so the Monday after this blog goes out. Though it was originally a personal story between Manoah and his wife, this would be the offering on the rock date from that story.

But Samson's story is very interesting for a bunch of reasons. Let me scan down the narrative for him and explain why we may see serious headlines start around Monday, 2025-07-28, but stretching out for many months.

Judges 14 tells the story of Samson's wife. There are a bunch of numbers within that story that would naturally trigger a long mercy delay. So we would not expect those stories to happen within this charted time interval.

Judges 15 tells the story of Samson's vengeance on the Philistines. Again, all of this is likely future headline stories, but offset by the numbers within the story. But, curiously, the 20 years of his judging is given at the end of this chapter, not at the strict end of his life. This locks in with the list of Judges and sets the hard date needed to even graph his first year.

Judges 16 tells the story of Samson's death when he pushed over 2 columns and killed the 3000 Philistines on the roof. In 2001, this story would replay as 911, but it would align exactly with the replay of the high place sacrifice when the heirs of Jacob asked for a king. See 1 Samuel 8:6, 9:12 and Acts 13:21.

So the story around the death of Samson actually replayed aligned with another serious historical story, ultimately, the establishment of the Jebusites as rulers in Jerusalem. We still suffer that historical event even today. It is why Netanyahu can come to visit Trump and dictate orders to Trump.

That high place sacrifice story replays on 2025-11-05, and is exactly 100 days from 2025-07-28, so the start of 40 years of oppression the Monday after this blog goes out, is the start of a 100 day count. So consider the offering on the rock at Samson's birth to be symbolic of the high place sacrifice of 911. All the other stories in Samson's life get offset in various ways.

911 was most certainly a false flag designed by forces sympathetic to Israel in order to draw the American public into war in the Middle East. This would naturally replay again if modern Israel started having trouble with its current wars in the Middle East. So the 100 days that start Monday, 2025-07-28 may show why we would see another false flag in the USA out in November.

At this point, presumably, Israel starts to loose, say against Iran, and wants US ground troops deployed to the Middle East. It will take a false flag against the USA to generate public sympathy for that sort of troop deployment. How, exactly, this plays out will be learned from watching the actual headlines as they unfold later this fall.

Martin Armstrong has been back on the podcast circuit this week warning that his computer suggests trouble begins next week. I just laid out the timeline reason as to why I would agree. His computer also suggests much more serious trouble next year. For us, next year starts a replay of the time of the kings. They were nearly always at war with each other and their neighbors. This would be the timeline reason as to why Armstrong's computer calls a year long war panic cycle. Most important, though, Armstrong ties that panic cycle to the USA.

Match Dates

Syria Status

The link here is to a Zero Hedge article dated July 19, 2025, summarizing fighting in Syria. About 1000 dead. 80,000 displaced. This is spanning across the 2025-07-17 watch date for the first year of Jephthah judging. See Judges 12:17.

There is not much solid news from Syria, but this looks to be the venue for this watch item.

Gaza Emergency

The link here is to an article on The Cradle that details an agreement dated 2025-07-16, so the last year of Jair, that summarizes the results of a summit directed at trying to help the people of Gaza. There is not much ongoing press for the Gaza Genocide because there is not much anyone in the world is able to do to help. Fighting Netanyahu is as difficult as displacing ancient Pharaoh.

Armenia/Iran Border

The link here is to a post on X dealing with an agreement signed July 23, 2025, which authorizes a transit corridor along the Armenian side of its border with Iran. This effectively gives Turkey overland access to central Asia. Armenia appears to have a corrupt government. Iran is not happy. This may be more Zionist posturing towards another war with Iran. A private army of Americans will patrol that corridor, giving the USA a virtual land border with Iran.

Thailand/Cambodia

The link here is to an article on Armstrong Economics. It deals with an apparent war breaking out over a border dispute between Thailand and Cambodia. The border has never been fixed since the French colonized the area in 1907. There has been fighting off and on over this border for a long time.

Hal Turner also picked up on this headline. Hal added that Thailand is allied by the USA, while Cambodia is allied with China. Hal's implication is that if this is not just a random spat, still quite possible, then this may be an American attempt at starting war against China using vassals in Asia, no different than war against Russia in Ukraine. So this would be the start of the Asian front for World War III.

Hopefully this will settle down.

Shop Work

The 3d printers were powered down this week to work on a long list of stuff that had been bugging me. Doing maintenance is not particularly easy because it means getting into the 3d printer enclosures. These are stacked and packed in with extension cords on the floor. They must be moved around in order to get into the printers themselves. Given the limited space in the shop this means shutting them all down for this sort of maintenance. Like shutting down a factory.

This work involved installing a new MMU kit on 1 of the Prusas. Nozzles where changed to the recommended type for both of the Prusas with filament feeders. These nozzles need less purging between colors.

The enclosure wiring was changed so the filter fans do not run all the time. The fans were setup for ABS which wants always running fans. PLA does not need fans like ABS.

The holders for extra printer beds were moved around, and a couple new holders 3d printed and installed. These were on the wrong side and not easy to reach with a screw gun unless the printers were moved out of place.

2 new beds were added to the set. The Ladder exhibit needs fresh 3d printer beds because the back of the parts are not covered in the final exhibit.

The Prusa Mini was removed to make room for another full sized Prusa MK4 which was ordered this week.

Once the farm was back in place and powered up, the Jacob's Ladder exhibit was started on the farm. Watch for early pics on Telegram.

Ryan and I also worked through some font related work that was needed for the Script exhibit. There is a standard set of open source fonts used for the ancient alphabets. The builder of that font family did not do a very good job of selecting characters from the Sarabit al-Kadim archaeologist's dig report. So, we picked a better set of those ancient characters and built our own new font. That exhibit also started 3d printing this week.

Both of these new exhibits are large and will be running for several weeks. But, it is nice to see the farm back in operation.

Code Work

We use the Git revision control system for all of our code work. For you programmers reading this, what follows will make sense. For the rest of you, please bear with me.

Since there are only 2 of us, and we normally work on independent projects, we don't usually do much fancy branching and merging in Git. Git has been mostly used for history keeping, so keeping proof of work. We also use Git for file sharing and backup. Git is much easier and safer for file sharing than, say, a shared file system.

Given how so many things are going on in the Table of 400, it felt right for Ryan to start using feature branches in Git so he can work on the harder table rows without needing to deploy early drafts of those same rows on his weekly deploy cycle. Git was designed for this task, and we set out to make sure he could use it this way.

After figuring out the best Git commands for this problem, we found a bunch of places in the build environment that would work better with Git if we made some changes. In particular we were putting into the Git repositories files which were machine generated. This was redundant and causing many phantom merge conflicts.

So we spent time this week working through and fixing these problems with the build environment so going forward this work flow is easier to manage. Merge conflicts now only exist in real places and then not very often.

Headline Review

The following general headlines caught my eye this week.

Barack Obama and Russia Gate

Tulsi Gabbard, Treason by Obama

Long Form Russia Gate Report

The top link here is to a Zero Hedge article covering what is known so far about Barack Obama's efforts to stop Trump at the start of Trump's first term in office. The second link is to an RT article covering the same material by RT. This is being called treason, which is a very rare term to be used by lawyers. The 3rd link above is to another Zero Hedge, long form, article covering the details. This for the record on what is known so far.

This headline is interesting because Obama was the 2008 fulfillment of a plague related headline during the 2008 financial crisis. Obama was the man, the Arab, normally Swarm of Flies, who would sleep in Pharaoh's bed. The land would be ruined before his departure. At the time we wondered where Pharaoh's bed may be. These days we know. That bed is in the White House. Pharaoh is whomever rules Israel, currently Netanyahu.

Obama, of course, has been running the show for a long time. Even the current Epstein File mess may be his doing to undermine Trump yet again. Obama was often thought to be the mind behind Biden's strange presidency.

In any case, references to Obama as the mastermind behind the Russia Gate Hoax points back to the prophetic over this man. The prophetic story from 2008 suggests he will still be pulling strings when nuclear war hits North America. Obama is not likely to be touched because he is a former president, and normally has Presidential Immunity. But, watch Obama's former aides.

Maybe AI Won't Replace You

The link here is to a Zero Hedge article describing the real problems with AI. Short answer, AI engines are usually fake. They don't actually simulate intelligence. Instead they read enough to be able to fake an answer. My opinion, this is not good enough for anything other than entertainment. Certainly not for most professional work. Say Law, or much else. I've been asked if I think AI might help with our work. I doubt it.

Rogue AI Wipes Out Company Database

Another interesting AI related article from Zero Hedge. This time some fools playing with AI ended up with that AI engine wiping out a production database. I've been asked if I think AI might help with our work. I continue to doubt it, at least not any time soon.

Dugin On Sacred Return Of Politics

This is a written interview of Alexander Dugin. He was asked a series of questions about a recent book of his. Dugin is of course an influential voice in modern Russia. He was previously interviewed by Judge Nap when the judge visited Russia.

Dugin seems to sit between Orthodox Christianity and modern politics in Russia. He is an interesting voice for understanding how Russia views the west in a general sense. I have been working to learn more about Orthodox Christianity because Protestants generally don't know anything about Orthodoxy. I have been learning from Dugan. I plan to return to issues related to Orthodoxy in future blogs. This interview is just the start.

In the interview above Dugan explains how he sees politics as always ultimately being based on religion. (I agree, just by watching American politics, the Democrats and Republicans form 2 competing secular religions.)

Dugan is very technical in this, mapping modern political systems of thought back to ancient systems and their ancient religions. For Dugan, this is especially not a good thing when it comes to the west. From Dugan's perspective, the war with NATO is Christian Russia fighting Satan in the west.

This is because none of the current political philosophies in the west are based in Christianity. Christianity in the west no longer informs politics. Once the Soviet Union collapsed, Orthodox Christianity returned to Russia.

The question for the rest of us: Which side, if any, will Joshua take in the war? Orthodox Russia is fighting Satanic Israel's vassals, the EU and the USA. According to Dugan, Russia is fighting Satan and this is the end-times fight.

Of course Orthodoxy is still based on an edited text. So the Orthodox side is not clean either. Russia also has an Israel Lobby. So the Russian side may be better, but it is still not an ideal fighter.

Will either side win? Can any side win a nuclear war?

Hard questions.