The Fourth HorseThe Fourth Horse

The Zakkai Yehuda Temple Lock

2026-02-03

Institutional Lock

Description

On February 3, 2026, the ordinance reservation for Zakkai Yehuda's FamilySearch profile PH6Q-1TR was placed by FamilySearch Support itself, under the user ID FS-Admin. The baptism was performed the next day, February 4, 2026. Three months later, in May 2026, the delete war began on the same profile. The sequence shows the lock was set first and the disassembly followed under its cover: premeditated, not opportunistic. A regular FamilySearch user reserving ordinances passes through standard submission queues with wait times and processing delays. FS-Admin bypassed them, which places the lock at the platform level, an institutional action rather than a user action. The lock positioned on the 9th Exilarch's profile protected the disassembly that followed. Open question held at Yet to Be Verified: who directed the FS-Admin reservation, whether through a support ticket or an internal directive. Evidentiary tier: DOCUMENTED, FamilySearch ordinance reservation records, direct observation, Research_3/045.

Significance

The temple lock on the Davidic line was set by the platform's own support infrastructure three months before the delete war began, confirming an institutional actor inside FamilySearch rather than a rogue user. Lock first, disassembly second.

Themes

THEOLOGYDEMOGRAPHICSFamilySearch Temple LockInstitutional ActorDavidic Lineage

Linked People (1)