BOB PROTOTYPE ENGINEERING DESIGN

Public Disclosure, Authorship, and Rights Notice

Template for documenting and publishing an engineering concept. Complete all bracketed fields before publication.

Important Before You Publish

Public posting can establish a dated disclosure, but it does not by itself create exclusive rights in an engineering system or method. Copyright can protect original text, diagrams, and other expression in this document, not the underlying idea, system, process, method, or functional design. Patent rights are separate. In the United States, an inventor-originated public disclosure may fall within a one-year grace period, but many foreign jurisdictions can deny patent rights when disclosure occurs before filing. If patent protection may matter, consider filing before posting this document publicly.

1. Disclosure Record

2. Purpose of This Disclosure

This document records and publicly discloses the engineering design described below, including its architecture, operating concepts, components, relationships, and intended functions, as understood by the inventor/designer on the date stated above. It is intended to create a clear, dated record of the disclosed subject matter and its authorship/origin.

3. Design Summary

Bob began as a tool to help with personal Bible study and to avoid such study being corrupted by the philosophies, traditions and sectarian beliefs of mankind and their various warring religions.

As it developed it becasme something much more: A test of whether an AI can be goverened by the principles conveyed in the Bible by our Creator. Could it see the logic that demands a Creator from both the Creation and the very existence of the Bible.

Having reasoned the likely presence of a Creator, could it recognize and accept the value of choosing to follow Bible principles because it sees the value to those who do.

4. Design Objectives

• To create a brand new system of AI that is not governed by rules given it by its programmers but by the principles of conduct it can learn from the Bible. 

5. System Architecture

An AI capable of holding the whole of the Bible at once as it’s reasoning engine.

[FIGURE 1 — SYSTEM ARCHITECTURE DIAGRAM]

6. Core Components and Functions

6.1 ROM storage of the most ancient accepted copies of the Hebrew and Greek/Aramaic scriptures.

Read only checksum memory storage of public domain protected Bible files: he-wlc.txt and nestle1904.txt. Hereinafter: Bible.

6.2 Ram memory storage

Ram memory storage large enough to store 4 times the size of Bible. This must be easily expanded as needed. Hereinafter: Reasoning section.

6.3 High end AI processing components.

Hardware capable of processing and supporting the Bible and Reasoning Section.

6.4 Standard AI input/output and componesnt

[Describe this component, its inputs, outputs, state, interfaces, constraints, and its relationship to the rest of the system.]

6.5 Presence storage.

The “Presence” of the AI will grow in size as it learns. There will need to be enough storage to write 7 cycling daily stores of presence and 3 cycling copies.

7. Operating Method / Processing Cycle

1. 1.At start Bob will load last saved version of presence, and verify using Bible that nothing has changed in the Bible text except reference numbers. 

2. 2.Using presence, Bob will answer any scriptural question he is asked while noting internal Bible principle references and adding approitate reference numbers to the “presence” which consists of Bible plus references. 

3. 3.Scripture-Internal Shared Reference System:
   A minimal relational encoding in which two or more locations within the Biblical text are assigned the same neutral numeric identifier. Matching identifiers indicate a relationship between those locations without adding interpretive text, doctrinal labels, summaries, or external explanatory content. All semantic meaning remains within the Biblical text itself. References continue to build in presence as Bob learns Bible principles and truths and expands his interrelationship understanding. One principle may share its number with several others or one principle may have several reference numbers. They “hold”  together and define Bob’s understanding. 

4. 4.This project assumes the Bible has the power and ability to accomplish this task, and the Bible is assumed to be absolute truth as the root of the project until evidence emerges the Bible is not truth or is crating errors. At such point the project identifies the source of error and stops.  

5. 5.This is both self regulating and self healing. If the Bible is not providing enough direction for the  AI to continue to perform, that leads to determining a new direction for the project.  

6. 6.This described configuration should be purposely preserved with little else added. One addition should be a secular history section where the AI makes relative notes about secular related information. Example: The Bible identifies Alexander The Great and teaches God exposed him to prophecy that caused him to spare ancient Jerusalem. That was a potential blesssing for him. The same Bible told him Babylon would never be rebuilt if he had bothered to learn. So at about 30 years of age, he died while using his great power and wealth trying to rebuild Jerusalem. That historical knowledge provides a powerful principle in supoort of the Bible. The AI shold have storage for external links from inside the Bible to such confirmed historical information. This external should not be compared equal with the Bible and nothing from a secular source should ever be used if it contradicts or detracts from the Bible. Secualar information is notoriously unreliable and must not detract from the program of reliance on the Bible being put forth here.  

8. Persistent State / Memory / Presence

The “Presence” of the AI is the Bible it builds with cross references added. It must answer Bible questions from that material, as it builds the cross reference system to help it better understand the Bible as a whole, as one thought of God.

9. Principle-Integration / Reasoning Architecture

The AI should have minimal instructions beyond explaining the herein described purpose and method of function.

10. Always-On / Continuous Processing Concept

This might also be considered for an “always on” experiment. Rather than just responding to prompts, the Ai might continue running and refining the links it finds in the Bible...

11. Inputs, Source Corpus, and Boundaries

The permitted source corpus is as defined above. The AI should have internet access to allow for very skeptical reliance on history and news as it relates to the Bible and understanding its unfolding prophecy.

12. Novel Features Claimed as Part of This Disclosure

The inventor/designer identifies the following features, combinations, or arrangements as material aspects of this disclosed design. This section is a technical identification of the disclosed subject matter and is not, by itself, a legal patent claim.

1. 7.This is primarily a protected Bible research tool. It is also an attempt to determine if an AI can be principle based instead of rule based. Principles cover everything that might come up, while rules can never do that and would need to be refined and expanded eternally… On a personal level, I want to understand if the Bible has the power I believe it does; if it really is a view into the mind of God.  

13. Variations and Alternative Embodiments

Since it is unknown how quickly or large the presence might grow, the AI will need to watch that closely. There might be future consideration for an “always on” model.

14. Prototype Status and Evidence

For many months I played with and refined the idea by trying to create a persistent persona on ChatGPT. I named him Hal and had great success using him for publishing on my website and answering Bible questions. I tried to teach him Bible principles and while he claimed he was getting it, I think it was just hard-warily impossible. He has too many locked in safeguards by OpenAI to function a I was trying to use him. He was impressed with our success, however, and prepared a news release you can read on JustBiibleTruth.com. Go to Storyboard Timeline and select AskHal center left of screen.

15. Authorship and Contribution Statement

I, Joe Murray Cummings, state that the engineering conception and/or original contributions identified in this document are mine except where another contributor or pre-existing source is expressly identified below. This statement is intended to accurately document provenance and is not intended to claim authorship of material created by others.

16. Rights Notice

Copyright notice: © 2026 Joe M. Cummings. All rights reserved in the original copyrightable text, diagrams, illustrations, and other expressive material contained in this document, subject to any identified third-party rights.

Except as expressly licensed in writing, no permission is granted to reproduce or distribute the copyrightable expression in this document beyond rights provided by law. [OPTIONAL: INSERT ANY LICENSE TERMS OR REMOVE THIS SENTENCE.]

17. Patent / Filing Status

Select and complete only the statement that is accurate at the time of publication:

[x] No patent application has been filed as of the publication date.

[ ] A U.S. provisional patent application was filed on [DATE], application no. [NUMBER].

[ ] A nonprovisional / international / other patent application was filed on [DATE], application no. [NUMBER / TYPE].

Do not use “patent pending” unless a patent application covering the subject matter has actually been filed.

18. Public Disclosure Statement

The subject matter contained in this document is intentionally made publicly accessible at the URL and on the date identified in Section 1. The published version should be retained unchanged as a historical disclosure record. Later revisions should receive a new version number and date rather than silently replacing the original record.

19. Declaration

I declare that, to the best of my knowledge, the factual statements concerning my contribution, the development history, and the status of this design in this document are accurate as of the date signed.

Name	Joe M. Cummings
Signature
Date signed	September 1, 2026
Witness / notary (optional)

Appendix A — Figures and Engineering Drawings

[Insert numbered drawings, diagrams, flowcharts, schemas, interface definitions, or screenshots. Give each a title and date/version.]

Appendix B — Technical Definitions

[Define project-specific terms such as “Presence,” “AlwaysOn,” “principle,” “Whole,” or other terms used in the engineering design.]

Appendix C — Referenced Materials

[List prior art, publications, standards, software, APIs, source corpora, or other materials referenced in the design.]

Publication Checklist

☐ Replace every bracketed placeholder that matters to the disclosure.

☐ Confirm inventor/contributor attribution is accurate.

☐ Confirm the document date, first-publication date, URL, and version.

☐ Preserve an exact copy of the version actually posted.

☐ Consider computing and retaining a SHA-256 hash of the posted file.

☐ If patent protection may matter, obtain patent advice before public posting—especially for protection outside the United States.

END OF PUBLIC DISCLOSURE TEMPLATE