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>
29 lines
532 B
Elixir
29 lines
532 B
Elixir
defmodule VavPipeline.MixProject do
|
|
use Mix.Project
|
|
|
|
def project do
|
|
[
|
|
app: :vav_pipeline,
|
|
version: "0.1.0",
|
|
elixir: "~> 1.16.1",
|
|
start_permanent: Mix.env() == :prod,
|
|
deps: deps()
|
|
]
|
|
end
|
|
|
|
def application do
|
|
[
|
|
extra_applications: [:logger, :crypto],
|
|
mod: {VavPipeline.Application, []}
|
|
]
|
|
end
|
|
|
|
# Construction spec §1.5 — exact version pins
|
|
defp deps do
|
|
[
|
|
{:jason, "~> 1.4.1"},
|
|
{:sanhedrin, path: "../sanhedrin", manager: :rebar3}
|
|
]
|
|
end
|
|
end
|