Files
bikoret/korban_processor
Scott KarpandClaude Opus 4.7 af2a3949cf korban_processor: name the kabbalah + holachah compression in zerikah.py
Pass 2 finding B: the full Temple sacrifice protocol has FIVE stages
between semichah and haktarah —

  1. semichah    owner identifies with the offering
  2. shechitah   ritual slaughter
  3. KABBALAH    kohen RECEIVES the blood in a vessel
  4. HOLACHAH    kohen CARRIES the blood to the altar
  5. ZERIKAH     kohen SPRINKLES the blood on the altar
  6. haktarah    burning of permitted portions

The pipeline implements only four modules. Stages 3 and 4 are folded
silently into zerikah(). The compression is acceptable —
kabbalah/holachah have no analog of physical blood movement in
software — but UNDOCUMENTED compression is itself a small gilui_arayot
(severing the distinction between three distinct ritual acts).

Now named explicitly in the module docstring with:
  - what the three stages are
  - why folding is acceptable here (the analogs are atomic in software)
  - what the analogs ARE in code (zerikah's return value = the
    receiving vessel; the function-call boundary to haktarah() in
    external_offering.py = carrying to the altar)
  - what to do if a future architecture requires distinguishing them
    (split this module into three; do not add the distinction
    elsewhere)

A future reader now sees the compression instead of inferring that
the pipeline silently dropped two ritual acts.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-26 12:01:41 -04:00
..
2026-02-26 14:02:34 -05:00