Revelation Riddle

This blog frames a riddle that once fully solved might interpret all of Revelation. Before that, recovery work status, especially problems with kerning, commas, and preparing hardware for audit. Finally, a headline review.

Paleo Bible Work

I have been continuing code work on a new Paleo Bible app. It may be ready for a first release in another couple weeks. We'll see. The code is being drawn from the earlier Paleo apps that were on the paleo.in website. Those apps were last worked on in the middle of 2024. We have learned much since then.

The first change has been to build out code support for 2 different audit patterns, what are currently being called the north and south patterns. Eventually one of these flips in boustrophedon style. That code is now mostly finished.

The second change is the code related to kerning. The shepherd's staff is tightly kerned throughout, but it does not cover all kerning cases. The code itself must handle the entire manuscript so it must handle all possible kerning values.

Kerned text is eventually tested against the audit canvas, so kerning is the step after the audit canvas and before full manuscript testing.

Ryan and I have both been working this problem. Ryan has been manually running important keywords, primarily names. I have been working the code to show off all kerning data configured in the software. This shows up in an appendix to the new app. (Some of this was done in the Lex app previously.) All current kerning pair data needs to be available for visual inspection as a way to check that the code is correct.

We need examples from real words to confirm we know the correct kerning related letter offsets. This is the data Ryan is currently generating. He is testing against words and phrases that are almost certainly inspired, so we are not accidentally building a system that runs against, say, Ananias' words.

In this kerning work we've run into several new insights that I want to share here for the record.

Commas

One morning I was in the shower thinking about the software I was about to go work on and I realized there may be a way for the Paleo writing system to express what in English is a comma. This would be a mid-sentence pause. This does not need any changes in the 3d system. But in the writing system it would be expressed as 2 Dot characters in succession.

Currently, 1 Dot marks a between word break. This is the equivalent of a space in English. So 2 Dots could separate words slightly more. This would be the natural way to express a comma. This is a difference in word spacing that would matter at the audit level, so the use of a comma would be caught as an inspired grammatical element.

This also relaxes the overall audit system, and will pass more text than previously. 3 units of between letter spacing is the marker for an inspired Colon, which marks end of sentence. We already understand that spacing.

Note also that 2 dots used horizontally as a comma would help explain why 2 dots vertically are used for a sentence marker. In situations where the text is written by hand, the 2 different marks are visually very different.

After a long discussion about this, Ryan started watching to see if he could find a use of a comma in his name related audit examples. He found such an example. Let me share it here for the record. Let me give this example in English because we cannot do paleo well in the blog.

"Nebuchadnezzar, king of Babel" is a phrase that is frequent in the text. All the words in this phrase pass audit. These words are reasonably complex and have fixed legal positions on the audit grid. The trick here is the name "Nebuchadnezzar" and the phrase "king of Babel" are only legal when they are 2 grid lines, so 2 dots, apart.

Instead of seeing this as failing audit, it can now be explained to pass audit, but with an inspired comma between the name and the title.

This was very exciting to see because we are starting to reason about the running language system and then explain what we are finding. The use of a comma between the name and the title is the same as might be seen in English.

Kerning Pair Ambiguity

As I was bringing up the code to look at all kerning pairs I eventually ran into a strange case. It shows up in the word "Babel." Ryan was later checking this word by hand which caused him to even find the example I just shared above dealing with the king of Babel. (There is a strange favor on our current work.)

In the word Babel, there is a kerning pair of Ba to Lu. Ba has a tail pointing to the right and Lu has a tail pointing left. So at the canvas center line, which is the Paleo location of the English base line, the Ba and the Lu have 3 empty audit grid locations. This is so even when there is no punctuation between these 2 letters.

This is not a conceptual problem with the language, but it does create visual distance between letters at the end of words like Babel. For the purposes of punctuation and audit control over the entire word, those 3 units on the grid must be empty in words like Babel.

The Ba and the Lu must separate another grid unit if the kerning is then capturing a Dot. This gap grows even wider with the other punctuation. You can imagine that if a single Dot has extra space, the other punctuation characters will also have extra space when they land between Ba and Lu.

This case is unusual. In nearly all other examples, the punctuation is squeezed tightly on the grid between adjacent letters. Punctuation is NOT squeezed tightly in this case.

Vocalization

We know from a prophetic dream when this work started that the punctuation functions acoustically to suppress the vowel of the last letter in the word before.

Babel, for example, is spelled Ba-Ba-Lu, but it is pronounced Ba-Ba-L. That trailing u sound is suppressed because of the punctuation that always follows. That lack of a trailing vowel sound indicates to the listener that this is the end of the word.

So if we find a word ending in Ba and the next word starting with Lu, then the vowel in Ba is going to be suppressed to mark the word break.

On the running canvas, we must add punctuation after the Ba and push the Lu away by 1 (or more) units on the canvas. In this case the punctuation characters are loose and not geometrically constrained by the geometry of the adjacent letters. Because it is acoustically modifying the Ba, it still must be adjacent to the Ba.

The Code Problem

The job of the kerning code is to take letter strings and compute grid placement for those letters. Once grid placement is known it can then be drawn on an audit canvas. More importantly, a kerned string can then be passed on to audit related code. The audit system cares about WHERE letters land on the grid, not just their order. Using location is the main way for software to sift out uninspired running text.

The kerning code left over from 2024 presumed fully constrained distances between letters. It was built from what we saw on the Shepherd Staff. That code was not written to track loose, so geometrically unconstrained, punctuation.

I am currently working towards updating this code, but it will be a few days before this is completely done. This is a conceptual rewrite, not a tweak.

After this week's work I am starting to see that there is quite a bit of nuanced beauty in this language system.

Prepping Audit Server

We started getting notifications that our version of PopOS is now ready to be updated. PopOS is a Linux distro maintained by System 76 located in Denver. For the past 3 or so years the team there has been rewriting the desktop for Linux. This is an impressive and difficult piece of work.

Like any massive software rewrite, it has taken longer to deliver than they had first planned. But, the results are well worth the wait and very impressive.

As many users of Windows are now leaving for Linux, PopOS is well positioned to benefit from that migration.

I last looked at this when I installed an alpha version of PopOS on Flash, our 40 CPU desktop machine. (Technically, it has the main board for a server in a floor standing case.) That PopOS early version had some sort of bug where every thread on that hardware hit 100 percent CPU utilization. Flash has since been sitting around, mostly frozen, for months.

This week, Ryan and I were able to get the new production version of PopOS 24.04 installed on Flash. This cleared up the 100 percent CPU bug that I'd found with that Alpha version. So that machine can now be used just like any server. But, there have still been screen related issues.

Ryan tested PopOS 24.04 on an old laptop. It took some special configuration settings to handle an old GPU. So we may be able to update our regular laptops here soon.

Flash started working correctly on screen with the same configuration settings, but it still has a problem which we think is related to a very old 4K monitor on what is now a very old GPU.

Our next step is to test this with a modern but less demanding 1080p monitor. I found a cheap monitor on Amazon, which came in Thursday this week. That new monitor still needs the correct plugs to draw power from the computer. So another order from Amazon will fix that over the weekend.

If this monitor does not fix this problem, we can still swap out the GPU. We have a more modern spare in the shop. We will see. In any case, Flash can now be used as a 40 core dedicated server, which is all we really need from that machine right now.

Getting this working is important for many reasons. We are not far from being able to run manuscript wide audits against our base Paleo texts. The new Paleo Bible app has 92 books that need to be run through audit related code. This code will check audit against every possible combination of words from the sequence of words in every verse across the entire set of available texts. If Flash cannot handle the work, there are another 48 CPU threads also available on the new desktop that I currently use in the shop. This should be enough. We can be patient.

Ethiopian Bible

Last week I shared about how Ryan added a printed copy of the Samaritan Pentateuch to his collection of printed Bibles. That Bible is the shortest canon and only covers the first 5 books in standard Bibles.

Based on feedback from a reader of the blog, Ryan has also added a printed edition of the Ethiopian Bible to his collection.

The Ethiopian Bible is the longest Christian version of the Bible, with 88 books in their standard canon. Ethiopia is probably the location of one of the Ishmael family of lost tribes. They may be carrying a witness to something that matters.

In particular, we are now watching for historical witness to ciphered texts. Ciphered texts may not have been lost to history. Let me explain this in a little more detail.

Joshua's Robe

The link here is to John 19:23 in the BRB. This is the point where the soldiers divide up Joshua's clothing, then cast lots over his robe.

The Robe itself may match Joseph's Robe, but it may also be symbolic for the base text and/or additional volumes. A clue that supports this contention is how those soldiers divided the rest of his clothing into 4 parts. References to 4, or lists of 4, are usually a marker for 4 layers of additional volumes found through ciphers.

This story can thus be taken as a parable. The main document, his robe, was taken by a lot. (It would end up in Rome, so to a Roman soldier.) The other 4 piles of clothing are also going to be divided. So the additional volumes are divided among the soldiers. This is probably symbolic of the lost tribes. So these volumes may have survived in history, but lost in the "houses" of the soldiers.

Let me suggest that once we do start recreating the ciphered documents, those recovered documents will generally match edited versions of those same texts that are lost out in the world. This story in John 19 is basically telling us that this must be so.

Some of those lost ciphered documents may have reached places like central Africa where they show up in modern libraries, like the otherwise strange books that make up the Ethiopian Bible.

By the way, there are also quite a few ancient books that float around loose in history OUTSIDE of standard canonical bibles. Ryan also has an extensive collection of reference works that carry English translations of many of those other known ancient writings. He reviewed those with me this week in order to help me understand what might be coming out of the ciphers.

We are trying to become generally familiar with these longer canons and known historical books so we are better equipped to see if ciphered documents were not actually lost to history, but hidden away in obscure and distant places.

Ciphered documents may also show up in some of the writings known to other Abraham based faiths. Iran, for example, may be carrying parts of this.

Public Attention On Religion

The war with Iran is causing widespread conversation about scriptural matters. There have even been comments in Podcast circles about how Hegseth and other administration officials are describing the war in Iran with Biblical references. (Even if they cannot quote the text very well.)

I have also seen this in various church circles, which I do not actually track very much, so this is a strange time. It is causing a great deal of stress and emotion in many places. Headlines are being interpreted through the lens of various families of textual interpretation. Of course the public texts have been edited, so these frames of reference are not all that useful.

Even Tucker has been trying to look at this Iran war through a Biblical lens. He is not particularly prepared for the task. He thinks conventional Christianity can explain what is going on. Tucker does not understand how Christianity is itself an edited step child of Zionism and that the texts of Christianity are unfit for his purpose.

Iran War In Revelation

In previous blogs on this Iran war, I have been making references into Revelation. The 5 month references in Revelation 9 are important in that they tie to Noah, either now or in 2029. Those references indicate that deep pits are how Iran seems to have found a way to defend itself against most Zionist attacks. If Iran can maintain political and military integrity, they can win, as the text suggests they eventually will. Though note that the first round of attacks as described in Revelation 9 tells us they will not fully defeat Israel.

Of course Iran will be attacked internally, politically. This appears the only way Iran can be defeated. There were several references here recently to Iran executing Zionist spies, this is an example of their internal problems. Trump also appears to have extended the cease fire in order to give Mossad and the CIA time to conduct a coup inside Iran.

In thinking about these many media references to Armageddon and Revelation I began thinking about the book of Revelation itself. I generally don't like going into that book because it exhibits several layers of editing. I just keep telling myself the audit is coming, keep working, and solve this problem once and for all once the audit is done. Flash will be given this problem as soon as the new audit code is known to be working correctly.

In previous blogs I have also surveyed Revelation and suggested that there are interpretive links that basically back up across the historical text, back to Eden, and then work forward. This is an internal system for finding matched stories, which is a first pass at understanding Revelation. That study is a text-against-text system for understanding the book.

I don't really want to go deep across the entire book until that audit work is done. But, I could also not stop thinking about certain structural features of the book which I have never noticed before. There appears to be a text-against-time study, which is what I am seeing now.

Let me lay out a possible solution to the biggest riddle in that book. It seems to indicate that Revelation has a primary application in a very narrow time in human history. Revelation may uniquely apply to the time we are living through right now.

Riddle Of Revelation

The link given here is to what is our current guess at the likely inspired start, at Revelation 1:9.

This likely inspired start of Revelation begins with John telling us that he was "in the spirit" on the "first day of the Sabbath." This introduction makes sense if he is on the first day of the 7th month holiday, the holiday of Tabernacles, also known as a Sabbath.

Greek based translations are a little different in the wording. In that case, John is understood as simply writing on the first day of a normal week.

Why would this introduction matter? Why does the reader need to know this timing?

I am learning to watch for tricks in the text where innocent introductions are really hidden interpretive keys that readers must not ignore. In the Zacchaeus story, Joshua is headed to Jerusalem. This is early in the overall parable, but telling us the punch line at the end is about the city of Jerusalem.

Revelation looks to work the same way. It looks like an unimportant step to open the book. But, the 1st day of the week has 1 powerful application at 1 specific prophetic time in all of world history.

The most important "1st day of the week" is Resurrection Sunday.

This is the day at the end of Joshua's time in the tomb. It follows Passion Week. This is the day when Joshua has gained the right to rule because he had been killed and had come back to life.

In recent blogs I have been explaining how that special day folds out to a 30 year interval that ends at the end of 13020, so about 1 year into a Noah's Flood replay that begins in February of 2029.

So John's introduction looks like the main interpretive key for understanding what follows in the Book of Revelation. But it has a narrow application in historical time. To understand this key we need to understand Resurrection Sunday itself.

Resurrection Sunday

The link here is to Luke 24 in the BRB. This is the last chapter of Luke. It contains the historical stories for Resurrection Sunday.

Resurrection Sunday begins when the women go to the tomb early in the morning. Perhaps just before the light of dawn. The calendar day itself is now about half over. There are about 12 hours still remaining in the 24 hour calendar day. The tail end of the account appears to drift beyond the end of that calendar day, into the following evening.

Placing in Prophetic History

This calendar day was the first day in the week AFTER Passion Week. It is the last day with day-accurate details from the week. So it is a natural tail on the events of Passion Week itself. Indeed, if we read through the account we see Joshua demanding a recounting of the events of that week.

This day is part of Joshua's ministry year, which was running at 30 historical years to the calendar day in his ministry. This particular calendar day aligns with 30 calendar years, the last of which is 13020.

Because this Luke account is starting at near sunrise, as prophecy for our modern time it is only interested in the 15 or so years that end on 13020. So roughly 13005 through 13020. (13005 is before day break.)

The main event at the tail end of this interval is Noah's flood. That is roughly starting in February of 2029. Very, very roughly, back up from February of 2029 by 15 years and find the start of this prophetic interval. This would be early in 2014.

If we go looking around 15 years before Noah we run into the Maidan Coup. This is when the European Zionists took over Ukraine as a first step to conquering Russia. They could then use Ukrainians as cannon fodder against Russia. That war continues now in Ukraine. This event is known on Zionist Wikipedia as the Revolution of Dignity. Here is the link for reference.

Revolution of Dignity

The newly elected leader in Ukraine rejected unity with the Zionist European Union and instead sought better relations with Russia. He had a mandate from his electorate for this work. The Zionists would have nothing to do with it and started a short civil war, known as the Maidan Coup.

The Zionists took over Ukraine by force. They started the war we know now in Ukraine. The Russians would quickly take back Crimea and eventually start a ground war to defend Russians trapped inside eastern Ukraine.

History will likely record that coup as the start of World War III. The Russians already count this as the start. In patience they are not fighting all that fast because they know this ends with a nuclear war. Most of Europe will cease to exist. Russian leadership is hoping something stops the European Zionists, like running out of fuel. (Russia cut oil delivered through Russia to Germany this week to help speed the end of the German war making industry. Iran is helping with this too.)

Luke Notes

Curiously, the name "Maidan" is playing to the "maidens" who went to the tomb early on Resurrection Morning. They knew something strange was happening, but they did not know where Joshua was to be found.

The women found the stone rolled away and an empty tomb. They did not find Joshua. Ukraine is mostly a unique dialect of Nazism. Kiev is no longer a city of Orthodox faith.

But important to note, Kiev has a famous system of caves. These match that empty tomb. One of the most important Orthodox monasteries is named for, and located above, those caves.

Kiev Pecharsk Lavra

This place was founded in 1051, so about 60 years from the arrival of Christianity in Russia. There are 2 cave systems below ground. They hold the remains of many famous monks from Eastern Orthodox Christianity.

That we would hit a headline at the tombs of saints is a major and important detail that helps affirm we are starting correctly. The Maidan Coup is resurrection morning.

The maidens, of course, found the tomb empty. The tomb could not hold him. In their shock, the women encounter 2 men who stood above them. Those men ask the women, Why do you seek the living among the dead? He is not here. He is risen.

One of the details from the 2014 coup was the sharp shooters on the roofs of government buildings. Those shooters were thought by many to be Zionists. So the women looking up is matched by the need to watch the roofs in Ukraine at this same time.

By now, so 2026, Ukraine has lost a huge number of men fighting against Russia. It is not a land of the living, but of the dead. It will be worse when the missiles, clothed in white, start to fly.

There are more riddles in that Luke 24 chapter. We must leave those for a future study.

Revelation Notes

So if we go back to Revelation, by Revelation 1:19 we find references to resurrection morning, a match to Luke 24. This is another internal clue that Revelation is written against Resurrection Sunday.

By Revelation 4:1 we find John is called up in order to be shown more things. This is like the 2 men in white who were above the women. Again, another match to Luke 24 and another match that indicates we are on the right path to solving the Revelation riddle.

Beware Time

There are many, many other riddles down through Revelation. An example would be Revelation 7, with the seal date list. We know those as history. They identify the tribes. See BibleTribes.org.

But there are complex ratios available to fit a tight 15 chronology for a possible complete application of the entire book. 12,000 days, for example, can go through the 2 Peter 3:8 ratio of 1000 to 1, so 12,000 become 12. Then we can go back through the 30 to 1 used for Resurrection Sunday itself. So the 144,000 can be 12 common years. So something like 2014 jumps to 2026. The lost tribes, all those on Jacob's side, are fighting against each other in Ukraine for 12 years. Status in the Ukraine war may be expected to change this year.

Wait For Audit

I want an audit before going into great formal detail on Revelation, but the general feeling across the culture that we seem to be on the cusp of something like Armageddon may not be all wrong. We may actually be living it out now, and it is starting to be felt by many across the world. More on this family of riddles in future blogs.

Match Dates

This past week we were looking for the end of 40 days of rain of Noah. The 40 day Iran war appears as the best match so far, though it was started and stopped 2 weeks early. The 2 weeks of cease fire at the end explains the offset.

We are still watching for a restart to the war, which would trigger stories from Revelation. As of the date of this blog, that restart does not appear to have happened. If this holds, then the 5 month references from Revelation 9 remain for a future time.

We are in a nervous pause, and there have been nearly daily attacks on shipping, which might become an otherwise mostly hidden fulfillment of a longer interval. This needs more time to decide what is going on.

Trump, or at least the Zionists, did blockade the entrance to the Strait of Hormuz. On the expected 40 day mark, at 2026-04-19, under their blockade, the Zionists did capture an Iranian cargo ship. This was a particularly strange episode, it took more than 6 hours. This long time span suggests nobody knew what to do.

Helmer With Nema on Touska

The link here is to the Youtube video of Helmer's weekly chat with Nima on Dialog Works. Helmer goes into the strange timing and explains what this says about decision makers in Washington DC. They apparently were deciding what to do back in DC across those 6 hours. Maybe nobody important could answer the phone in Israel?

Watch Dates

This blog goes out on 2026-04-24, the replay of the last year of Asa's reign. The following day, Saturday, 2026-04-25, is the replay of the start of Jehoshaphat's reign.

There is a planned meeting with the Iranian Foreign Minister in Pakistan on the 25th, but not with Americans. He is also scheduled to travel to other places, including Oman and Russia. This is not a negotiating delegation, so I would not expect much to change. But, we will see.

By early on the 24th, there have also been a series of warnings issued by perhaps 15 countries asking their citizens to leave Iran, suggesting the world knows the Zionists are about to start bombing Iran again. We will know better across the weekend how this plays out.

Headline Review

The following caught my attention this week.

More On Iran Rains

The link here is to yet another link highlighting the change in weather in Iran, apparently because weather modification radars were taken out in the war.

First Post on Vessels

First Photos

Top link was the first post I saw about Iran shooting at Indian vessels on April 18, 2026. This was US time, near the start of the 19th in Iran. 2nd link is photos. This preceded the USA boarding the Touska. This sort of small arms fire might be filling in across an otherwise apparent gap in the 5 month reference in Revelation. We cannot know for sure what might be going on prophetically for another few weeks. But this does land on the charted end of the 40 days of rain for Noah.

Touska

Pic

More

These links are the first posts on the Zionist attack on the Touska. Then pics. This was a container cargo ship sailing from China to Iran. Debate centers on what was on the ship. Either normal Chinese civilian cargo, or else rocket fuel. Take you pick, we are in the fog of war.

Here the blockade by the Zionists is starting to take hold. Oil through Hormuz effectively ends at this point. The link above with Helmer on Dialog Works is the best for understanding this event.

President of Argentina in Israel

This link is one of many that have been detailing the visit of Argentina's president visiting Israel. He has stated several times here recently that it is better to be alive and slave to Pharaoh than dead.

His position is why Pharaoh continues to rule. This is the opposite of Iran. Iran does not fear death. Iran can win, so they can end up alive and free from Pharaoh. Iran, of course, has dug deep caves, which helps.

Dead Scientists

There have been numerous reports recently of dead scientists, most working on alternative energy and related fields. These sorts of deaths come in waves. Every decade or so, the experts in these fields end up dead or missing. The link here is a little obtuse to the main point, but is interesting in how the government appears to be ill equipped for much of this study. It is a long form article on unz.com reviewing a recent video.

Biblical War

This is just another reference link on how US officials are describing the war in Iran as Biblical. If those officials knew the real story they would not be endorsing this war. Do they think Washington DC or Jerusalem will survive? Why do they think they have Joshua's favor in this war? They haven't read the book carefully enough.

Old Aramaic Prayer

This link is to an Aramaic Wire post on X. This details their oldest known prayer thought to have come in the first century. Building reasons to believe this is an old practice. They kept the edited text, not the inspired text. But still interesting to track this ancient branch of Christianity.

City Of London Pic

The City of London is inside the City of London. Got it? If you don't know the verbal game played by this Zionist headquarters, then this link will help. It shows a photo of the bigger city and then outlines the Levitical city within. This is similar to Washington DC, which was probably patterned after this City of London in terms of sovereignty.

First Warning: Leave Iran

This is the first of the warnings that I saw about leaving Iran. In this case on April 22, 2026, asking Americans to leave. This would become about 15 nations warning the same by the 24th.

Nimitz On Site

The link here details the arrival of the USS Nimitz to the Indian Ocean on April 23, 2026. This ship is thought to be needed for more Zionist attacks on Iran. It replaces the USS Ford. It had to travel around Africa. This would explain the Zionist side's need for delaying the end of the cease fire. It is a prize target should shooting resume.

Litani River Border

The link here is to a post on Telegram by Pepe Escobar. It shows the area taken by Israel from south Lebanon. The border is now set at the Litani river. Unspoken in most media circles is how this border change also changes rights to off shore gas fields, so this is a financial play in addition to territory.

More Later,

Phil