Step 14: Connect components — chamishim karsay zahav
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>
This commit is contained in:
1 parent
f8f70c77e5
commit
c67672777b
18 files changed
+1435
-121
No files matched your search
@@ -21,7 +21,8 @@ defmodule VavPipeline.MixProject do
|
||||
# Construction spec §1.5 — exact version pins
|
||||
defp deps do
|
||||
[
|
||||
{:jason, "~> 1.4.1"}
|
||||
{:jason, "~> 1.4.1"},
|
||||
{:sanhedrin, path: "../sanhedrin", manager: :rebar3}
|
||||
]
|
||||
end
|
||||
end
|
||||
Reference in new issue
Block a user