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>

BUILD_KORBAN.md

@@ -11,8 +11,8 @@ Moshe assembled the whole congregation and said: these are the things God comman
 Read these files in this order. Do not summarize from memory. Read fresh.
 
 1. `specs/structure_not_content.md` — **Read this first.** This changes what the build means.
-2. `specs/shorashim_architecture.md` §3.5 (Korban Processor)
-3. `specs/shorashim_vayakhel.md` §1.4 (Python dependencies), §3.4 (external model API contracts)
+2. `specs/bikoret_architecture.md` §3.5 (Korban Processor)
+3. `specs/bikoret_vayakhel.md` §1.4 (Python dependencies), §3.4 (external model API contracts)
 4. `specs/broken_tablets/README.md` — see where the calf was
 5. This file