Notes on Adonai

This blog explores the Adonai divine name. Then the story of Joseph revealing himself to his brothers. After that, shop work and a headline review. Finally, a special section on trouble with carbon fiber infused 3d printer plastic.

Divine Names

Ryan is continuing to work through the tagging tasks related to the divine names study. This work has caused some breakage in the TT and related apps which he is also currently cleaning up.

This family of studies is causing us to see details in the text which were nearly impossible to see until we could start unpacking the likely original divine names used throughout the text.

The major divine names are Joshua, Yahweh, Elohim and Adonai. There are, of course many other words and abbreviations. Yah, for example, is probably just a short form of Yahweh.

I had the local Christian radio station playing in the shop for some Christmas music. For the filler, between songs, they were explaining the origin for many of the famous Christmas songs. As part of that, they defined Hallelujah as meaning praise Yah, which for that radio station, was just another name for god. All I could do was cringe. The short form of Solomon's false god is not another name for god. Yah is a small part of the pantheon of false gods found in the Bible.

In any case, I am starting to form a mental frame of reference to understand what is going on when someone starts talking on the radio. This divine names study pervades nearly every other study in the Bible. It is overlooked by the people who should know better.

We are working under the assumption that different divine names mark different editors. This with the condition that later editors could have changed the divine names used by earlier editors.

So Yahweh is going to be Solomon's work. Elohim is going to be Ezra. I have covered both of these in previous blogs.

This week, Ryan has gone far enough along in his work to suggest that Adonai is a marker for additions put into the text by Mordecai. Let me show you an easy example of this.

Against Edom, Against Arabia

The link here is to Isaiah 21:11 in the BRB. This is the start of a passage that runs through verse 17. It is a pair of prophecies against Edom and against Arabia.

You will see an FM medallion ahead of both of these prophecies, indicating Mordecai is the likely editor who added this to the text.

Why would this be Mordecai?

For content reasons. Mordecai is near the top of the empire with 120 provinces across the known world. He set in motion something like a civil war when the Jews fought back against the locals in each of those provinces.

These 2 prophecies are likely part of Mordecai's condemnation of the locals in those various provinces within that empire.

So you can read down through the details of these passages. Then look down to verses 16 and 17 where there is something like a signature line. In the Aramaic of these last 2 verses, there are 2 references to Master. Normally these are hiding Yahweh references but in this case the first reference is hiding a Hebrew reference to Adonai.

So what is going on with Adonai?

It looks like Mordecai signed his work using his signature divine name, Adonai. Then, later, when Ezra is leading the return to Jerusalem, Ezra comes along and uses Yahweh. Ezra also puts the emphasis on Yahweh by writing "Yahweh the god of Israel" so there is no doubt whom Ezra is referencing. Ezra is doubling down against Mordecai's Adonai.

Ryan has placed an FE medallion ahead of that last phrase to mark how this is likely an Ezra edit atop a Mordecai edit.

These verses would then also be an example of following the law of Babel. Nothing can be retracted. But additions are always allowed. Ezra is fixing Mordecai's addition with Ezra's own further addition. Ezra is bringing Mordecai's work in line with the temple system at Jerusalem.

Joshua, A Family Secret

In the blog 2 weeks ago, I used Luke 2 as an example of how the name Joshua was both hidden from the public, and given to Miriam and Joseph. This was the name they were to give their baby. In terms of the public text of the time this was likely a reference to Joshua son of Nun. It was not a divine name reference in public texts of their time, so the divinity of Joshua was likely hidden through his young years.

That name Joshua was not given publicly until Joshua's 8th day. So until that day, the name Joshua was a family secret.

The day of Joshua's birth, the shepherds showed up at the manger and used that same family secret name. They would report what they had seen and heard. They would use the name Joshua which was proof they were not making anything up. Apparently unlike Joseph, Miriam cherished this in her heart, knowing something amazing was going on. She knew this was important because it had been pronounced from the skies.

The use of Joshua as a family secret, in modern cryptography called a shared secret, like a password, also shows up in the account of Joseph in Egypt. The divine name, Joshua, is a shared secret between Joseph and his brothers. The Egyptians are not party to this shared secret. It is an important detail to the plot that is otherwise lost because of how divine names were changed. Let me show you.

Sent For Food

The link here is to Genesis 43:11 in the BRB. This is the start of the story where Jacob sent his sons back to Egypt for more grain. With the Keyword God markup turned on you should be able to follow the divine name story that is embedded within this passage. Let me hit the highlights.

Jacob's Commissioning

At Genesis 43:14 Jacob is talking with his sons before they depart for Egypt. You will see "God Almighty [El Shaddai * Joshua]" at the start of this verse.

Let me explain this notation. In the BRB itself, the Aramaic reference to the divine name is marked with the normal green Keyword God, so "God Almighty" is the English for what is actually in the Aramaic. So in this unusual case, there is no Master hiding a Yahweh reference. As the Aramaic word for god hides Elohim, this Aramaic might still be hiding Elohim Almighty in Hebrew. The contents within the brackets shows the Hebrew side.

Normally, within the brackets, Ryan will place the Hebrew term or terms found at this same location. So El Shaddai is what is found in Hebrew. El is God and Shaddai is Almighty, so in this rare case the Aramaic and Hebrew are the same. Aramaic is not hiding an Elohim Almighty as would be allowed by the Aramaic.

When there is an asterisk within the brackets, this will mark the start of a substitution suggested by Ryan. Normally this will be * Joshua as here. But it can be anything, even back to false divine names, like Yahweh. Ryan explained to me that the use of the asterisk is a very old convention used to mark up candidate insertions. So by using this symbol, the BRB is using a conventional notation to mark what should be put back.

So the text beyond the asterisk in the BRB is a replacement text that will show up in the running text of the TT and related apps.

Returning to Genesis 43:14, this strange case is also leaving a clue for later audit work. God Almighty might be inspired or else it might need to be converted to Joshua in order for it to pass audit.

Did Jacob use the term "God Almighty" when he was commissioning his sons for their trip to Egypt? Probably not. Why? Because Jacob knew Joshua by name, and because the phrase is used by editors in other places.

Joseph's Don't Fear

If you continue down the passage you get to the next divine name references at Genesis 43:23. Here Joseph is consoling his brothers that, "Your God, the God of your Father" has put silver in your sacks.

Why would Joseph use these exact terms here?

If you read carefully, you can see Joseph has Egyptians listening in. Because of that audience, Joseph cannot use the true divine name, Joshua.

Instead, Joseph needs to use the generic term, God, and then he ties it to the god of his brother's father. Though Joseph's brothers don't immediately get what is going on, Joseph is speaking in code about how the true Joshua god caused all this to happen. Joseph knows this because this is his mission. He is referencing Jacob's god because he knows Jacob follows the true god.

The same generic term for god is used in Genesis 43:29. Joseph still has an Egyptian audience so he still uses the generic term.

Joseph Makes Himself Known

If you continue reading down the passage you eventually reach Genesis 45. This is where Joseph is going to make himself known to his brothers.

Verse 1 indicates that Joseph ordered everyone to leave him alone with his brothers. Though verse 2 indicates those servants still heard Joseph weeping, and as Joseph had perhaps feared all along, those servants reported on Joseph to Pharaoh. There is either 1 or 2 reports, see Genesis 45:16, but it appears that Joseph spoke quietly with his brothers over some of his key points.

By verse 4, Joseph gathers his brothers around him closely. We might call it a huddle, so he could speak to his brothers in relative privacy. Within the conversation that follows we see Joseph referencing god in verses 5, 8 and 9.

In the BRB Ryan now marks these as likely inspired references to Joshua. That BRB notation now also means that Joshua will be the term that shows up in the TT and related apps. Why is Ryan suggesting this transformation?

The divine name is a shared family secret. His brothers could not recognize him by sight. Joseph needs to prove who he is to his brothers. Joseph knows this most interesting and important of their shared family secrets, the name of the one true god.

The family knows that name via Abraham. Nobody in Egypt is going to know that name, at least not as the name of the true God. Because Joseph could use this name, and did so with his brothers, this is why Joseph could be believed.

Note how this story involving Joseph has similar structure to the stories in Luke 2. The plot complication in both of these stories is the same. Who knows the family secret? Who knows the name Joshua?

Ryan still has much, much more work to do in order to get full control over all references to the divine names. This is a time of heavy editing which is showing up in the BRB, TT and related apps with occasional breakage. Ryan is fixing those as he finds them.

Watch Dates

We are currently in the day-for-a-year replay of the reign of David. The next interesting dates in this series begin around January 14, 2026, with the start of Solomon's co-reign with David. We will return to that next week.

Note, in this previous week, Netanyahu visited Trump in Florida. Alex Christoforou reported on his daily news report that most of the wealthy donor class had their yachts tied up in the region. Probably, all were gathered to visit Pharaoh who had flown in and was giving marching orders for war with Iran. These orders were likely given to Trump and Trump's minions.

There may still be temple related headlines come late January, but the bigger headline may yet be another war in the Middle East.

Shop Work

This week in the shop I started with a review of the existing exhibit related projects. I wanted to make sure they are all current in terms of design features. Perhaps the least current design was for the Joseph's Robe exhibit. So I opened up the design files in order to bring it up to current standards.

Robe Design Changes

The big deal for this particular exhibit is getting the correct placement for the 660 individual tiles that make up that exhibit. I have learned quite a bit from the other exhibits and the first goal was to get the row and column numbers 3d printed on the back of each individual tile.

This slows down the printing process because each tile is now unique. But it also makes it possible for anyone doing the assembly to have a hope for getting it assembled correctly.

In looking again closely at this exhibit I realized there is some affinity to the Staff exhibit. To bring these exhibits into agreement, the vertical blank columns on the front of the Robe needed to be removed. I could do this simply by reassembling the existing exhibit. Just a few trim pieces needing to be reprinted. The overall exhibit size reduced from 5 panels to 4, making transport easier.

Since the last time I built this exhibit, I also found a better way to handle sectioning of large panel style exhibits. Previously, I 3d printed replacement back panel parts that could be used to permanently assemble the individual panels into a large single display.

At some point in the past year I realized I could achieve the same goal by using parts along the edges of the back of the exhibit that would rotate. This design change will also work on other similar exhibits. By rotating parts rather than replacing parts, there is no need for 3d printing what were effectively spare parts. These extra parts tend to get lost, as they have done in the current shop over the past year. So I also set out to fiddle the existing exhibit so I could try out this design change.

This particular design also gained a general assembly file that can be used to check final assembly against a known good display on the computer. I also now generate the tile pattern from software so there is little chance of design issues for each tile.

So I 3d printed the changed parts and combined those with existing parts to rebuild this exhibit. It turned out nice. Watch for pics on Telegram.

River Birds

The 3d printing process was started this week for the birds and bird cages that are used on the River exhibit. This is the easy part for this exhibit. Watch for pics on telegram.

Ladder

I stopped printing the ladder when I adjusted panel height. That exhibit was started again, this is now the 3rd iteration for the ladder. Changing panel height changed the length of the links which makes each ladder taller. Watch for pics on telegram.

Yellow Lid

The lid for the yellow chest was finished with reprinting this week. Watch for pics on telegram.

Blue Front

The front of the blue chest was also reprinted this week. The story of this panel has not changed, but the colors shifted with green for grass along the river. The elevations needed to change to make the grass the highest feature, so there was a tedious redesign to get this cleaned up. Watch for pics on telegram.

Staff Design

The 3d design for the shepherd's staff was worked out this week. There are other staffs in the River Exhibit, but those should be simpler.

This stand alone staff eventually carries the Paleo letter string for the Commandments. This design was done to proof the design parallels to the Robe, which turned out OK. The robe is as wide as the staff is long.

The staff needs an audited, letter-perfect, copy of the 10 commandments before it can be printed correctly. I may look more closely at that problem here soon.

New Desk

I am settling into a work routine where I can sit most of the day at the new desk in the shop. This is helping productivity. It is nice to keep the printers within ear shot when I am doing computer work.

Headline Review

The following caught my attention this week.

AI Slop Problem

Last week I discussed some of the problems of AI generated garbage content on Youtube. The link here is to a recent video that explains more of the problem. External content creators are also flooding Youtube with cheaply generated AI garbage.

Depending on the subject, there is a MASSIVE personal safety risk to much of this sort of content.

Russia Advances In Ukraine

The link here is to an article on RT that explores the general advances that have been made by the Russian army, especially across December, 2025. The Ukrainian lines are generally falling, Russia will be able to more easily move west in the months to come.

Silver Shorts Implode

The link here is a to a post on X that details trouble with the silver futures markets in the USA. On the Friday after Christmas the NY Fed was tapped for $17B to bail out some bank who was caught in a Silver short squeeze. The price for physical silver in China is way above current prices in the USA. American banks are loosing control of the price for this (once upon a time) monetary metal.

Other reports indicated China has now banned the export of silver from China. We also understand that coin shops in the USA are currently not buying silver coins, presumably because they fear a collapse in the price of silver.

This is a possible prelude to an echo of the 2008 financial crisis that begins again with prophetic dates mid January. More on those dates in a future blog.

Hal Turner added on January 2, 2025, that over the previous night the Fed injected another $105B in order to keep the banks afloat. Financial troubles are brewing, as we would expect for a replay of the 2008 financial crisis.

Europe and Nuclear War

The link here is to a Glenn Diesen video in Youtube. His guest is Professor Sergey Karaganov, who is well placed in the Russian establishment. He has some things to say about how the war in Ukraine can eventually go nuclear should the Europeans keep threatening to escalate the war. The short answer is Russia will not engage in a ground war with Europeans.

This is more evidence in support of the idea that the timeline for Noah that begins in 2029 will be a nuclear war, not a conventional war.

Russian Cavalry

The link here is to a 12 minute Youtube video on the HistoryLegends Flashpoint channel. I am posting this in response to my own comments about the Revelation passage dealing with 200,000,000 horsemen. I speculated how that Revelation reference might be a problem of ancient war vocabulary needing an uplift to current weapons systems, like Tesla robots.

Seems I should not speculate so quickly about a technical problem with the text. The Russians are using at least some horses and horsemen in the Ukraine war. This video explains. The host on this video is as equally baffled as everyone else.

If that wasn't enough, I did get a phone call from an old prophetic friend who does NOT know about our current work. Seems visions of horsemen in this upcoming war are also going on with prophetic types. Beware, this may matter once there is no gasoline.

New Years

The link here is to a post on X by Stew Peters. It is hilariously captioned. "Donald Trump is spending New Years at Mar-a-lago with the president of the United States." Not a typo. Quite funny.

Max Blumenthal on Dialog Works

This video starts with Netanyahu's trip to Miami. The host, Nima, who normally records in Brazil, was in Tehran, Iran. Max visited there in May. So Netanyahu's orders to Trump to attack Iran are personal for these guys. Interesting background.

Attack on Russian Palace

Just before Netanyahu was visiting Trump in Miami, Zelensky also visited Trump. After Zelensky left, about when Netanyahu was arriving, there was also a Ukranian drone attack on Russia. This attack was publicly said to be targeted against a presidential palace that is remote and north from Moscow. The timing alone is strange.

The link here is to a Dialog Works video on Youtube. In this video Nima interviews John Helmer who is based in Moscow. John provides some evidence that this was really an attack on one of Russia's nuclear control bunkers located in the same area. This target explains strange behavior from the Russian side in the hours after the attack.

The west collectively is escalating to nuclear war. They do not want peace with Russia. The rest of this video suggests Russia is now looking for a pause in the Ukrainian fighting. Not good if so. The west needs to rearm, which is why they want a delay.

Daycare Fraud

The link here is to a post on X dealing with daycare fraud. This has made national attention from Minnesota, where that state government appears to be funding Somalia in various ways.

The link here deals with Washington State Senator Lisa Wellman who has filed legislation to prevent release of similar data in Washington State. There is a strong likelihood that the crime ring pattern in Minnesota is copied around in other states. This post suggests Washington State has a similar crime ring.

Evolution Myth

The link here is to a Tucker Carlson video on Youtube. In this video he interviews James Tour, a world renowned chemist. James explains there is currently no known path for taking basic chemistry and creating life. Evolution is thus a myth, with none of the normal science that would make it at least a theory.

Shop Safety

There was 1 last link that I want to share this week. The link is below. It won't make much sense without a little personal testimony on shop safety.

When I first graduated from college, I worked in a factory where parts were made in a rabbit's warren of factory clean rooms. I wrote software for the final product testing machine. Our station was mostly outside of the clean air. My coworkers were also mostly writing software, so we did not need to go into those clean rooms directly.

We sat on the dirty air side of a glass wall that surrounded the clean rooms. We were in the return air flow, so papers dropped on the floor would float in a cushion of air.

We had a sister factory in Silicon Valley that was designed similarly. They made different models of our product line using manufacturing steps similar to our own.

One weekend that sister factory was on the national news. That factory was shut down for maintenance. A welder was working in the attic where the blowers were located that drove the clean room air flow. He was adjusting the ducts and welding them back together.

A spark from his torch fell down through a crack near the ducts into the main manufacturing floor which then triggered an explosion in a dumpster. It was so powerful, the dumpster itself busted through 2 cinder block style concrete walls before landing in the empty employee parking lot. Thankfully, nobody was hurt. The attic itself had a concrete floor, which protected the welder. It was news footage from the mess outside that made it on national news.

By Monday morning, everyone where I worked found out we were also shut down as a result of that Silicon Valley factory explosion. We also had regular office space, so we had a place to work. It would turn out to be about 3 weeks where we could not cross yellow caution tape. Just like our Silicon Valley sister factory, we were locked out of our factory too.

Nobody knew exactly what had gone wrong. And, whatever did go wrong also meant someone was careless in terms of factory safety standards. Both problems had to be fixed before anyone was let back in and the manufacturing lines could be restarted.

It turns out the chemical composition of much of the garbage in the exploding dumpster was the same as the propellant of the solid rocket boosters on the then flying space shuttle fleet. It was not as fine grained as the shuttle boosters, but under the right conditions could still ignite explosively. Low grade rocket fuel was an unintended byproduct of an early step in the factory.

There were also no published safety standards that would apply to that situation. Nobody had made rocket fuel in a high tech clean room before. OSHA standards would be changed as a result of the federal investigation of that accident.

But, since this problem had been overlooked, our corporate headquarters demanded a complete external safety review... Of every square inch of the factory. Even us software guys had to answer for every inch in our little corner of that factory. Every item, that was not stuff like you might commonly find in a regular office, had to have current MSDS data posted on the wall at each step along the manufacturing line. What is an MSDS you might ask?

Material Safety Data Sheets, MSDS for short, are available for essentially every imaginable ingredient that might be used in a factory, or created by a factory. Here is a technical definition, "A Material Safety Data Sheet (MSDS) is a document that provides detailed information about chemicals, including handling precautions, emergency measures, and potential risks to humans and the environment, aimed at reducing accident risks." An MSDS itself must comply with a series of other industrial standards, The Workplace Hazardous Materials Information System, or WHMIS for short, is the most important of those other standards.

You know you need an MSDS if you can smell the item, or if the item is flammable, or if the item is somehow otherwise dangerous, especially products built of fibers, like fiber glass insulation, that can float into the air.

Our computers had paper printers which had ink which smelled of chemicals, so we had long debates with our safety people. These were normal office printers, so would normally just be allowed. But we learned those regular computer printers were something nobody would really want to use, either in a factory, or in an office.

Note that modern inkjet printers do not outgas chemicals like the printers from those days. Nobody uses printer paper like we did in those days either.

Now, let me tell you my story.

PLA infused with Carbon Fiber, called PLA-CF

I bought a spool of PLA-CF, thinking it would help make some of the larger exhibits stronger, or at least more rigid. I purchased it from the filament factory in Vancouver, WA.

I used some of it in testing. It was gray. When I replaced that filament in the 3d printer with normal yellow PLA, I noticed a strange black residue coming out of the nozzle in the printer.

I've never seen such residue before, nor since. It had something to do with that manufacturer's plastic, but I had no idea what it might be. The yellow purge was showing that black particles were clearing out as I purged in the new yellow spool.

This past week I ran across the following video that explains those black particles.

PLA-CF

The link here is to a 16 minute Youtube Video on the "I built a thing" channel.

The video explores how carbon fibers are a useless upgrade to standard PLA filament for 3d printers. The host of this video has access to very expensive test equipment which he uses to explore what is going on.

This is a very important understanding as to what happens when carbon fibers are added to PLA. Carbon Fibers do NOT make PLA stronger because those fibers do NOT chemically bind to PLA plastic.

What happens instead, is that bubbles form around the fibers making the plastic weaker. Worse, those now loose fibers escape the plastic. By touch, or just into the air.

As soon as I saw that, I had flash backs to the story I shared above. I realized carbon fiber has no place in a regular, office grade, nor warehouse grade, 3d print farm. Carbon Fibers are dangerous. They need special handling, perhaps almost clean room handling, or at least ventilated hood handling which is used for some types of painting. In any case, there is no way a human working with a 3d printer should come in contact with those fibers. Nor should any end user nor salvage worker come in contact with carbon fiber infused plastic. I don't think it is possible to make safe-to-touch models using this stuff.

PLA-CF should at least come with an MSDS in the package. Websites selling this stuff need to also warn that this stuff is dangerous. Finally, if there is any possible use case for this stuff, the printers themselves need to be setup in strict factory conditions, not office nor warehouse conditions, like most 3d print farms.

The Voron printers in the current shop, for example, are designed to allow for external venting. So the attach points are there to add drier vent plumbing to those printers so they can exhaust to the outside. ABS, for example, does generate fumes, which is the use case the Voron designers were concerned about.

Anyway, this has been an interesting adventure in safety issues related to 3d printer plastic. Some of these plastics appear to be less regulated than they should be.

We will stick with the simple and relatively safe family of standard PLA plastics. We will not use plastics with any additives, especially not carbon fiber.

More Later,

Phil