Files
bikoret/vav_pipeline/config/prod.exs
T
Scott KarpandClaude Fable 5.1 5e325d36cc the second scroll: the mesorah snapshot, pinned and read (bishe'arecha step 6)
Devarim 17:18 — the king writes his copy from before the priests, not from
memory. scripts/build_mesorah.py takes one open-licence version per work
per language from the Sefaria export (bucket sefaria-export, catalogue of
2026-10-02; Public Domain / CC0 / CC-BY / CC-BY-SA only, checked in every
file; no CC-BY-NC — the Bavli is Wikisource's) and lays it down beside
L1: mesorah/works/<slug>/{he,en}.json, index.json, integrity.sha256,
build_report.json. 128 works (Rashi, Onkelos, Ramban, Ibn Ezra, Sforno
on the Torah; all of Mishnah; 37 Bavli tractates; Bereshit and Shemot
Rabbah, Sifrei, Tanchuma), 256 files, 44.9 MiB, tree hash 7d5b3a6c…
computed as L1's (sorted relative path, then bytes; the two post-hash
files excluded). What is out, and why (licence), is in Terumah §E5.

Read, never fetched: korban_processor/mesorah.py finds citations as
written (Rashi on Devarim 6:5, Berakhot 2a, Mishnah Berakhot 1:1,
Bereshit Rabbah 1:1, Sifrei Devarim 32, Tanchuma Bereshit 1 …), resolves
each against the snapshot (complex works through their unnamed node,
Tanchuma by parashah), lists them as examination.mesorah_references, and
makes every passage found a given source for that examination — so a
claim about Rashi anchors in Rashi or does not. The Vav Pipeline couples
coupled(reference(R), mesorah(Work, [Address])) or not_in_mesorah; the
engine accepts mesorah/2 as a terminal and not_in_mesorah is Form 4.
VavPipeline.Mesorah pins the hash, re-reads the tree at startup and every
ten minutes, and /kodesh/health carries mesorah_hash. Mounted read-only at
/mnt/mesorah in the vav-pipeline and korban-processor images. L3
bedikot.mesorah (migration 20261013000002).

Also: the 1-in-12 Day6 serving failure of 2026-10-04 reproduced with seed
446116 — HaltMonitorTest left the system halted; it now resolves on exit
and the Day6 setup is defensive. Construction §3.11, Terumah §E5, Tamid
§1.1, bishearecha §IV, KOHEN, AGENTS. Doorpost 0638d4eb…. Elixir 604/0
(seeds 835592 and 446116), korban 294/1 skipped, Prolog bedikah 44/44,
L3 10/0.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-13 19:13:36 +00:00

30 lines
1.2 KiB
Elixir

import Config
config :logger, level: :info
# Production defaults — Construction spec §4.4
# Env-var overrides are in runtime.exs (evaluated at boot, not compile)
config :vav_pipeline,
l1_mount_point: "/mnt/torah",
mesorah_mount_point: "/mnt/mesorah",
# Doorpost repo root — Devarim 11:20, ukhtavtam al mezuzot beitecha.
# The category-grade specification files are COPYed into the image
# (see deploy/docker/Dockerfile.vav_pipeline, INSCRIBE THE DOORPOST)
# so a running pod can verify its own corporate-text identity. Without
# this, @repo_root falls back to a path that only exists on the build
# host, VavPipeline.Doorpost.verify_identity/0 returns
# SPEC_INTEGRITY_FAILED on every boot, and the chatzotzrot that fires
# is a false alarm — which is worse than no witness at all.
# Read at COMPILE time via Application.compile_env/3.
doorpost_repo_root: "/opt/shorashim/spec",
manna_provision_file: "/var/lib/shorashim/manna/today.json",
cycle_boundary_check_interval_ms: 60_000,
shema_context_cache_ttl_ms: 0,
http_port: 4000
# L3 — Production PostgreSQL
# DATABASE_URL is set at runtime via runtime.exs
# These are compile-time defaults only
config :vav_pipeline, VavPipeline.Repo,
pool_size: 20