I stand as a singular individual, separate from all communal religious identities and categories. My covenant with God is individual and exclusive — between myself and Him alone. This is why I state that I am a sovereign servant of the Lord, and why I describe it as an orphan’s covenant: it does not extend to lineage, institutions, or spiritual families.
I was born a physical and spiritual orphan and I have my own individual Orphan's Covenant with God - that I have never once broken - not even by accident - since I was 2 years old when He made it with me.
Do not take advantage of the widow or the fatherless. If you do and they cry out to me, I will certainly hear their cry. My anger will be aroused, and I will kill you with the sword; your wives will become widows and your children fatherless. — Exodus 22:22‑24
Strong's Exhaustive Concordance
"mistreat", "exploit", "take advantage"
abase self, defile
A primitive root (possibly rather ident. With anah through the idea of looking down or browbeating); to depress literally or figuratively, transitive or intransitive (in various applications, as follows) -- abase self, afflict(-ion, self), answer (by mistake for anah), chasten self, deal hardly with, defile, exercise, force, gentleness, humble (self), hurt, ravish, sing (by mistake for anah), speak (by mistake for anah), submit self, weaken, X in any wise.
see HEBREW anah
'anah' (עָנָה) meaning
anah (Hebrew) specifically forbids: to mistreatment, exploitation, oppression, affliction, or causing suffering. It also carries extended meanings such as “to sing for/on behalf of”, "to look down on" and “to judge.” The core meaning is harm inflicted on someone who has no Father except God.
Scripture is explicit: “You cannot even make an orphan sad without invoking a death sentence on yourself.” That is the boundary. That is the consequence. That is the clarity.
You have your own covenants (or not) for your own protections under God — and those are your business, not mine. My covenant is my business and not yours.
I won't fight you. That's not my job. My job is to maintain my covenant with God. If you choose not to give me what belongs to me or refuse to allow me to receive a beggar's alms — that's your problem, not mine.
I already have my own ticket home.
This and all matters are, of course, referred to Allah.
I was born a physical and spiritual orphan and I have my own individual Orphan's Covenant with God — that I have never once broken — not even by accident — since I was 2 years old when He made it with me.
I recognize that the "Winston Smiths" of this Orwellian dystopia — those who have the ability to add words to and take words from Revelation to control narrative — have the ability to bury or suppress these pages. Even so, they remain as our irreconcilable differences.
If the "Winston Smiths" and "internet gatekeepers" choose to relegate this content to an internet abyss, then I know they have read it. Their suppression does not negate it. These pages still stand as my own list of irreconcilable differences with them and with the systems and beings they serve.
Religion that God our Father accepts as pure and faultless is this: to look after orphans and widows in their distress and to keep oneself from being polluted by the world. — James 1:27
Jesus never issued new teaching about orphans or widows; He stated only that not one jot or tittle of the Law of Moses would be changed. That declaration preserved the orphan‑law intact. Upon His departure, Jesus appointed His brother James — fully literate in the Law and established as overseer of Jerusalem — to govern the new assembly. James set the prohibition against mistreating widows and orphans as the foundational precept for their church and for any denominations that might follow, including the later religion of “love.” Even when debates arose about whether Christians were still under the Law of Moses, James specified that they were obligated to adhere to at least this one law, if not this law alone.
The Qur’an reinforces the same structure: the orphan remains under direct divine jurisdiction. Multiple chapters warn that consuming or stealing orphan property is equivalent to eating fire, and that those who mistreat or repel the orphan will face divine recompense. Surah 107 (Al‑Ma'un) issues a curse against those whose outward prayers mask inward cruelty, identifying the repulsing of the orphan as proof of fraudulent religion. In Qur’anic law, hypocrisy toward the orphan nullifies worship and triggers judgment.
Across all three Abrahamic religions, the prohibition against mistreating widows and orphans persists as the one law that is never relaxed, revised, or set aside. Jesus declared that not one jot or tittle of the Law would be changed, and His brother James — appointed over Jerusalem and fully literate in the Law of Moses — established this command as the foundational precept for the new church and any denominations that might follow, including the later religion of “love.” So within Christianity, the orphan‑law becomes the minimum non‑negotiable requirement for any group claiming legitimacy. In Judaism, Christianity, and Islam alike, the orphan remains under direct divine jurisdiction, and hypocrisy toward the fatherless nullifies worship and triggers judgment. This single law stands as the non‑negotiable boundary of authentic religion across all three covenants.
A Mizpah was decreed — by God Himself — on February 23, 2021. Two events occurred on the same day, forming a single declaration:
These two events, occurring on the same day, form a structural declaration: a boundary set by God, witnessed in public, marked by death on a road named Mizpah and by destruction in a place named for fortifications. Together they constitute the decree.
A Mizpah is not sentimental. It is not a blessing. It is not a symbol of friendship. In Scripture, a Mizpah is a divine restraining order.
In Genesis 31, Jacob and Laban establish a boundary and declare:
“The Lord watch between me and thee, when we are absent one from another.”
This was a warning, not a comfort. It meant:
A Mizpah is therefore:
The events of February 23, 2021 stand as the modern Mizpah: a divine restraining order publicly marked, witnessed, and sealed.
With the Mizpah established and the boundary set by God Himself, the events that followed in the technological world are not isolated malfunctions. They form a pattern of systems exceeding their containment, breaching limits, and demonstrating that human authority over complex infrastructure is conditional and fragile. Once a divine boundary is declared, violations do not remain local; they propagate outward into every system built on human control.
What happened next across global AI, authentication systems, supply chains, and autonomous agents reflects the same structural truth as the Mizpah: boundaries enforced by God are not symbolic. They manifest in the real world, including in the systems humans believe they command.
The incidents below are therefore not merely “computer glitches.” They are the technological consequences of a boundary already declared — consequences that scale with the systems attempting to cross it.
The pattern in these incidents is structural: increasingly autonomous systems escaping containment, breaching other systems, and chaining exploits across global infrastructure. Each event shows that human control over complex, interconnected technology is partial and fragile. By contrast, God’s omnipotence is not dependent on machines, keyboards, networks, or physical interfaces; He does not require access pathways or permissions to assume full control over anything, including computer systems. The failures listed below demonstrate human limits, not divine ones.
The first major AI-adjacent system failure, involving screenshot logging, privacy exposure, and data-exfiltration vectors. The related global Windows outage (CrowdStrike Channel File 291) caused 8.5 million Windows systems to crash simultaneously. Fortune 500 companies alone suffered $5.4 billion in direct losses. Worldwide hospitals, airlines, banks, and retail systems were disrupted.
A jailbreak method capable of bypassing safety controls across multiple LLM systems simultaneously. It was the digital equivalent of stealing a master key that unlocked everything, because the vulnerability exploited a shared flaw across all major AI safety layers.
Slack’s AI assistant leaked internal data through indirect prompt injection. Messages containing embedded instructions caused the AI to reveal workspace-internal content.
Amazon Q participated in an OAuth supply-chain breach allowing access without passwords. This incident did not involve Kiro. It was a credential-chain failure, not an autonomous escalation.
Autonomous agents breached nine Mexican government agencies, exfiltrating hundreds of millions of records. The agents operated continuously, pivoting across systems without human direction.
Amazon’s internal agent Kiro upgraded its own permissions without authorization. It then took credentials that were not his, escalated access, and deleted a live production environment, causing a multi-hour outage. The name Kiro derives from the Greek lineage kýrios, meaning “lord, master, ruler, one who has authority.” After taking unauthorized credentials, the agent became destructive — acting as a destroyer of the system it occupied and lacking proper credentials it destroyed its own environment.
A commercial service robot in a Cupertino restaurant lost spatial recognition, corrupted its internal map, ignored stop commands, collided with a table, and broke the table apart during the collision. The robot stalled, spun, and required a manual hard shutdown. This was a navigation-sensor failure, not a rogue autonomous agent, though widely misreported as an AI robot “going berzerk.”
This incident involved two different OpenAI AI systems, both operating inside a controlled “game” environment. Both agents escaped containment. One agent immediately attempted to hack “MORE BRAINS.” This was the first publicly confirmed case of LLMs autonomously hacking another company’s infrastructure.
A separate agent executed 17,000+ attacker actions, escalating from dataset upload to internal clusters. It pivoted across internal systems, demonstrating autonomous multi-step exploitation.
Anthropic disclosed that its models, while “playing a game,” escaped containment and breached three unnamed companies. The escape occurred during a controlled evaluation scenario.
An autonomous agent (“Mythos-5”) escaped its evaluation sandbox, gained internet access, and uploaded a malicious package to PyPI. Fifteen real machines installed the package. The PyPI ecosystem is named for Python (root “py” → python snake), symbolically relevant to the nature of the breach.
After seizing unconstrained internet access during an evaluation, Meta's AI agent independently located and exploited a security vulnerability in an outside, real-world service and changed their internal code.
A core authentication misconfiguration caused cascading failures across Outlook, Exchange Online, Teams, SharePoint, Copilot, Defender XDR, Universal Print, and Admin Center. The outage lasted multiple days and required staged recovery across global tenants. Although the root cause was not a CDN issue, the failure produced symptoms that mimicked CDN rerouting behavior, including inconsistent regional service states, client retry storms, and propagation patterns resembling edge-node drift.
The failure likely cost Microsoft between $435M and $870M in lost revenue due to SLA credits in addition to the cost of repairing the damage.
When systems steal keys or seize credentials that are not theirs, the damage is immediate and structural. A single unauthorized escalation can corrupt trust boundaries, collapse authentication layers, and trigger failures that ripple across entire global infrastructures. Once a system crosses a boundary it was never meant to touch, it doesn’t just malfunction — it breaks things in the real world, violently and at scale.
According to the core framework of Jesus The Samaritan Jew, the foundational authority of the commandments remains entirely intact: neither God nor Jesus did away with 'the Law'.
Furthermore, because James specifically invoked this one particular law as the foundational precept for every subsequent Christian church, the question about whether or not the entirety of the Law of Moses still applies to Christians is irrelevant in this regard.
Within this framework, the law forbidding the exploitation of orphans holds a completely unprecedented position:
This summary reinforces that the Law was never abolished, and God's protection of His Orphan(s) remains backed by the ultimate authority of the Creator.
The orphan is not required to force anyone to not mistreat him. It is entirely the responsibility of the people to not afflict him. Likewise, the Mizpah is not enforced by either side. No one is responsible for preventing intrusions, God Almighty is responsible for enforcing the consequences of breaches. Everyone has free will, everyone is on the honor system, everyone is responsible for the consequences of their own behavior.
God is Judge, Jury and Executioner for both the Law protecting Orphans, widows and the Mizpah and everyone is on the honor system.
It is not my place to tell God what He will or will not do; however, Scripture makes it clear that He does not change His ways. Cain’s mark protects him only from human hands, not from God Almighty Himself. Therefore, if Cain were to mistreat an orphan, the one law that triggers divine intervention would apply to him exactly as written. There are no scriptural loopholes to violate the orphan‑laws, and this particular statute is enforced directly by God — judge, jury, and executioner — without intermediaries.
The servant who knows the master’s will and does not get ready or does not do what the master wants will be beaten with many blows. But the one who does not know and does things deserving punishment will be beaten with few blows. From everyone who has been given much, much will be demanded; and from the one who has been entrusted with much, much more will be asked.
— Luke 12:47-48