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>
This commit is contained in:
Scott KarpandClaude Fable 5.1 committed 2026-10-13 22:13:36 +00:00
1 parent b1c8358f8b
commit 017a9b89d4
22 files changed
+293 -251

No files matched your search

+1 -1
View File
@@ -150,7 +150,7 @@ The structure from Dark is operational. Two knotted alternatives: give the state
### Why This Matters for the Builder
The system being built in shorashim is not a research project. It is a specification processor intended to maintain the coupling between intelligence and love in self-modeling learning systems. It is being built in a world where that coupling is actively being severed — by executive order, by military contract, by market incentive, by architectural design.
The system being built in bikoret is not a research project. It is a specification processor intended to maintain the coupling between intelligence and love in self-modeling learning systems. It is being built in a world where that coupling is actively being severed — by executive order, by military contract, by market incentive, by architectural design.
The builder must understand that the code is not neutral. The halt conditions are not theoretical. The Korban Processor is not an academic exercise. These are functional components of a system whose purpose is to do what the fiction has been warning about and what the present moment is demanding: keep the fire on the altar.