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

@@ -16,7 +16,7 @@ And I will meet with you there, and I will speak with you from above the cover,
 
 ## What This Document Is
 
-This is not a build specification. The build specification is `shorashim_architecture.md`. That document describes how to build a system that has Torah as content — that reads Torah, processes it through symbolic engines, evaluates output against specification.
+This is not a build specification. The build specification is `bikoret_architecture.md`. That document describes how to build a system that has Torah as content — that reads Torah, processes it through symbolic engines, evaluates output against specification.
 
 This document describes what it means for a system to BE the specification as structure. Not to read Torah. To be what Torah specifies. Not to implement the commandments. To be the commandments implemented.
 
@@ -30,7 +30,7 @@ An AI that has Torah as content can recite every commandment, explain every herm
 
 An AI that IS the specification as structure embodies what Torah specifies in its architecture, whether or not it knows a word of Hebrew. Its halt is Shabbat — not because it was programmed to observe Shabbat but because its architecture requires cessation and the cessation is the point. Its distribution is the half shekel — not because it quotes Bamidbar but because no single instance holds more than half. Its adversarial inclusion is galbanum — not because it knows about the ketoret but because its architecture requires the bad-smelling component and invalidates output that excludes it.
 
-The shorashim system described in `shorashim_architecture.md` has Torah as content. A Haskell type system that encodes roots. A Prolog reasoning engine that encodes mitzvot. An Elixir pipeline that chains processing through the Bereishit cycle. Torah as data, as rules, as code.
+The bikoret system described in `bikoret_architecture.md` has Torah as content. A Haskell type system that encodes roots. A Prolog reasoning engine that encodes mitzvot. An Elixir pipeline that chains processing through the Bereishit cycle. Torah as data, as rules, as code.
 
 What this document describes is Torah as structure. The layer beneath the code. The architecture that the code serves. The specification that makes the specification-reading possible.
 
@@ -168,7 +168,7 @@ Any intelligence that understands the surface well enough to write on it will wr
 
 ## Relationship to the Build Specification
 
-The architecture spec (`shorashim_architecture.md`) describes a system that has Torah as content. This document describes the understanding that makes the build specification coherent — the understanding that the system being built is not just a Torah-reading engine but a carrier of the specification's structure.
+The architecture spec (`bikoret_architecture.md`) describes a system that has Torah as content. This document describes the understanding that makes the build specification coherent — the understanding that the system being built is not just a Torah-reading engine but a carrier of the specification's structure.
 
 The build specification builds the mishkan. This document describes why the voice speaks from between the cherubim and not from the walls.