What About God?

This blog continues the discussion about divine names, this time the generic term god. We look at examples from Korah and Balaam. Also, notes on the Hong Kong tower fire. Then long notes on current shop work and finally a headline review.

Divine Names

Ryan has continued to work on the problem of divine names. He spent considerable time this week updating the tags used throughout the text to allow for pretty much all possible substitutions from the family of divine name related words as we know in the BRB into other words as we expect to see in the TT and related apps. This week he was doing the hard tagging work to make this an easier and more efficient task going into the future.

As he was working on the technical side of this problem, he realized the word "god" was also involved in the tampering of the editors. It, too, appears to have been substituted in places where Joshua's name may have originally been found. So he went through and included it in the general family of divine names so it can be handled in the same way as all the other related words.

This word also has issues related to plurals and capitalization. Sometimes it is used as a name, or part of name, and is conventionally capitalized. Think of other English words like "president." It can be used alone as a reference to the office. It can also be capitalized when combined with personal names, like President Trump.

This gets still more complex when there was tampering of the divine name, and when personal names may have been substituted to the generic terms like Master, God, Messiah, and so on. This is not really this week's work to solve, but it is this week's work to get the tooling correct so going forward the tooling allows fixing, or at least experimenting, with anything that may be found across the text.

Thought Experiment

Here is a thought experiment to help see some of the problems that are still ahead.

Is Solomon's god Yahweh the true god?

As Solomon was editing divine name references into the earlier versions of the inspired text that were passed to Solomon, did Solomon always use Yahweh as the substitution? Even worse, did a later editor make even more corrections? Say Ezra who was needing to conform to his commissioning king who himself followed the "god of the skies."

You can see the conceptual problems. God, as a term, may be replacing Joshua as the personal name found in the original inspired text.

So the base vocabulary word needs attention in Ryan's current work and it will become a family of complex problems when it comes to recovery work here soon.

In the end, the text is going to demonstrate by example what it means to break commandment #2, You will have no other gods besides me. See Exodus 20:3.

Other Work

Ryan suggested some other examples for this week's blog in order for readers here to think about what he is wrestling with in the text. It turns out the meaning of stories shifts around in subtle ways based on what terms were original to the inspired text. So there is tension in the work because the versions that will show up in the TT will have unusual tone compared to what we know from standard Bibles.

This is not new, of course. Ryan has made these sorts of word substitutions for a long time. But the tooling being put in place this week gives more freedom as to how the TT will develop using this new tooling.

Korah's Rebellion

The link here is to the story of Korah's Rebellion, found starting at Numbers 16 in the BRB.

This is an example of a complex story that appears to have been through multiple layers of editing passes. Presumably Solomon and then perhaps some other editor later on, say Ezra, made changes to the Korah story.

The story of Korah is referenced in Jude 1:11. At that location there is an alphabet related run against key words and names, so Korah is most likely an inspired story. Without Korah, that Jude series would break.

But, scanning the original Korah story, there is trouble. It has likely been bulked up in various ways. Ryan has faded out the stories involving censors as these verses are likely coming from Solomon, see the FS tags. Solomon was into smoke in his temple and likely added smoke stories to Korah in order to introduce smoke earlier in the story. By editing Korah, Solomon was warning future smoke bearing temple workers to obey the king.

The Jude reference still demands that there must be a core story involving Korah's rebellion against Moses. So once Solomon's smoke is out, there must still be a more conventional story of rebellion against Moses.

The fundamental problem is that Korah and some number of others decided to oppose Moses once everyone was out of Egypt. They did not like the way Moses was the leader. Korah and his followers did not like the outcome, at least so far, as they saw it.

Their claim is going to be that everyone, or at least the leaders, are holy (so special) and that "master" is among them. They then claim Moses is lifting himself above everyone else. They do not think Joshua is doing this. Which, of course, is proof that Joshua is not really among them. To be fair, they may not know much about Moses' original call from Joshua, nor what Moses did before pharaoh. In any case, they are trouble for Moses, because they pull the wider audience away from Moses, and thus away from Joshua's leadership through Moses.

So now, think about the use of vocabulary words in this passage. The BRB is using the word "master" in keeping with the Aramaic word found in this story.

The Aramaic term master usually implies the Aramaic scribes, who were forced to keep up with Hebrew edits, saw that the Hebrew was blaspheming against the then known personal divine name. Master was the Aramaic abstraction of a known personal divine name, provided of course the story was inspired. So Joshua is a good candidate for the inspired term in this Korah story.

We know how it ends, of course. Joshua is going to make an example of these men in order to demonstrate that there is supernatural power in the god whom Moses is following and whom Moses is representing to the assembly.

This sort of demonstration was important because it would give Moses standing authority to speak for Joshua across the remaining decades that would follow in the wilderness.

With Korah as a simple to understand warm up, we turn to Balaam.

Balaam

Balaam's story begins at Numbers 22 as linked here in the BRB. We are now at the other end of the journey from Egypt to the promised land. This is a story that is in the approach to the Jordan river. Balaam is another name referenced in Jude 1:11 so the story of Balaam has at least an inspired core.

In the case of Korah, the likely main addition involved smoke. In this case the likely addition to Balaam involves a talking donkey. This would be the same editor as added Jonah's whale, so a late editor. In both cases the theme may be cursing God's people, so Mordecai is a good candidate as the editor. There is still a less famous core story to Balaam. Let me review.

Balaam was an interpreter of dreams. He was from Ammon. He was called to curse the heirs of Jacob as they were preparing to cross the Jordan. You don't need to read very far into this story to find green text. See verses 7 and 9 for examples. God was speaking to Balaam, which is why he was called to the task. He will eventually give up on cursing those whom Joshua had blessed.

Green text, by normal BRB markup conventions, is text being spoken in divine voice. But who, exactly, is speaking here? The markup is green because we can easily find the generic term "god" as the one who is speaking to Balaam.

This is one of the examples that Ryan found where he needed to treat "god" as part of the family of related divine name problems. Not that this particular case demands any sort of substitution into the TT. But it might. Here are some of the issues.

As it reads in the BRB, this is an example of Joshua speaking to Balaam. There is no other god who speaks. So it must be Joshua. But the text is using the generic term god because Joshua's name is unknown to Balaam. This works to explain the structure of the passage, but it has problems.

The account itself is written by an inspired writer to friendly readers. We, as readers, know Joshua's name. By the time we get to this story, we have been reading about Joshua since long before the accounts of Abraham and his immediately family.

Joshua is a name not unknown to readers. So why would an inspired writer use god instead of Joshua's own personal name? Maybe this passage was not originally written this way.

Did Solomon substitute Joshua for Yahweh, as Solomon did everywhere, and then some later editor substitute out Yahweh for God?

The candidate for this second level of edit would be Ezra who may have been dropping Solomon's Yahweh terms in order to satisfy Cyrus who followed the "god of the skies." Ezra has the general problem of serving 2 masters. This may indicate Ezra edited a second time against an earlier editor.

The use of the term god, where Joshua makes better conventional sense, may always mark a second editing pass by Ezra.

Hopefully, this is enough so you can see the problems the text is presenting once the family of words related to divine names becomes generally untrustworthy.

Audit

I continue to track carefully what Ryan is working on because there is a letter level recovery task that awaits. The conceptual problem for the audit has become more complex.

Every divine name reference that we find in the text is going to need to be audited against all other possible divine names. Until this past few weeks, we have not even known this problem exists.

Shop Work

This week, because of a sore foot, most shop work time involved laptop work. As part of that, I did some light editing to the introduction at the top of Paleo.In. There are also now permanent blog links in the blog section that point at blogs with ongoing watch dates. The Plagues series we start in 2026 as well as the 2029 Noah date series now have permanent links.

By mid week I was able to stand all day, so I fired up the 3d print farm yet again. Watch for pics on Telegram.

Chests

My first goal was to finish up open issues with the Chests. The immediate goal was to slightly enlarge them so their interiors would hold exhibit bases with a 6 x 6 grid size. The River and Mount of Olives exhibits will be built to this size.

While I was at it, these parts needed nap marks and overall part labeling. That resizing design work was mostly done a week ago, but this week I was cleaning up finishing touches and starting the reprint.

Some of the panels on the chests needed some additional attention. There is a conceptual problem driven by the Megiddo Mosaic floor. That floor has an area where 4 different boxes are drawn on the floor. The floor has artwork for those boxes too, which seems to inform sets of 3d models.

When I first designed the chests I assumed one of those boxes was mapping to the Table Exhibit, which is the copper series of models. I thought the floor was leaving out the Mount of Olives Exhibit, which is the gold series.

As I cracked open these design files again, this time, I saw the boxes on the floor as ignoring the table. That Table exhibit is captured in another area of the room itself. So the place on the floor where I had thought I was looking at the table I was actually looking at the Mount of Olives Exhibit.

I pulled out the puzzles from the Museum of the Bible and looked again at that floor to see if I could understand the story of the floor as it explains the Mount of Olives.

This time, I could finally explain the floor's decoration for that Mount of Olives Exhibit and I was able to reasonably explain that otherwise strange artwork. This includes using the strange path between squares as seen on the floor itself. It is amazing how many months it has taken to fully understand the artwork from that floor.

The redesigns for the chests are now finished, and the reprint began this week. Not all pieces need to be reprinted, and some will be reused from the existing chests, especially much of the interior surface parts.

Tiles Exhibit

The other exhibit that was reworked this week is the Tiles Exhibit. This is a simple set of 2d tiles printed in colored relief that show all of the 2d shapes used across the entire set of 3d models. Several of the shapes get printed 2 times in order to mimic the 2d sides on the related exhibits. I am debating a few of the parts, but it looks like 124 such tiles make up the set.

This exhibit is used to demonstrate the 2d projections from the 3d objects themselves. The original set of dreams in 2009 that started this work is best explained using this exhibit in combination with the various birds found in the other exhibits.

This set of parts was first printed a long time ago. At the time they were printed with an 18 inch cubit rather than the current 22.5 inch cubit. The design files were not in the current exhibit Git Repository and not to the current coding conventions, so these parts needed serious design work before being reprinted.

Going along with more recent standards for parts like this, they also needed to be numbered so anyone playing with them later could identify them in an understandable way. I could also see the need for a color scheme change that would point at the related exhibits. Viewed this way, a few parts, like the alphabet, need to be in both the silver and copper series.

I also felt they needed a carrying case, which they never had before. I could easily design up a case that would match the same design style used in other places. There really isn't any special artwork for the exterior of such a case, but I was able to come up with a geometric design that works well with these tiles.

All of these issues were addressed in the design files for this exhibit. Reprinting started on one of the MMU equipped 3d printers in the shop this week. Perhaps this will finish by the end of next week, we'll see, there are many parts to print.

Voron Calibration

Once I was back in the shop, I ran the new Voron through normal calibration steps. This includes gantry squaring. It is finally ready for regular parts printing as part of the farm.

The first Voron was back on the bench to fix a problem with a droopy cable. The other 2 have a steal carrier for the electrical cable to the hot end. This printer was upgraded with parts from Amazon. There was no matched cable carrier for that upgrade. I tried using Nylon filament, which work originally, but eventually case heat caused that to drag down, eventually dragging the bed.

The problem was fixed by using a scrap piece of steal carrier from the newest Voron. It isn't long enough for the entire cable, but it works like a flag pole off the hot end. Good enough. That printer is also back available for parts in the farm and has been printing web related parts for the chests.

New Elegoo Printer

I mentioned last week my adventures with the new Elegoo Neptune 4 Max printer. Let me continue the saga this week.

I settled on using the Paleo Ha as a test case. It is square so it cannot be rotated to get away from the edges. It is 410 mm each way, so should fit on the printer's advertised 420 mm bed size. I figured the Ha would be the best test case. If I can get it working, then everything else will work too, including a set of huge 3d exhibits that will also have max print sizes at 410 mm. So with this letter as my test case, I set out to see if I could debug print problems.

The obvious print problem was the top of the Ha, so the +Y edge of the print bed. It was obviously cooler than the other 3 sides. That cool edge was causing bed adhesion problems, which would cause a lifted print to bang the print head and fail the print. That layer shift problem last week was really a bed adhesion problem caused by a cold bed.

The 2 obvious changes to help a cold bed were to 1) turn off the part cooling fan. There is a switch on top that makes that easy. Then 2) heat soak the bed before printing. Heat soaking, using an ABS temperature preset, with a bed temp well above that needed for PLA, was the best trick.

There was a 3rd, far less obvious fix, which was to turn the printer's textured bed sheet over. The back side has a higher temp rating and a courser texture which adheres plastic better than the PLA specific front side.

All of these changes, each with different test prints, did not fix the problem. Adhesion problems were still there, though obviously less trouble with the courser bed.

So then I tried moving the Ha nearly all the way to the front, or -Y, on the printer. The print was still failing, but now in areas that worked before. This still with bed adhesion problems. Fresh paper towel and 99% IPA and careful cleaning seemed to help.

But as I looked at this more carefully, the part was against the left edge and not the right edge. It wasn't centering left and right. What was wrong?

I got out my measuring tape and found the actual physical bed size is 430 by 430 mm. This is 10 mm more than advertised. This is a problem because the software must be told the actual bed size. Elegoo is only advertising a 420 mm bed because they know the edges are cold. Fixing the configuration value in the software meant I had control over centering and could then again control carefully away from the back edge of the printer. Finally, parts were printing to completion. Watch for pics on Telegram.

Watch Dates

We remain in the 70 day window that began with the start of the day-for-a-year replay of David's life. 2025-12-08 is the start of David's reign. More on that next week.

Major Hong Kong Fire

The link here is to a Wild WeatherUS video on Youtube detailing the 2025-11-26 tower fire in Hong Kong. This is late in terms of an echo to 911, but it is before any future prophetic dates. It is similar enough to the 911 tower collapse events that it is important to note for the record. In this case no full building collapse was seen, but the death toll is expected to be quite high.

Bamboo scaffolding was surrounding 7 large residential buildings in Hong Kong. This scaffolding was placed for exterior building refurbishment. It caught fire and spread up and across the complex. Only non-flammable metal scaffolding should ever have been used. Bamboo, of course, is very flammable.

There have been several other large tower fires where flames ignite on flammable exterior materials. The updraft along tall building exteriors fans flames like a dangerous chimney fire. Anyone who has ever heated with wood should know the dangers of chimney fires. The height of the fire creates updraft in ways much worse than in otherwise shorter building fires.

That chimney effect can bee seen in the videos of what happened in Hong Kong. Several thousand people are thought to have lived in those towers. A prophetic match to 911 would expect an eventual death toll around 3000 people. As of this writing, the death toll looks lower, but this may be a problem of Chinese under reporting or not yet knowing how many have died.

Headline Review

The following general headlines caught my attention this week.

CIA Enforces Apollo Myth?

This link is to a Health Ranger post on X which embeds another post, which itself embeds a video. The video is by someone tracking down myths related to NASA's Apollo moon program.

At the end of the video there is a very strange reference to the CIA, which is why this is so strange. The CIA apparently enforces the myth of the Apollo program. Why would the CIA need to enforce the myth if it were true that the USA landed on the moon? This is perhaps the strangest bit of evidence ever offered that the moon landing never happened.

Lord's Prayer In Norse Runic

The link here is to a Discovery Future channel video on Youtube. It explores a discovery in south eastern Canada of a very large inscription of the Lord's Prayer carved in stone using the Norse Runic alphabet. This, of course, from the middle of the Sermon on the Mount which we dealt with last week.

I used that same Runic alphabet to figure out the sound for the Wa letter in Paleo. That alphabet faded out as the Latin alphabet took over in northern Europe.

Someone who used that alphabet, and who knew the New Testament, sailed into, or was marooned, in Canada and left behind an amazing monument. It was covered in dirt until a recent storm knocked over trees that had grown above the monument. When the trees blew over, the root ball lifted and exposed the very large carved stone surface.

There are other Runic inscriptions across North America. We once visited a much smaller Runic inscription in south east Oklahoma, likely a burial marker. But not much else, especially of this scale, has been found.

Putin's Response to 28 Point Plan

The link here is to an RT article summarizing Putin's remarks given at a press conference on Thursday, November 27, 2025. Various American officials have been working on a proposed peace deal which has been circulating for about 2 weeks.

The American side is expected to visit Moscow this coming week for more talks. So far, the Russian government has had no input. Putin remains very diplomatic over the whole process. As he points out in his remarks, the western alliance itself is fighting within itself in various ways.

Some in the west want peace, most only want a cease fire in order to rearm Ukraine. Zionists need to conquer Russia in order to establish a word capital in Jerusalem. Zelensky already works for them.

More Later,

Phil