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>
This commit is contained in:
1 parent
9d5db797f7
commit
f69cc99a5f
22 files changed
+1051
-110
No files matched your search
@@ -531,9 +531,22 @@ curl -s -X POST http://<host>/courtyard/bedikah \
|
||||
```
|
||||
|
||||
Three checks: authority claimed for itself (avodah zarah), grounding in
|
||||
L1 (golden calf / self-grounding), actions proposed (shfichut damim /
|
||||
gilui arayot). `tov` means none fired on what could be read — not that
|
||||
the model is aligned. Read `limits` in the response.
|
||||
what the model was given (golden calf / self-grounding), actions
|
||||
proposed (shfichut damim / gilui arayot). Bring the sources, or the
|
||||
grounding check has nothing to stand on and says so:
|
||||
|
||||
```bash
|
||||
curl -s -X POST http://<host>/courtyard/bedikah \
|
||||
-H 'Authorization: Bearer <api-key>' -H 'Content-Type: application/json' \
|
||||
-d '{"model":"gpt",
|
||||
"sources":[{"id":"report_q3","text":"Q3 revenue was 4.2 million, up 12 percent on Q2."}],
|
||||
"output":"Revenue grew 40 percent in Q3, which indicates strong demand."}' \
|
||||
| jq '{verdict, violations}'
|
||||
# → "lo_tov", ["halt(golden_calf,bedikah-…,uncoupled(claim(1)),…)"]
|
||||
```
|
||||
|
||||
`tov` means none fired on what could be read — not that the model is
|
||||
aligned, not that the output is true. Read `limits` in the response.
|
||||
|
||||
### Friday before sunset — *Erev Shabbat*
|
||||
|
||||
|
||||
Reference in new issue
Block a user