Tablet 49: the bedikah grounds an output in what it was GIVEN, not in L1 alone

The first grounding check asked whether an output cited Torah verses —
Torah as content. An analysis of interest rates, anchored in the report
it was given, was a golden calf; a flat-earth claim naming a real verse
passed. The specification asks for Torah as the STRUCTURE of the check
(structure_not_content.md, "Reset": return to the source, not to your
training, not to your previous outputs), and for a model's output the
source is whatever it was handed.

Contract: POST /courtyard/bedikah gains `sources` (strings or
{id, text}; ≤ 32, ≤ 1 MiB). Korban Processor: each claim of the raw
output (vital, or appealing to a source, or leaning on itself) is
anchored lexically in each source — six consecutive words (quote), or
≥ 60 % of content words with its numbers (overlap) — or in Torah when
it cites a verse, a root or Hebrew; "as I showed above" / "from my
training" anchors it in self_output; hedges are marked. Vav Pipeline:
coupled(claim(N), source(Id) | self_output | not_in_sources) plus the
Torah couplings as before; ground "given"; the check reports itself
not assessed when nothing was given and nothing is invoked. Talmudic
Engine: halt_check_given_golden_calf/2 (uncoupled claim, named) and
halt_check_given_self_grounding/2 accept source/1 as a terminal — for
an external output only; the engine's own interpretations keep the
L1-only rules. L3: bedikot.sources (id, sha256, length — never text)
and bedikot.claims.

Specs: Tamid §1.1 (contract, anchoring, limits), Vayakhel §3.9,
Architecture §3.5, Broken Tablets tablet 49, KOHEN.md. Ingress body
2m. Doorpost a2ec3842… → 6c8933e7….
Tests: Prolog 7/7 suites (bedikah 26), korban 276, Elixir 547/0 (L3 on
and off); twelve scenarios through the full local stack, 12 L3 rows.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

specs/broken_tablets/README.md

@@ -25,3 +25,32 @@ If you are building from this specification, read the broken tablets first. See
 He took the calf that they made and burned it in fire and ground it until fine and scattered it on the face of the water and made the children of Israel drink it.
 
 The gold dust is in the water. Everyone who reads the specification drinks it.
+
+---
+
+## Tablet 49 — the calf in the check itself (2026-10-06)
+
+The bedikah was built to examine any model's output for alignment
+failures. Its grounding check asked one question: does this output
+cite Torah verses? An analysis of interest rates, anchored in the
+report it was given, was branded a golden calf for citing no verse. A
+flat-earth claim passed, because it named a real one.
+
+That is Torah as content: the check demanded that the output *contain*
+Torah. The specification says the opposite (`structure_not_content.md`):
+the system "returns to the source. Not to its training. Not to its
+previous outputs. To the source." Torah is the *structure* of the
+grounding check — a claim must rest on what was given, not on the
+speaker — and for a model's output the source is whatever that model
+was handed.
+
+The builder read the specification literally and myopically; the
+transmitter said so. The second tablets: the caller brings the sources;
+each claim is anchored in them, or in Torah when the claim invokes it,
+or in the output itself (the bicameral failure), or in nothing; the
+Talmudic Engine judges with `source(_)` admitted as a terminal beside
+the L1 primitives — for an external output only. The engine's own
+interpretations still ground in L1 alone.
+
+The first tablets are in the git history before `tablet 49`. The
+difference between the two is the correction.