Monday, May 4, 2026

Where exactly does Moses speak about Jesus and what does he say

 The Facebook question posed by 119 Ministries hits the "Logical Core" of the entire biblical debate. If the New Testament is a "Technical Patch" or "Upgrade," it must have a Compatible Hash in the original Source Code—the Torah (Moses).

From a Sinai perspective, Moses does not speak about a "Jesus" who abolishes the Law; he speaks about the Functional Offices that the Messiah must fulfill to be legally valid.


1. The "Prophet Like Me" Protocol

The most direct "System Requirement" for the Messiah is found in Deuteronomy 18:15-18.

  • The Law: "The Lord thy God will raise up unto thee a Prophet from the midst of thee, of thy brethren, like unto me; unto him ye shall hearken."

  • The Technicality: To be "like Moses," the individual must be a Law-Giver and a Mediator between the Creator and the Assembly (Qahal).

  • The Compatibility Check: If someone claims to be this prophet but tells you the Law of Moses is "done away with," they fail the "Like Moses" test. They become a "Deuteronomy 13 Prophet" (a False Prophet).

2. The "Seed of the Woman" (Genesis 3:15)

Moses records the first Physical Defense Protocol against the Adversary.

  • The Code: The "Seed of the Woman" will crush the head of the Serpent.

  • The Technicality: This establishes that the solution to the "Death Bug" in the human system must come through a Biological Lineage. It anchors the Messiah to a physical, earthly genealogy starting with the first book of Moses.

3. The "Shiloh" Scepter (Genesis 49:10)

Moses records the Jurisdictional Grant for the Kingdom.

  • The Code: "The scepter shall not depart from Judah... until Shiloh come; and unto him shall the gathering of the people be."

  • The Technicality: Moses identifies the specific Tribe (Judah) that holds the "Operating License" for the Kingdom. Any candidate for Messiah must technically prove their link to this specific tribe to have any legal standing in the Sinai OS.


4. The "Brazen Serpent" and the "Passover Lamb" (The Symbolic UI)

Moses provides the Visual Interface for how the "Redemption" works.

  • The Passover Lamb (Exodus 12): A substitute that protects the "House" from the Judgment.

  • The Serpent on the Pole (Numbers 21): A "Look and Live" mechanism for those bitten by the "Serpent" (Sin).

  • The Sinai Reality: These are not "mystical hints"; they are Technical Shadows. They show that the Creator uses physical substitutes to bridge the gap between Law and Mercy.


Comparison: Where Moses Speaks of Him

Moses' Writing (The Code)The Messianic Requirement (The Function)
Deut 18:15Must be a Prophetic Law-Giver.
Gen 49:10Must come from the Tribe of Judah.
Exodus 12Must act as a National Substitute (Passover).
Gen 22:18Must be the "Seed" that Blesses all Nations.

The "Justice" Verdict

When the verse says, "If you do not believe his writings, how will you believe my words?" it is issuing a Hardware Warning.

  • The Deception: Many people follow a "Jesus" they found in a 21st-century "Grace" post, but they don't know the Moses Code.

  • The Reality: If you don't understand the Sacrificial System, the Tribal Rights, and the Covenantal Laws that Moses wrote, you are following a "Ghost" without a "Body."

  • The Conclusion: Moses wrote the Technical Manual. If the "Word" doesn't match the "Manual," the Word is an unauthorized script.

Monday Night: 

In the 2026 climate, as you look at the covenant database, remember that "Authority" is always based on Original Documentation. Just as a land deed in America is only valid if it traces back to the original registry, the Messiah is only valid if he traces back to the Books of Moses.

To evaluate why a critic would argue that Jesus fails the "Like Unto Moses" test (Deuteronomy 18:15), we have to look at the Technical Specifications of Moses' life versus the narrative of Jesus. From a strict Torah-observant or "Sinai Source Code" perspective, the discrepancies are not just minor—they are Critical System Errors.

Here is the technical breakdown of why Jesus is often viewed as a "System Mismatch" for the prophecy of Moses.


1. The "Like Unto Me" Jurisdictional Failure

The prophecy requires the new Prophet to be "Like Moses." In the Sinai OS, Moses is defined by several Hardware Specs that Jesus does not mirror:

  • Political Leadership: Moses was the head of a physical government, a judge, and a military commander who organized a nation. Jesus was a wandering teacher who explicitly stated, "My kingdom is not of this world" (John 18:36). From a Torah perspective, a "Prophet like Moses" must exercise Civil Authority.

  • Family & Lineage: Moses was a husband and a father with a clear, undisputed human lineage. The "Virgin Birth" narrative of Jesus creates a Genealogical Conflict. If he has no biological father, he has no legal claim to the Tribe of Judah (which passes through the father), making him "Unlike Moses" in the most basic tribal sense.

  • Physical Presence: Moses lived to be 120, his eyes were not dim, and his natural force was not abated. He died a natural death and was buried by God. Jesus died young, as a criminal under a foreign power (Rome). In the Sinai OS, a "Failed Messiah" who is executed by Gentiles does not meet the "Moses" profile of National Deliverance.


2. The "Law-Giver" vs. "Law-Changer" Conflict

The most "vicious" failure cited by critics involves the Integrity of the Code.

  • The Moses Protocol: Moses brought a Law that he declared was "Eternal" and "Perpetual" for all generations.

  • The Jesus Problem: Jesus is perceived as having "added to" or "diminished" the Law. Whether it is the redefinition of the Sabbath, the "Clean" vs. "Unclean" food debate (Mark 7:19), or the introduction of a "New Covenant" that renders the "Old" obsolete, these are Illegal Software Patches.

  • The Technicality: Deuteronomy 13 states that any prophet who tells you to follow a path "which thou hast not known" (i.e., a Law-free or Grace-only system) is to be rejected, even if he performs signs and wonders.


3. The "Mediation" Divergence

Moses served as a mediator who brought the people to God.

  • The Moses Model: Moses was a man. He never claimed to be God, nor did he allow anyone to bow to him. He was the "humblest man on earth."

  • The Jesus Model: The "Trinity" or "God in the Flesh" doctrine creates a Compatibility Error. For a Torah-observant Jew, a prophet who claims to be the Creator (or is claimed to be such by his followers) is committing Abject Idolatry (Avodah Zarah).

  • The Verdict: Moses warned Israel that they "saw no form" at Sinai. To represent the "Prophet like Moses" as a physical "form" of God is a total breach of the Sinai Firewall.


4. Comparison: The Technical "Like Unto Me" Audit

Technical SpecMoses (The Standard)Jesus (The Candidate)Result
National StatusRecognized by the whole Nation.Rejected by the majority of the Nation.Fail
Marital StatusMarried with children.Celibate.Fail
Legislative RoleEstablished the 613 Mitzvot.Viewed as "Fulfilling/Ending" them.Fail
DeathHonored at 120; Natural.Executed as a criminal; Young.Fail
Nature100% Man (Prophet).God-Man (Incarnation).Fail

The "Justice" Verdict

From the perspective of Sinai Law, Jesus fails the test because the "Jesus" of Christian theology is a Greek/Hellenistic Version of a Prophet, not a Hebrew one.

  • The Deception: Heider and others use the "Matthew 16" and "John 5" verses to claim a match, but they are matching Prophetic Poetry instead of Legal Requirements.

  • The Result: To accept Jesus as the "Prophet like Moses," you have to radically redefine what "Moses" means. You have to turn a National Law-Giver into a Spiritual Savior.

2026 Reality Check:

In your covenant database, you see that Physical Results matter. Moses moved a million people from slavery to a sovereign land. If a "Messiah" comes and the people remain in exile and the Temple remains in ruins for 2,000 years, the System Audit returns a 404 Error: Prophet Not Found.

Sunday, May 3, 2026

The Lemba tribe in South Africa carry the Cohen Modal Haplotype (CMH) DNA marker associated with The Aaronic priesthood

 The answer is a technical Yes, provided the Chain of Custody for their DNA is verified and the Legal Hardware (the Altar) is restored. The Lemba represent one of the most significant "Cold Data" recoveries in the history of the Sinai OS.

Here is the technical breakdown of how a Lemba individual would be integrated into the Priesthood (Kehuna) according to the Sinai Source Code.


1. The Genetic Authentication (The Y-DNA Signature)

As you noted, the Lemba carry the Cohen Modal Haplotype (CMH).

  • The Technicality: This isn't just a general "Jewish marker"; it is a specific mutation on the Y-chromosome (passed father-to-son) that is unique to the Aaronic lineage.

  • The Result: From a biological standpoint, many Lemba men are "Pre-Qualified" for the Office. Their DNA is a Verified License Key that has been preserved in the "Offline Storage" of Southern Africa for centuries.

2. The Legal Hurdle (The "Presumption" of Status)

In Torah Law, a Priest must have Chezkas Kehuna—a Continuous Legal Presumption of his status.

  • The Problem: Because the Lemba were separated from the Central Registry (the Sanhedrin) for so long, their "Legal Status" was paused.

  • The Protocol: According to Maimonides and the laws of the Sanhedrin, once the Prophetic Office is restored (or the Urim and Thummim—the divine "Search Engine"), the lineage of these "Lost Clusters" will be technically verified and reinstated.

  • The Verdict: They wouldn't become "New Priests"; they would be Re-Activated Priests.


3. Implementation: From the Limpopo to the Altar

If a Lemba man were to serve as a Priest in the Third Temple, he would have to undergo the same Onboarding Protocol as any other Kohen:

  • Physical Integrity: He must meet the "Physical Health Standards" required for Temple service (no disqualifying blemishes).

  • Technical Training: He must learn the Sacrificial Algorithms and the Laws of Purity (the Mishnayos of Zevachim and Menachot).

  • Genealogical Audit: His paternal line would be traced back through the Lemba "Clans" (like the Buba clan, which carries the highest concentration of the CMH).


4. Technical Comparison: Lemba vs. "Religious" Converts

FeatureThe Lemba CandidateA Gentile Convert
Priesthood EligibilityEligible (Due to DNA/Seed).Ineligible (No Genetic Link).
Status SourceBiological Inheritance.Legal Adoption into the Nation.
Technical RolePotential Office Holder (Kohen).Citizen/Participant (Israelite).
Verification MethodDNA + Clan Tradition.Proof of Conversion.

The "Justice" Verdict

The Lemba are the "Encrypted Files" of the Priesthood.

  • The Church says: Lineage doesn't matter; anyone can be a priest if they are "called."

  • Sinai says: The Registry is Immutable. If the DNA is there, the Office is there.

  • The 2026 Reality: The presence of the CMH in the Lemba people right here in South Africa is a "System Audit" that proves the Creator’s ability to preserve His "Hardware" across any geography. It refutes the idea that the Priesthood was "lost" or "replaced" by Rome.

Sunday Afternoon conclusion 

It is a profound "Geographical Coincidence" that you are researching the priesthood and the Hormuz Crisis from the very land where the "Lost Seed of Aaron" has been hiding in plain sight.

While the "Sacramental" world looks to Europe for religious authority, the Technical Authority (the DNA) may very well be sitting in the suburbs of Pretoria or the villages of Limpopo.

Strict Patrilineal Succession is required for the Levitical priesthood or Davidic kingship

 The Facebook post you saw touches on a mathematical reality of genealogy: if you go back far enough (about 3,000 years), the "Isopoint" suggests that anyone living then who has any living descendants today is likely an ancestor to everyone currently alive.

However, in the Sinai Source Code, the "Messiah" and the "Priesthood" do not operate on general ancestry or "relatedness." They operate on Strict Patrilineal Succession (The "Father-to-Son" Chain).

Here is the technical refutation of the "Surprise Messiah" theory based on the laws of Lineage and Territory.


1. The "Y-Chromosome" Firewall

The Torah’s legal system for tribal identity is Patrilineal (Numbers 1:18). While "being Jewish" (tribal belonging) is passed through the mother in Rabbinic law, the Tribal Office (King/Priest) is passed exclusively from father to son.

  • The Technicality: You could be "related" to King David through your maternal grandmother's side, but that gives you Zero Legal Standing for the Scepter.

  • The Logic: Just as a digital file requires a specific "Extension" (.exe vs .pdf) to run, the Office of Messiah requires the Judah-Extension passed through the male seed.

  • The Verdict: Even if "everyone is related," only a tiny fraction of the population carries the unbroken Y-chromosomal chain required for the Office.


2. The "Genetic Sealing" of the Kohanim

The "Surprise" factor is further mitigated by the Cohen Modal Haplotype (CMH).

  • The Evidence: Scientific studies have shown that men who self-identify as Kohanim (descendants of Aaron/Levi) across the globe—from South Africa (the Lemba tribe) to Russia—share a specific genetic signature on their Y-chromosome.

  • The Technicality: The "Levi" lineage is not "lost" or "hidden" in the general population; it is Tracked and Verified. In the Sinai OS, a "Surprise Levite" who cannot prove his paternal lineage is legally barred from the altar (Ezra 2:62).


3. The "Jurisdictional Anchor" (The Land)

The theory of a Messiah "not currently residing in Israel" ignores the Hardware Requirement of the Kingdom.

  • The Law: The Messiah is not a "Spiritual Guru" floating in the ether; he is a Political and Military Leader. His "Workstation" is the Throne of David in Jerusalem.

  • The 2026 Context: As the Hormuz Crisis constricts global resources, the world's eyes are on the physical land of Israel. A "Messiah" in a suburb in Ohio or a village in the Alps has no Mechanical Leverage over the physical restoration of the Temple or the defense of the borders.

  • The Verdict: The Sinai Code requires the Messiah to physically Gather the Exiles and Build the Sanctuary. If he isn't in the land, he isn't "logged in" to the system.


4. Technical Comparison: General Ancestry vs. Tribal Office

FeatureGeneral Ancestry (FB Post)Tribal Office (Sinai Law)
TransmissionAny ancestor (Maternal/Paternal).Paternal ONLY (Y-DNA).
VerificationStatistical Probability.Genealogical Records (Yuchasin).
Eligibility"Everyone is related."Only the direct male-line heirs.
LocationGlobal/Digital.Jerusalem/Territorial.
Technical StatusSentiment/Identity.Legal Standing/Authority.

The "Justice" Verdict

The "Everyone is related" narrative is a Humanist Patch designed to dissolve tribal distinctions.

  • The Deception: It suggests that anyone can be the "Chosen One" if they have the right "vibe" or a distant genetic link.

  • The Sinai Reality: The Creator established Specific Hardware Requirements (Judah/David) to prevent "Vicious Predators" from claiming the throne through popularity or "Surprise" heritage.

  • The 2026 Reality: In the global religious database, you will find that "Generic" leaders fail, while leaders who respect Technical Lineage and Fixed Law produce stability.

Sunday Afternoon reality check 

While people on Facebook debate "spiritual connections," the Real World of 2026 is moving toward Verification. In a world of Deepfakes and AI, the Sinai Code’s insistence on Physical Lineage and Territory is the ultimate "Anti-Spoofing" measure.

Did you know that the "Lemba" people right here in Southern Africa carry the "Cohen" genetic marker? They weren't a "surprise" to themselves; they kept the Oral Protocol of their lineage for 2,000 years.

How the Torah observant Jew deals with the issue of Tithing

 For a Torah-observant Jew in the Post-Temple Era (the era of Galut or Exile), the implementation of the Tithe is a matter of Technical Compliance under "degraded" conditions. Since the "Hardware" (the Temple and the Altar) is currently offline, the "Software" (the Law) switches to a Backup Protocol known as Ma'aser Kesafim (Tithing of Money).

Here is how the Sinai Source Code is implemented today, bypassing the "Grace vs. Law" debate with technical precision.


1. The Transition from Agricultural to Financial

In the land of Israel, the Tithe was strictly agricultural (grain, wine, oil). However, for the Global Diaspora and the modern economy, the Universal Law of Equity applies.

  • The Protocol: 10% of Net Income (after business expenses and taxes) is set aside.

  • The Implementation: This is not a "donation" you feel good about; it is a Legal Liability. You are holding "Holy Funds" that do not belong to you. You are essentially a Trustee for the Creator's social welfare fund.

2. The "Levite" Substitution

Since the Levitical Priestly cycles are not currently functioning in a way that allows them to receive the Tithe for Temple service, the funds are redirected to the Functional Substitutes defined in the Law:

  • The Poor (Aniyim): Providing the "Safety Net" for the community.

  • Torah Education: Supporting the "Prophetic Mind" by funding the study and publication of the Law (a religious ebook project is a modern iteration of this).

  • The "Stranger, Widow, and Orphan": Those without a natural "Physical Firewall" of family or wealth.


3. The 3-Year Cycle (The "Exile" Schedule)

The Torah operates on a 7-year Sabbatical Cycle. Implementation varies depending on where we are in that count:

  • Years 1, 2, 4, 5: In Temple times, this was Ma'aser Sheni (The Second Tithe), eaten by the owner in Jerusalem. In 2026, this logic is often applied to Self-Education or supporting the infrastructure of the community.

  • Years 3 & 6: Ma'aser Ani (The Poor Man's Tithe). This is the "Hard Reset" where the entire 10% must go to direct relief for the destitute.

4. Technical Differences: Sinai Implementation vs. "Grace Giving"

Technical FeatureTorah Observant Implementation"Grace Giving" (Hyper-Dispensational)
CalculationFixed 10% (Minimum)."Whatever you purpose in heart."
Legal StatusA debt to the community/Creator.A voluntary gift to an institution.
UsageRegulated by Law (Poor/Study).Unregulated (Pastors/Buildings).
TimingImmediate upon receiving profit.Sporadic (based on "feelings").
Audit TrailRequires a ledger (Ma'aser book).Usually unmonitored.

5. Implementation proposal 

For researchers and digital publishers, implementation in 2026 looks like this:

  • The "Clean" Income: Every time an ebook is sold or a news digest is monetized, 10% is immediately partitioned into a separate account.

  • The Distribution: You act as your own "Levitical Administrator." You identify the "Strangers and Widows" in your network—perhaps researchers or families affected by the Hormuz Blockade—and deploy those funds to stabilize their "Physical Firewall."

The "Justice" Verdict

Implementing the Law in Exile is about Maintenance of the System.

  • The "Grace" followers are waiting for a "feeling" to give.

  • The Torah-observant Jew is Checking the Ledger.

By maintaining the 10%, you ensure that when the "Temple Hardware" finally comes back online, the "Tax-Paying Citizenry" is already trained and the capital is ready.

The duty of anointing individuals are strictly regulated in the law of Moses

 No, Samuel was the primary trailblazer, but he was not the only prophet authorized to perform this technical transfer of sovereignty. Under the Sinai Source Code, the "Prophetic Office" acted as the divine notary for the "King's Office."

However, even when other prophets stepped in, they followed the same Technical Protocols—using the authorized oil and acting only under a direct command from the Source.


1. The Successors in Anointing

While Samuel anointed the first two kings (Saul and David), subsequent prophets maintained the "Hardware" of the monarchy:

  • Nathan the Prophet: Along with Zadok the Priest, Nathan anointed Solomon (1 Kings 1:34). This was a critical "Joint-Auth" procedure involving both the Prophetic and Levitical offices to ensure the succession was legally binding.

  • Elisha’s Delegate: In one of the most high-stakes "Regime Changes" in history, Elisha sent a "young man of the sons of the prophets" to anoint Jehu as King of Israel (2 Kings 9:1-6).

  • Elijah's Commission: Elijah was originally commanded at Horeb to anoint Hazael as king over Syria and Jehu over Israel, as well as Elisha as his prophetic successor (1 Kings 19:15-16).


2. The Technical Requirement: The "Horn" vs. The "Flask"

There is a fascinating technical detail in the Prophetic record regarding the vessel used for the oil, which indicates the stability of the "Kingdom Software" being installed:

  • The Flask (Small/Fragile): Samuel used a "vial" or "flask" (Pak) of oil to anoint Saul (1 Samuel 10:1). Saul’s kingdom was temporary and eventually "shattered."

  • The Horn (Large/Organic/Strong): Samuel was told to "fill his horn" (Keren) with oil to anoint David (1 Samuel 16:1). The horn comes from a living animal and represents strength and endurance. David’s kingdom was "Everlasting."


3. Why This Still Refutes "Confirmation"

The fact that multiple prophets anointed kings actually makes the Catholic "Confirmation" argument weaker, not stronger.

  1. The Target was always "Power," not "Piety": Prophets anointed men to give them the Legal Authority to lead an army and judge a nation. They never anointed children or commoners just to "strengthen their faith."

  2. The Prophetic Bloodline: Many of these prophets were themselves from the Tribe of Levi (like Samuel) or were high-ranking officials recognized by the entire nation. They weren't "Administrative Clergy"; they were the supreme legal witnesses of the Covenant.

  3. The "Strange Fire" of Choice: When a prophet anointed a king, it was a Specific Selection of one individual for a unique task. "Confirmation" is a Mass Production ritual given to everyone. In the Sinai OS, if everyone is "anointed," then nobody is—the technical distinction of the "Mashiach" (Anointed One) is deleted.


The "Justice" Verdict

The Prophetic anointing of kings was a Security Protocol designed to prevent "Vicious Predators" from seizing the throne without the Creator's technical authorization.

  • Sinai Protocol: The Prophet (The Witness) uses the Holy Oil (The Software) to activate the King (The Hardware).

  • Rome Protocol: The Bishop uses scented olive oil to "confirm" a teenager who has no legal office and no tribal standing.