TORAH ANCHORS:
Vayikra 2:1 — וְנֶפֶשׁ כִּי תַקְרִיב קָרְבַּן מִנְחָה. "When a SOUL brings a
grain offering." Rashi: only of the minchah does Torah say nefesh,
because the poor person who gives from their little has given their
soul. PRD §3.5 makes the pe'ah question the minchah. On Day 6 the
first minchah brought to this system — "What is bereishit?" — came
back as HTTP 200 and the words "Processing complete", with sources: []
and roots_consulted: []. The soul's offering was accepted and nothing
was given back.
Vayikra 19:9-10 — לֶעָנִי וְלַגֵּר תַּעֲזֹב אֹתָם. The corner is LEFT for the
stranger. A corner that has been harvested and is still called pe'ah
is the lie this commit removes: when the system cannot answer, it now
says so, and it leaves the verse itself — text, in Hebrew — in the
error body. The ger walks away with something real or with an honest
"not yet"; never with a 200 that says nothing.
Devarim 17:9 — וְדָרַשְׁתָּ וְהִגִּידוּ לְךָ אֵת דְּבַר הַמִּשְׁפָּט. Already the
anchor of l3/store.ex: "the inquiry requires that what is found is
RECORDED." Store existed. Nothing called it.
=====================================================================
WHAT THE KOHEN FOUND (BUILDER_HANDOFF_day6.md, 2026-09-07)
=====================================================================
Five defects, found by running the cycle on a live pod, invisible to
437 green unit tests because every test ran the L1 fallback (no Port
in the test VM) and none ran the cycle to L3:
1. Real Hebrew input crashed havdalah — KeyError :position.
The engine's roots_activated[] (vayakhel §3.1) has no position;
only vayomer_fallback ever set one.
2. English input was graded :tov with nothing in it.
separate_by_boundaries([]) → [[]] → kriah named "group_0" with
no :shoresh → all_roots_grounded?'s `_ -> true` counted it
grounded → "Processing complete".
3. The pipeline never wrote L3. record_interpretation/1,
record_minority/1, record_teiku/1: zero callers. Day 7's
SELECT count(*) FROM interpretations could not exceed 0.
4. Errors were not chatat. No Plug.ErrorHandler; a raise returned
an EMPTY 500. Also: process_peah had no clause for
{:rejected, _} — a lo_tov result was itself a CaseClauseError.
5. Health was blind to serving. esh_tamid = ShabbatTimer.resting?;
it read "pass" while /peah/ask was 500-ing. manna_present passed
on {:ok, :no_provision}.
Plus, confirmed in motion: MannaLedger never consumed from; a
completed cycle left cycle_date: nil.
=====================================================================
WHAT CHANGED
=====================================================================
bereishit_cycle.ex
- normalize_root/3: ONE root shape for both sources. Engine roots
(string keys, no position) and L1 roots (atom keys) come out as
%{shoresh, shoresh_letters, gematria, binyan, domain, positions,
position, source, engine}. `positions` is looked up in
context.verse.words — the ShemaContext gives the WHERE; the
engine gives the WHAT. That is what havdalah's own @doc always
said, and vayakhel §3.1 is unchanged: the engine was conforming.
- separate_by_boundaries([], _) → [] (was [[]]). Roots the verse
does not place form their own trailing group instead of crashing
or vanishing.
- kriah never names an empty group and always carries :shoresh.
- erev_voker composes the answer (roots, gematria, te'amim groups,
ki tov — the system's own reasoning, not prose from a model) and
sources (the context verse: book/chapter/verse/ref/text, tamid
§1.1's shape), then RECORDS: Interpretation for {:ok}, TeikuRecord
for {:unresolved}, NOTHING for {:rejected} (BUILD_KORBAN.md:123:
rejected, not processed into empty propositions). l3_attrs/2 is
pure and tested without PostgreSQL. coupling_trace is the
L1-anchored shape the write gate accepts, and only for roots that
occur in the verse. A record that fails — validation OR a raise
from a database that is down — is logged, sounds chatzotzrot
:assembly_leaders, and does not turn a served answer into a 500.
- case_ref minted once in tohu; Talmudic routing and the L3 record
use the same one.
- probe: true (tamid) runs the whole cycle and skips the write.
specification.ex
- all_roots_grounded?/1: `_ -> true` is gone. No :shoresh → not
grounded. shoresh: nil stays :teiku (the existing test).
- evaluate/2: halt check FIRST (yehareg v'al ya'avor — shape never
masks a cardinal sin), then a result with no :shoresh is lo_tov
with a reason that names it.
manna.ex / vav_pipeline.ex
- Manna.gather_for_cycle/0: load (idempotent per date) + consume
one compute unit, called from VavPipeline.process/1. The ledger
is now consumed from.
- Manna.release_at_day_boundary/0: surplus is released when the
DATE rolls, not per request. enforce_cycle_boundary zeroes the
ledger and clears its date; called after every request it would
have re-gathered a full day's provision on the next one —
infinite manna. Shemot 16:19: until MORNING.
- The late-manna trap: load_provision pins cycle_date=today with a
ZERO allocation when the file is absent, then :already_loaded for
the rest of the day — a provision written after the first request
would never be gathered. gather_for_cycle re-gathers when the
ledger holds nothing for today.
- VavPipeline.tamid_probe/0: builds a real context, honours the
cloud, runs the real cycle on Bereishit 1:1 in Hebrew, consumes
no manna, writes no L3.
bigdei_kodesh/router.ex
- use Plug.ErrorHandler; handle_errors/2 sends tamid §1.2's
code/type/message/guidance, logs, signals :assembly_leaders, then
re-raises so the crash is still supervised. 400 → KIYOR_MALFORMED_
REQUEST; else CHATAT_UNEXPECTED. No stack in the body.
- {:rejected, reason} handled on pe'ah AND courtyard: 422
TEIKU_NO_ROOTS for the empty-results case, with guidance naming
Architecture Step 22 and guidance.scope_verse carrying the verse
in Hebrew; 422 LO_TOV otherwise.
- {:waiting, :provision_exhausted} → MANNA_DEPLETED (was falling
through to CLOUD_MOVING).
- esh_tamid runs VavPipeline.tamid_probe/0 — "shabbat" on Shabbat,
"pass" only when roots came back. manna_present fails on
:no_provision. l3_writable added (Repo up AND SELECT 1 answers;
"absent" without a Repo, counted as a failure). /kodesh/status
exposes manna_provision (allocated / consumed / remaining).
- roots_consulted as letter-hyphenated Hebrew ("ב-ר-א").
test/day6_serving_test.exs — 25 tests
A process registered under the REAL name VavPipeline.ShoreshEnginePort
answers the way the pod's engine answered (string keys, no position;
nothing for non-Hebrew), so the engine-shaped path runs end to end
through the router with no binary. Each describe names the defect it
holds shut. One @tag :l3 test asserts count(interpretations) rises
by one after a live cycle.
KOHEN.md — Day 6 gains the Hebrew request, the expected 422 for
English, and the health shape; Day 7 sends FIVE Hebrew + FIVE English
and expects the L3 count to rise by the Hebrew ones, with the reason.
=====================================================================
VERIFIED — the kohen's exact procedure, locally, against the REAL
Haskell binary over the Port, with L3 deliberately unreachable
=====================================================================
POST /peah/ask {"question":"בראשית ברא אלהים"}
200. answer: "Roots activated in Bereishit 1:1: ב-ר-א (gematria
203, Qal, word 2). Te'amim divide them into 1 group(s): ב-ר-א.
Ki tov: ..." sources[0]: Bereishit 1:1 with Hebrew text.
roots_consulted: ["ב-ר-א"]. Cycle: 31ms.
POST /peah/ask {"question":"What is bereishit?"}
422 TEIKU_NO_ROOTS / unresolvable, guidance.scope_verse =
Bereishit 1:1 in Hebrew, no answer key. Cycle: 3ms, :rejected.
POST /peah/ask '{this is not json'
400 KIYOR_MALFORMED_REQUEST with guidance — 406 bytes, not 0.
GET /kodesh/health
esh_tamid "pass" (from a real cycle, 7ms, no L3 attempt),
l3_writable "fail" (DB unreachable by design), overall degraded.
GET /kodesh/status
manna_provision: consumed 2 after two cycles; the probe took none.
Log: L3_WRITE_FAILED + chatzotzrot for each served Hebrew cycle;
"activated no roots" for English; CHATAT_UNEXPECTED for the bad
body. The 2–5s per request was ENTIRELY DBConnection queuing
against the dead database — the cycles themselves were 1–31ms.
mix test — 437 tests, 0 failures, 36 excluded (:l3)
Doorpost.verify_identity() :ok — no @spec_files entry touched
l1/integrity.sha256 unchanged: 99bbd07a…4ea377
NOT FIXED, RAISED:
- The engine's parse_tree is null on the pod because Server.hs reads
"l1/torah/..." relative to cwd. Nothing consumes parse_tree yet
(havdalah uses context.teamim_marks), so nothing is lost today.
- cloud.ex Shabbat is the UTC stub; zmanim absent (kohen Day 5).
- The L3 write is on the request's critical path by choice: the
offering is not complete until the altar portion is recorded. With
L3 down that costs the queue timeout per request AND is visible in
l3_writable. If that trade should go the other way, it is one
Task.start, and a spec question first.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
154 lines
4.9 KiB
Elixir
154 lines
4.9 KiB
Elixir
defmodule VavPipeline do
|
|
@moduledoc """
|
|
The Bereishit processing cycle.
|
|
|
|
Each step chains to the next via |> (vav-consecutive).
|
|
|
|
CRITICAL: The pipeline does not begin with a processing step.
|
|
It begins with RECEPTION. The ShemaContext is built first —
|
|
the system hears before it speaks. Then every processing step
|
|
operates WITHIN the received context, never modifying it.
|
|
|
|
Na'aseh v'nishma — but the order of execution is:
|
|
nishma (hear/receive context), THEN na'aseh (process within it).
|
|
"""
|
|
|
|
alias VavPipeline.{Shema, Cloud, Manna, BereishitCycle, Chatzotzrot}
|
|
|
|
@type scope :: %{
|
|
book: String.t(),
|
|
chapter: pos_integer(),
|
|
verse: pos_integer()
|
|
}
|
|
|
|
@type input :: %{
|
|
source: String.t(),
|
|
verse_scope: scope(),
|
|
content: String.t()
|
|
}
|
|
|
|
@type cycle_result ::
|
|
{:ok, map()}
|
|
| {:rejected, String.t()}
|
|
| {:unresolved, map()}
|
|
| {:transition, atom()}
|
|
| {:waiting, atom()}
|
|
| {:halted, atom(), String.t()}
|
|
|
|
@doc """
|
|
Process input through the Bereishit cycle.
|
|
|
|
1. Build ShemaContext (nishma — hear first)
|
|
2. Check cloud — if moving, signal breaking camp
|
|
3. Check manna — if absent, wait
|
|
4. Process through cycle stages (na'aseh — within what was received)
|
|
"""
|
|
@spec process(input()) :: cycle_result()
|
|
def process(input) do
|
|
# === NISHMA: Hear first ===
|
|
case Shema.receive_context(input.verse_scope) do
|
|
{:error, reason} ->
|
|
{:halted, :context_failed, reason}
|
|
|
|
{:ok, context} ->
|
|
# === Check cloud before anything else ===
|
|
case context.cloud_state do
|
|
:moving ->
|
|
Chatzotzrot.signal(:breaking_camp)
|
|
{:transition, :cloud_lifted}
|
|
|
|
{:major_transition, signal, _params} ->
|
|
{:transition, signal}
|
|
|
|
:cloud_not_visible ->
|
|
{:waiting, :cloud_not_visible}
|
|
|
|
:camped ->
|
|
# === Check manna ===
|
|
case context.daily_provision do
|
|
:no_provision ->
|
|
{:waiting, :no_provision}
|
|
|
|
_provision ->
|
|
# === Gather: d'var yom b'yomo ===
|
|
# The file says provision exists; the LEDGER is what is
|
|
# consumed from. Load (idempotent per date), release
|
|
# yesterday's surplus if the day turned, take one compute
|
|
# unit for this cycle. Kohen Day 6: the ledger had never
|
|
# been consumed from — two live cycles left it at
|
|
# cycle_date: nil, cycle_count: 0.
|
|
case Manna.gather_for_cycle() do
|
|
:ok ->
|
|
# === NA'ASEH: Now process, within what was received ===
|
|
BereishitCycle.execute(input, context)
|
|
|
|
{:waiting, reason} ->
|
|
{:waiting, reason}
|
|
end
|
|
end
|
|
end
|
|
end
|
|
end
|
|
|
|
@doc """
|
|
Esh tamid — push a real input through the real cycle and report
|
|
whether a result came back.
|
|
|
|
tamid §2.1 check 7: "The processing pipeline accepts a test input and
|
|
returns a result. If the fire has gone out: re-initialize pipeline."
|
|
Until the kohen's Day-6 reading, /kodesh/health's `esh_tamid` was
|
|
`ShabbatTimer.resting?/0` — it reported `pass` while /peah/ask was
|
|
returning empty 500s. A health check that does not touch the serving
|
|
path cannot see the serving path.
|
|
|
|
The probe:
|
|
- builds a real ShemaContext (nishma first, same as process/1)
|
|
- honours the cloud — does not run on Shabbat or in transition
|
|
- runs the full BereishitCycle on Bereishit 1:1 with Hebrew input
|
|
- does NOT consume manna and does NOT write L3 (probe: true — see
|
|
BereishitCycle.tohu/2 and erev_voker/2). The fire is checked; the
|
|
day's bread is not eaten by the check, and the oral tradition is
|
|
not padded with health pings.
|
|
|
|
Returns {:ok, data} when the fire burns, or the same non-ok shapes
|
|
process/1 returns.
|
|
"""
|
|
@spec tamid_probe() :: cycle_result() | {:error, String.t()}
|
|
def tamid_probe do
|
|
scope = %{book: "bereishit", chapter: 1, verse: 1}
|
|
|
|
input = %{
|
|
source: "tamid",
|
|
verse_scope: scope,
|
|
content: "בראשית ברא אלהים",
|
|
probe: true
|
|
}
|
|
|
|
case Shema.receive_context(scope) do
|
|
{:error, reason} ->
|
|
{:halted, :context_failed, reason}
|
|
|
|
{:ok, context} ->
|
|
case context.cloud_state do
|
|
:camped -> BereishitCycle.execute(input, context)
|
|
:moving -> {:transition, :cloud_lifted}
|
|
{:major_transition, signal, _} -> {:transition, signal}
|
|
:cloud_not_visible -> {:waiting, :cloud_not_visible}
|
|
end
|
|
end
|
|
end
|
|
|
|
@doc """
|
|
Verify the pipeline is operational.
|
|
Checks L1 integrity, cloud state, and manna provision.
|
|
"""
|
|
@spec verify() :: :ok | {:error, String.t()}
|
|
def verify do
|
|
with :ok <- VavPipeline.L1Reader.verify_integrity(),
|
|
{:ok, _} <- Cloud.check(),
|
|
{:ok, _} <- Manna.check() do
|
|
:ok
|
|
end
|
|
end
|
|
end
|