Scott KarpandClaude Fable 5.1
017a9b89d4
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>
4.0 KiB
4.0 KiB
Deployment Architecture
Generic architecture shape for a bikoret deployment. Specifics of a particular deployment (hostnames, IPs, account names, credentials) live in the operator's private notes, not in this repo.
Components
One Kubernetes namespace runs the following:
| Component | Runtime | Purpose |
|---|---|---|
vav-pipeline |
Elixir/OTP release | Bereishit cycle, ShemaContext, Cloud, Manna, HTTP API (pe'ah, courtyard, chatzer, kodesh) |
shoresh-engine |
Haskell binary, spawned by vav-pipeline as an Erlang Port (staged into the pod by the shoresh-engine-install init container — NOT a sidecar container; a Port is a child process of the BEAM and cannot cross a container boundary) |
Root activation, te'amim parsing, gematria |
talmudic-engine |
SWI-Prolog (sidecar via Unix socket) | 613 mitzvot, 13 middot, kushya generation, teiku |
korban-processor |
Python 3.12 (sidecar) | Offering protocol, eish zarah validation |
All four run in the same pod. vav-pipeline is the main container; talmudic-engine and korban-processor are sidecars; shoresh-engine runs inside vav-pipeline as an Erlang Port child process, staged in by an init container.
External dependencies
| Dependency | Purpose | Contract |
|---|---|---|
| Managed PostgreSQL 17+ | L3 Oral Tradition (append-only) | DATABASE_URL env var. Requires SSL. Role with SELECT, INSERT only — UPDATE, DELETE revoked (see migration). |
| (none — in the images) | L1 Torah filesystem (~29 MB) | Baked into every image at /mnt/torah, owned by root with no write bit. No volume. The pipeline hashes the tree at startup and every ten minutes; no cycle runs on a scroll that does not match the pinned hash. |
| Block-storage PersistentVolume | Manna provision and its ledger (read-write, 1 GiB) | Mount at /var/lib/bikoret/manna. Operator writes today.json daily; the vessel writes ledger.json. |
| Ingress controller + TLS cert | Public HTTPS access | Cert-manager with Let's Encrypt HTTP-01 is the reference setup. |
| Container registry | Image distribution | Any registry that supports Docker v2 protocol. |
Kubernetes manifests
Kept in deploy/k8s/:
namespace.yaml— the namespaceconfigmap.yaml— non-secret configurationsecrets.yaml— template only; operator fills inDATABASE_URLl1-volume.yaml— PV and PVC for Torah filesystem (vestigial: L1 is in the images; do not apply)manna-volume.yaml— PVC for provision filedeployment.yaml— the pod with 3 containers + 2 init containers (shoresh-engine-install,migrate). Four images are still built and pushed; shoresh-engine ships a binary, not a running container.service.yaml— ClusterIP and external LoadBalancergitea-mcp-deployment.yaml— separate MCP server for Gitea connector (optional)gitea-mcp-ingress.yaml— TLS ingress for the MCP servergitea-mcp-secret.yaml— template for Gitea PATcert-manager-issuer.yaml— Let's Encrypt ClusterIssuer
Containers
Four Dockerfiles in deploy/docker/:
Dockerfile.vav_pipeline— multi-stage Elixir 1.16.1 / OTP 26.2.1 releaseDockerfile.shoresh_engine— multi-stage Haskell GHC 9.6.4 / CabalDockerfile.talmudic_engine— SWI-Prolog 9.2.2 with socket serverDockerfile.korban_processor— Python 3.12.2 slim
Configuration surface
The system reads three things from its environment:
- L1 Torah — in the image at
$L1_MOUNT_POINT, not writable by the service user. Read and hashed at startup and every ten minutes; every cycle is gated on the last reading. - Manna provision — JSON file at
$MANNA_PROVISION_FILE, written by the kohen/treasurer. - L3 database — connection string in
$DATABASE_URL.
Nothing else is configurable. The system obeys Torah (L1 + calendar) for governance and the provision file for resources.
Seven-day inauguration
Before serving users, run the shiv'at y'mei milu'im sequence documented in KOHEN.md. Each day validates a specific layer. Partial inauguration is no inauguration.