Scott KarpandClaude Opus 4.6
c67672777b
Three connections built and tested: - Haskell Shoresh Engine via Erlang Port (JSON lines over stdin/stdout) - Prolog Talmudic Engine via Unix domain socket (JSON over /tmp/shorashim/talmudic.sock) - Erlang Sanhedrin via native BEAM calls New: Server.hs (JSON-line server loop), json_bridge.pl + socket_server.pl (Prolog socket interface), ShoreshEnginePort + TalmudicEngineSocket + SanhedrinClient (Elixir GenServer wrappers). BereishitCycle now routes unresolved cases through Talmudic Engine and Sanhedrin. All connections gracefully degrade — pipeline falls back to L1 data when engines unavailable. 46 Elixir tests, 33 Haskell tests, 57 Prolog tests — 0 failures. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
23 lines
841 B
Elixir
23 lines
841 B
Elixir
import Config
|
|
|
|
# L1 mount point — relative path for dev, absolute for production
|
|
# Construction spec §4.4: l1_mount_point: "/mnt/torah"
|
|
config :vav_pipeline,
|
|
# Dev: relative to project root (run from shorashim/)
|
|
l1_mount_point: "l1",
|
|
# Manna provision file
|
|
manna_provision_file: "var/manna/today.json",
|
|
# Shabbat check interval (1 minute)
|
|
cycle_boundary_check_interval_ms: 60_000,
|
|
# ShemaContext: no caching — always read fresh
|
|
shema_context_cache_ttl_ms: 0,
|
|
# Step 14 — Component connection config
|
|
# Shoresh Engine (Haskell) — binary path for Erlang Port
|
|
shoresh_engine_binary: "shoresh-engine",
|
|
shoresh_engine_cwd: nil,
|
|
# Talmudic Engine (Prolog) — Unix domain socket path
|
|
talmudic_socket_path: "/tmp/shorashim/talmudic.sock"
|
|
|
|
# Import environment specific config
|
|
import_config "#{config_env()}.exs"
|