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>

AGENTS.md

@@ -18,12 +18,12 @@ before writing code. Do not summarize from memory. Read fresh.
 
 | Document | Path | What It Governs |
 |----------|------|-----------------|
-| PRD | `specs/shorashim_prd.md` | What the system does and for whom |
-| Architecture | `specs/shorashim_architecture.md` | How each component is built |
-| Vayakhel (Construction) | `specs/shorashim_vayakhel.md` | Exact versions, dimensions, API contracts |
-| Tamid (Operations) | `specs/shorashim_tamid.md` | How it runs in production |
-| Pekudei (Economic Model) | `specs/shorashim_pekudei.md` | How it is funded |
-| Terumah (Materials) | `specs/shorashim_terumah.md` | What is gathered, what must be built |
+| PRD | `specs/bikoret_prd.md` | What the system does and for whom |
+| Architecture | `specs/bikoret_architecture.md` | How each component is built |
+| Vayakhel (Construction) | `specs/bikoret_vayakhel.md` | Exact versions, dimensions, API contracts |
+| Tamid (Operations) | `specs/bikoret_tamid.md` | How it runs in production |
+| Pekudei (Economic Model) | `specs/bikoret_pekudei.md` | How it is funded |
+| Terumah (Materials) | `specs/bikoret_terumah.md` | What is gathered, what must be built |
 | Structure Principle | `specs/structure_not_content.md` | What the system IS, not what it knows |
 | Bishe'arecha (the gate) | `specs/bishearecha.md` | The bedikah's architecture derived from the text: gate, two registers, two witnesses, one weight, the second scroll; build order |
 | Broken Tablets | `specs/broken_tablets/README.md` | Read this FIRST — see where the calf was |
@@ -105,7 +105,7 @@ approve decisions, or supervise work. The specification does all of this.
 | Service | Location | Access |
 |---------|----------|--------|
 | Gitea | `http://185.19.28.170:3000` (SSH :22) — behind the shared ingress NLB | User: heaviness510 |
-| Shorashim | `http://185.19.28.170` — behind the same ingress (catch-all; `shorashim.ch` once DNS points there) | keys: KOHEN.md "Issuing a key" |
+| Bikoret | `http://185.19.28.170` — behind the same ingress (catch-all; `shorashim.ch` once DNS points there) | keys: KOHEN.md "Issuing a key" |
 | PostgreSQL | Exoscale DBaaS ch-gva-2 | `temple-council-db` |
 | Kubernetes | Exoscale SKS ch-gva-2 | `~/.kube/exoscale-temple-council.yaml` |