Files
Scott KarpandClaude Fable 5.1 c0d0555aed the name: Bikoret — code, contracts, images
Headers X-Bikoret-Key / -Rebuke / -Verdict / -Bedikah; the `bikoret`
object and the "— bikoret …" fringe on a gate reply; environment
variables BIKORET_*; the image user and paths (/home/bikoret,
/tmp/bikoret, /var/lib/bikoret/manna, /etc/bikoret/secrets,
/opt/bikoret/spec); the tmp-bikoret pod volume; local databases
bikoret_dev/_test. Kubernetes resource names, the shorashim_app role and
the domain are unchanged (Tamid §1.1, "the names that still carry the
old word"). Doorpost c963c4fe…. Elixir 604/0, L3 10/0, korban 295,
Prolog bedikah 44/44. Gitea repo renamed heaviness510/bikoret (old URL
redirects).

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-13 22: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/bikoret/spec",
manna_provision_file: "/var/lib/bikoret/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