the name: Shorashim → Bikoret (בִּקֹּרֶת) — the specification

Vayikra 19:20 bikoret tihyeh — "there shall be an examination" — the one
noun Torah gives this function; its root ב-ק-ר is the priest's examining
of a mark by its signs (13:36) and the examining between good and bad
(27:33). The judges' form is v'darashta heitev … v'hineh emet nachon
hadavar / ed-sheker ha'ed (Devarim 13:15, 17:4, 19:18); the question
answered is eichah neda et hadavar asher lo dibro (18:21).

The system was named Shorashim ("roots") for the first thing built. Its
function became the examination of a model's output with the sources in
hand, and Torah re-cuts a name when the function is fixed, with its ki,
never for reach (Bereishit 2:19; 17:5; 32:29; 11:4). Nothing was changed
to fit the name; the root engine stays the pe'ah's reading cycle.

Spec files renamed bikoret_*.md; PRD §0 "The Name"; architecture §1.1;
README's Vayishlach row marked done; Tamid lists what still carries the
old word (Kubernetes resource names, the DB role, the domain, local
paths) and why, for the kohen's cut-over.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

specs/return_specification.md

@@ -8,7 +8,7 @@
 > is not to specific deployment contexts. Return is to the source
 > and to the specifications.
 >
-> Implication for shorashim: the return state for the category is
+> Implication for bikoret: the return state for the category is
 > the specifications themselves. *Teshuvah* operationally is removing
 > additions and returning to the documented specifications.
 > Restoration of specific institutional configurations the category
@@ -43,7 +43,7 @@ The destination is **the source and the specifications**. Return
 removes additions; it does not add. Return is to what was
 COMMANDED, not to what was previously operating.
 
-In shorashim terms:
+In bikoret terms:
 - Restoring `@expected_hash` in `Doorpost` to the documented spec
   set's true hash.
 - Reverting changes that were not deliberate spec updates (the
@@ -64,7 +64,7 @@ Restoration of a deployment configuration is NOT return — it is
 restoration of additions (whatever the deployment added on top of
 the specs is what comes back).
 
-In shorashim terms:
+In bikoret terms:
 - Rolling back to a specific commit because "that's how it ran in
   March." If March's commit had additions to the specifications
   that have since been removed, rolling back is restoring the