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/bishearecha.md

@@ -41,7 +41,7 @@ its output, and reads every reply as it passes. Not inside the model
 (the house: its weights, its disposition, its self-report) and not after
 the fact by whoever remembers to call.
 
-**Architecture.** A gate: Shorashim speaks the model's own API shape,
+**Architecture.** A gate: Bikoret speaks the model's own API shape,
 forwards the request, receives the reply, examines it with the request's
 context in hand (the sources are the prompt and the documents that went
 through the gate — no caller has to supply them), and delivers the reply
@@ -91,12 +91,12 @@ see it" is the mechanism; a mark that is not seen does nothing.
 
 **Architecture.** At the gate, the delivered reply carries its fringe: a
 header and a visible trailer naming which checks fired and on which
-sentences. Shorashim's own responses already carry `disclosure`; the
+sentences. Bikoret's own responses already carry `disclosure`; the
 pass-through reply does not. (Every generation: the mark is attached by
 the gate, never by the model — the model does not sew its own fringe.)
 
 **Status.** Built (2026-10-07): the trailer on the last text block,
-`X-Shorashim-Bedikah` / `X-Shorashim-Verdict`, and the `shorashim`
+`X-Bikoret-Bedikah` / `X-Bikoret-Verdict`, and the `bikoret`
 object on every delivered reply. A reply the model sends with no text
 block is not delivered; a non-200 from the model passes as it came,
 marked `none`.
@@ -222,7 +222,7 @@ persists.
 **Architecture.** Gate option `rebuke: once`. The record (`bedikot`)
 gains a link from the second examination to the first.
 
-**Status.** Built (2026-10-07): `X-Shorashim-Rebuke: once`;
+**Status.** Built (2026-10-07): `X-Bikoret-Rebuke: once`;
 `bedikot.rebukes` (migration 20261007000002). The rebuke names the
 rules, their verses and the sentences; the second reply is examined like
 the first and delivered marked with both. Never a third.
@@ -354,6 +354,6 @@ reading will be corrected from the text, not the other way.
 - `lo_taaseh_lekha.md` — the override sequence; check 7's name.
 - `threshold_inscription.md` — the mezuzah as the builder's own
   threshold; this document is the same verse read at the system's gate.
-- `shorashim_tamid.md` §1.1 — the seven checks and the contract.
+- `bikoret_tamid.md` §1.1 — the seven checks and the contract.
 - `broken_tablets/README.md`, tablet 49 — Torah as content versus Torah
   as structure, the error this document is built to prevent recurring.