Paleo.In

Phil Stone holds a Bachelors degree in Computer Science and a Masters degree in Business Administration. I was saved, in the normal Protestant sense, when I was in college. From that point, I was always interested in the Bible.

After college, I worked a series of jobs in the computer industry that would foreshadow current work. My first job was writing software for test equipment used to certify product rolling off a high tech manufacturing line. I am still writing certification software, this time to certify the inspired core of the Bible.

Before the Internet was a thing, I was involved in the early work to create Graphical User Interfaces for Personal Computers. Today, those same skills apply to Web Apps, which is my normal platform for writing apps.

I was involved in the first major 3d design project using computers for designing airplanes. For the companies involved, this was a massive business risk. The project used very new, very rare and very expensive hardware. But, it turns out, this was about the first place in the world where anyone could learn the practical problems encountered when using computers for the 3d design of huge, integrated, sets of mechanical objects. I now use 3d design software for designing modern, plastic, versions of the exhibits described throughout the Bible.

My final tech industry job looked at the use of Open Source software in commercial applications. This work especially looked at the design, legal problems, and an important first corporate use of Linux. This work also involved the problem of "evil twins." These happen with some open source projects. Most of our current work will eventually become open sourced. Provided, of course, we don't inadvertently create an evil twin.

Before leaving the corporate world for current work, I was an elder in a Presbyterian church. I had read the Bible through about 19 times. I was starting the work that became the Bible Time and Bible Tribes projects. Those are discussed below.

I set out to follow Jesus, now called Joshua, for what I thought would be a 5 month project. I am still at it, approaching 30 years later.

Ryan Eaton holds a Bachelors degree in Biblical Studies. Adults who knew him when he was young, expected him to become a Pastor or at least someone in full time ministry. From his very youngest days he was always interested in the Bible.

After graduating college, Ryan worked in a low security facility for adjudicated youth. He later worked as a resident counselor in a private residential High School. This was a place where the rich and sometimes famous sent their troubled children for an education. Both of these jobs reflected his pastoral gifting.

Before leaving Ryan's last job, he turned his attention to problems with the Bible. His first major study looked at how it might be possible to use the Bible itself to determine the inspired order of the books of the Bible. This was the first use of our current work principle. Use the Bible to fix the Bible. His hypothesis was that the 66 chapters of Isaiah might inform the order of the 66 books of Protestant Bibles.

That work was called the Book Order Bible. Copies of those Bibles were for sale for a time. In 2006, with the bankruptcy of his employer, Ryan began full time work on Bible related topics. Ever since that time, he has remained working on a series of successively more difficult Bible related problems.

Ryan's Book Order Bible work still remains. Ultimately it became the Bible Research Bible, the BRB, described in detail below. Isaiah does inform ancient book order, but not using modern chapter breaks. The BRB was returned to the standard Protestant book order to allow readers to focus on the many more important problems with the text of the Bible.

The Testimony (TT) - web app
The Bible is named after "Babel." This from the Tower of Babel, where men make a reputation for themselves. The Bible is also named after Nebuchadnezzar's Babel. In both cases, the name represents confused speech. (Bible came to mean "book" much later in time.)

The Bible was built in order to support the state religions of various kings and empires down through history. The Bible also carries within itself an inspired core. That inspired core is known as "The Testimony." Thus the name for this app.

Using just the tools of a Bible study, it is mostly possible to identify which parts of the Bible are inspired. This is the most important and fundamental of all Bible studies. This is also the hardest of all possible Bible studies because it grinds against lessons taught in church. Some church topics, traditions, and practices, are not, ultimately, inspired. Getting through that lesson is hard. This is why our work has taken so long.

Our own work on this particular problem began in earnest in early 2016 when we learned the identities and agendas of the 6 villainous editors. By the middle of 2016, this app was first online. This is when we started to select out the subset of the Bible that we had reason to think is inspired.

Our current work is to verify this English language draft of The Testimony by running a letter level audit against ancient manuscripts. This is why we say "Digitally remastering the Bible."

This English language app will be updated to exactly match the results of the audit as current work progresses. More on the audit below.

This app is updated weekly, usually Friday afternoon.

Story Grid (SG) - web app
The Testimony manuscript has serious internal structure which is unfamiliar and unknown to anyone only familiar with the Bible. This mostly hidden structure functions through rigorous story pairing.

That inspired internal structure ultimately eliminates the need for resource works like Study Bibles. We expect once this work is finished, that young learners will eventually memorize the pairing system as presented in this Story Grid app. Both Ryan and I would have memorized such a grid, if it were available, when we were young.

That internal story pairing structure is intimately tied to the Paleo Alphabet. That alphabet is also unfamiliar to most people. So using this app effectively, also requires learning the Paleo Alphabet.

This Story Grid app is also currently one of the main tools being used to "wrinkle out" some of the more difficult story breaks and story placements still not settled in our draft copy of The Testimony. So beware, this app is unfinished. It shows off the promise of what inspiration looks like.

Each tile in the grid in this app can be tapped to show the common, related, story pairs. This is a draft. The current, and likely correct, grid size and shape was finally determined late in 2025. Content for each grid location is still being worked.

This app is updated most Fridays.

Sabbath Reads (SR) - web app
The text of The Testimony is short enough for most people to be able to finish a complete read once each calendar year. It becomes a weekly goal to read another section.

The columns in the Story Grid app provide the starting point for Sabbath Reads. Every other Story Grid square, reading down, becomes the next story in this Sabbath Reads app.

The calendar app, linked below, indicates which section should be read each week in order to avoid most holidays and finish a complete read once each calendar year.

This app is updated weekly.

Qu Map (QM) - web app
The inspired alphabet has 25 symbols. This includes 22 letters and 3 punctuations. Each symbol has a related 3d model which is itself a model of something. Those models are easily recognizable objects from the daily, physical, world. Those models define the meaning of the letters. So the meaning of inspired words is also loosely defined by the spelling of each word.

Those 25 symbols thus have 25 defining objects. They want to be displayed, say on a table. Because the prime factors of 25 are 5 and 5, this suggests these symbols should be arranged on a 5 by 5 grid. In the end, a 5 by 5 grid is the natural canvas on which to arrange all of those 25 symbols.

We call this 5 by 5 canvas the "Qu Map." This is named after the Paleo Alphabet letter Qu. That letter is strategically placed on that same map.

Each of the 25 symbols becomes something like a tree planted in an orchard. Each tree yields fruit, so lessons, in season.

What we found, after playing around with this map, is that there are places in the physical world which are supernaturally designed to follow that same map. So we built this Qu Map app to show off what we found.

For most of our English Language users, the USA Qu Map is the most important to understand. The USA map also forms a natural American Pilgrimage for those who would want to visit each location. Most Americans have already visited at least a few locations on the overall USA version of the map. We have ourselves visited all the locations except those in Alaska and Hawaii.

This app gets updated most weeks because it contains some scripture references.

Paleo Clock (CLK) - web app
Modern clocks were developed for use by early astronomers. This was centuries before even mechanical calculators. To reduce their manual, pencil, calculations, they relabeled the faces of their clocks. This relabeling moved from historical "Hours of the Day" (O'Day) to their then newfangled and specialized "Hours of the Clock." (O'Clock)

In order to avoid a complete round of manual calculations, astronomers needed their clocks to be accurate for at least 24 whole hours. Clock makers fought to make the most accurate clocks for use by astronomers. So the best and most accurate clocks were labeled with "O'Clock" times, not "O'Day" times.

Eventually, the British Navy and businesses with hourly employees starting using the same accurate clocks designed and labeled for astronomers. With that, the convention of counting "hours of the day" was replaced with "hours of the clock."

Of course scripture still uses "hours of the day." The British Navy was the first to formally set midnight as the calendar day break. Scripture uses sunset. These various differences in the time keeping system cannot be easily calculated using modern clocks. Not only are modern clocks mis-labeled in terms of hours, but modern clocks also use Real Numbers with an implicit hour 0.

Hours of the day use Counting Numbers. Counting Numbers start from 1. Counting Numbers are still used for labeling days of the month. Before astronomers, time keeping used the same number system as calendar keeping.

This Clock App provides several different analog clock faces. The hour and minute hands are located conventionally. But, those clock faces are labeled to correctly show "hours-of-the-day."

This tricky set of lessons must be carefully learned and mastered before any hour accurate references to time in the text can be understood. This is especially so for most timed events in Passion Week.

Mechanical versions of some of these clocks will be available in our 3d design files for the exhibits.

This app has been in our stable of apps for a long time. It gets updated irregularly. Typically, updates are because of changes to styling or notes.

Paleo Calendar (CAL) - web app
The story of the prophet Samuel documents a time when the people asked for a king. The people wanted to be like all the other nations around. They wanted an earthly king to fight their battles. They had forgotten who had parted the Jordan and brought them into the land.

With their request for a king, the covenant established at the Jordan river crossing became effectively broken. The tribes of Jacob would eventually loose their land and be returned to the nations from which they came.

One sign of the broken covenant was a change in the calendar. With the loss of the calendar came a loss of the holidays. There was a loss in knowing the times. There was a loss in knowing the timeline of history. There was a loss in predicting the future.

Breaking the covenant by asking for a king caused an outworking of that breakage that showed up in their national calendars.

The southern kingdom was given over to a lunar calendar, with about 29.5 days per month. The northern kingdom was given over to a solar calendar, with about 30.5 days per month. The modern Jewish calendar is effectively the southern kingdom's calendar. The modern Gregorian calendar is effectively the northern kingdom's calendar. Though beware, the northern kingdom had a complex history reaching the current Gregorian calendar.

It has always been possible to prove from the text that the inspired calendar has month lengths of exactly 30 days. This can be done using the story of Noah. It can be done using Revelation.

Since about 1948, it has been possible to accurately recreate the entire calendar and connect it, day accurately, to the modern Gregorian calendar.

The link here is to an app built to use and show that inspired, 30 day per month "Paleo" calendar. It also counts months and years correctly, with the start of the calendar at the first day of the first month of the first year of Adam.

The full calendar derivation, along with all cites, is given in the Bible Time website, links to that follow below.

This app has various optional Settings that can display useful values inside each calendar square. Check the Settings menu for those.

This app is updated irregularly. Typically because of a change in styling or notes.

Bible Research Bible (BRB) - web app
This app is our primary English Bible. Ryan has maintained this Bible since about 2006. It was originally called the "Book Order Bible." This early name was used because the historical order of the Bible's books are disputable. Once we found more serious issues, we switched back to a more conventional Protestant book order.

This English text is heavily annotated. There are very many Bible Studies that cannot be properly addressed without a certain level of markup in the text itself. As we have progressed through a series of such studies, the text in this Bible has been updated with new systems of markup in order to make those studies easier and faster for us to carry out.

Particularly important markup includes fully colorized text. Color is used to identify who is speaking. This eliminates the need for most quote related punctuation. This makes the text much easier to follow.

Red Letter Bibles are a precursor to full colorization. Though theoretically possible, the first printer of Red Letter Bibles was told not to colorize the divine voice in the Old Testament because divine voice is assigned in contradictory ways by various faith communities. In our BRB we have gone ahead and colorized the entire thing.

Our BRB Markup also covers specialized types of keywords, like names of people and places, digits, time references, currency, and types of animals and plants. This makes topical studies around these types of words easier and faster to carry out.

There is also an extensive series of quote cross references. This allows quick study of each end of internal quotes as found in the text. Surprising to many readers, New Testament quotes are often taken out of context. Also surprising, some quotes have no known source.

There is also a set of markup to indicate "Filters." This markup indicates text likely added by any of the 6 villainous editors. This includes text thought to have been added by any of Solomon, Ahab/Jezebel, Nebuchadnezzar, Mordecai, Ezra and Ananias.

There are a few other categories of markup that some users may also find interesting. Most specialized markup is not visible by default. Explore the settings menu to learn all of the markup features.

The English in this Bible is generally checked against the Aramaic texts. This is especially so in the New Testament as our use of the Aramaic New Testament goes back to the start of this manuscript work in 2006. Our use of the Aramaic Old Testament began later, so the Old Testament is somewhat less strict against the Aramaic Old Testament.

This app's BRB text is the starting point for the text in The Testimony app linked above. Everything here marked under a "Filter" tag is thought to have been added by one of the 6 editors. That material is not found in The Testimony. Read the extensive included notes for more details on these points.

This app is updated weekly. Typically, on Friday afternoons.

Bible Reader (BR) - web app
This app provides a selection of other Bible texts. These are presented in an approximation of their traditional printed form.

Most American Christians do not understand the variety of Bibles used across the Christian world. This app provides at least a selection intended to highlight that diversity.

Instructors introducing students to the problem of general Bible history may find this app helpful.

This app is updated irregularly. Typically because of updates to styling or notes.

Bible Harmony (BH) - web app
The Bible as passed to us by history contains many duplicate passages. For example, the material in Kings is also found in Chronicles. For another example, much of the material in the Gospels is found in the other Gospels.

In the end, we expect most of this type of duplication to go away. Only 1 version of most stories are likely to survive audit.

This Bible Harmony app starts with our BRB text. For subjects in passages that are duplicated, this app presents those passages in parallel form. This format allows the reader to study the differences between otherwise parallel passages.

This type of presentation is normally called a "Harmony" thus the name of this app.

This is another advanced tool that instructors may find useful for introducing students to the problems of the Bible as passed by history. Particularly important to this study is as an introduction to the problem of contradictions. In very many places, parallel versions of stories are presenting conflicting accounts. In conflicting accounts, both versions cannot both be true at the same time. This is NOT an expected feature of inspired text. This is in part why the Bible we know now is not fully inspired.

This app is updated most weeks because it is based on the BRB text which is also updated weekly.

Verse Reader (VR) - web app
Our audit and recovery work is ultimately carried out at the level of the letters of the text as passed by history. The best way to study this level of the problem is by looking at different versions of the Bible's text where verses are displayed side-by-side. That side-by-side display of verses is the purpose of our Verse Reader app.

This app is mostly for our own purposes in studying word level spelling of various manuscripts. Instructors introducing students to the nature of the Bible texts as passed by history may find this app useful.

This app is updated irregularly.

Bible Time (BT) - website
This website explains how time works in the Bible. The website is broken down into sections that are themselves long Bible studies that lay out an extensive theory on how time works in the Bible.

Key ideas include how counting works in the Bible, especially 1 based counting. It explains the structure of the calendar. It explains how genealogies are used to short-hand very long runs of human history. Most, but not all, genealogies run together end-to-end.

It then goes carefully through the Chronology of the text and counts off years from Adam. This series of dates runs through the Babylonian Deportation. It then deals with calendar issues related to the "Jewish return" that began in 1948 but then reached the Old City of Jerusalem in 1967.

It explores certain riddles that allow reconnecting the modern calendar to the day-accurate calendar that has been running all along since Adam.

There is also an extensive section dealing with the New Testament. The exact Julian Calendar dates for Joshua's (so Jesus') life are knowable. This site explains the math. That life was also a day-for-a-year replay of the historical timeline from Adam. So he personally embodies the entire timeline of scripture. Within his life there were also timelines that replay in history. Some go beyond events in the first century. Those provide the basis for modern prophetic timelines. This is especially so for the timing of World War II (and III).

This ultimately means that historical time is both fractal and repeating in various ways at various times and at various rates across all of human history.

This website contains a Passion Week harmony that we would now consider to be poorly presented. There is a planned 3d exhibit that will clean up and expand on Passion Week. That exhibit will display detailed predictive aspects of that timeline.

This website also includes some interactive time related tools that are occasionally used and referenced in the Blog.

This website is updated irregularly.

Bible Tribes (BTR) - website
The Bible Tribes website originally began as a tab on the Bible Time website. The material in Bible Tribes grew large enough that it deserved its own website.

This website introduces the concept of a "Seal Date." These are times when some nation used wax and a seal on some sort of national document. Those dates and documents identify lost tribes as listed in Revelation 7. Find the dates, find the documents, and the tribes can be found.

Once found, the various ancient promises given by Jacob over his sons and grandsons then match various characteristics of those now identified modern nations.

To do all of this, the Bible Tribes website carefully tracks the promises given to Abraham and his various heirs. Those promises spread out across the various family lines and no longer live in any specific singular people group. This is important because there are some people today who think their tribe is unique. Any such belief, anywhere in the world, is shown false by this study. The redemptive plan reaches all nations.

The bulk of the website is broken down into tribe specific tabs. Those tabs are organized in the Revelation 7 order. They provide the seal dates and related documents that identify the tribe. Those tabs also then include articles that softly identify the tribe by signs.

In doing this work we found that most of the identified countries have sub-cultures that know their ancient tribal identity. This is done by signs, not by dates.

Each tribe related tab also includes a map of that nation's colonies. By this, most of the world has been reached by Abraham's heirs. A few nations, say those in West Asia, will fall under Ishmael, which has a parallel set of promises not covered in Bible Tribes.

English readers here should pay particular attention to the Manasseh and Joseph tabs.

Note this study is a precursor to the problem of recovering vocalization for the Paleo Alphabet. There is an exhibit, a wall hanging, that summarizes this study and provides a map to the Paleo Alphabet for the purposes of finding correct letter vocalization.

Bible Tribes was an important and early precursor study to what was, at the time of discovery, future Paleo language work.

Ezekiel's Bones (EB) - website
The prophet Ezekiel had a vision of a valley of dry bones. The reference to "bones" is a reference to the silver set of 3d models. These models assemble like a kit into the form of a human skeleton. There are both male and female forms. The male is a sower. The female is a reaper. They ride on chariots configured for their specific field work.

We are using this as the general name for the complete set of exhibits. The majority of the exhibits are intended for setup and display in a main gathering room. A few of the exhibits are intended for a more private room. Either an "inner room" or an "upper room" depending on the type of building and floor plan.

Originally, these various exhibits would have been kept in Moses' tabernacle. These exhibits are also what Joshua himself built at his house in Capernaum.

There are other references that suggest everyone should have a copy. This is what it means to sit under your own "vine and fig tree." This idea is calling out the promise using the names of certain of the exhibits. At least any private house which hosts a fellowship should have a complete copy of all exhibits.

There is a very long list of items in this set. The Ezekiel's Bones website linked above has a detailed list along with photos of a few exhibits that have already been fabricated.

We are following an iterative design process. All exhibits must be 3d printed a few times before we know we are finished with this work. Proven designs will be published on that website once we are happy with the work.

This website is updated irregularly. It will get more frequent updates once we are done with design work and we consider the designs as finished.

Paleo Bible (PB) - web app

The Paleo Bible begins by taking an Aramaic copy of the entire Bible. Each letter is transformed into the Paleo Alphabet. This starts with all of the conventional books found in Protestant Bibles. It also includes a wide selection of Apocryphal Books. Especially interesting to us is the Book of Tobit, which we expect to be mostly inspired.

The app uses the same basic tooling as used in our other Bible related apps, especially the BRB. It is generally capable of the same detailed markup as found in the BRB. The menus, navigation, and settings are generally the same. The full markup found in the BRB is theoretically possible to be added to this Paleo Bible. None of that markup has currently been completed.

We don't expect all of the books passed by history to pass the audit. So we don't expect the historical canon to be correct. We do expect books that fail audit will become a type of process control on the overall audit and recovery process.

For books with some inspired content, we generally don't expect every verse to pass audit. In all cases, there is the risk of detailed issues of recovery, say correcting divine names.

The Paleo Bible app is built as an interlinear. So every Paleo word has an English word assigned. Exhaustive lexicon related data will be part of this app.

There is a huge amount of work still ahead. We are doing this work on a public facing app because we have quite a few friends who are closely following this work. Details on issues with this work are covered in the blog.

Once enough passages in this Bible start to pass audit, those passages will form the nucleus of a future "Paleo Testimony" app.

This app is currently updated irregularly.

Paleo Blog RSS Feed
This requires the use of an RSS Feed Reader. This is the best, and most private, way to follow what is often a controversial blog.

Paleo Blog Via Email
We send copies of the Blog out via email. You can use the sign up form linked here to get your email on the list. Of course you can unsubscribe at any time. We do not share this list with anyone. It is generally better to use an RSS reader to follow the blog, not email, if you can.

Paleo.In Group on Telegram
Links to new blog posts are shared in this PaleoIn group on Telegram. These links go up at the same time as the blog goes out on Friday afternoon. We also use this Telegram channel for weekly photos of current shop work. You can also ask questions and interact publicly with us there. As long as you are signed up with Telegram, you should be able to follow without expressly joining this group.

Future Work

Recovery of the inspired Testimony from within the pages of historical manuscripts is not the end of the work.

There are many places within the text of the Bible that hint at additional volumes. These are generated through a cipher system. The inbound text for that cipher system is the inspired manuscript of the Testimony itself that comes out of the audit.

The output of the ciphers looks to be additional inspired writing.

Cipher related future work is only theoretical until more of our current projects reach completion.