0 Fork 0

Files

T

Scott KarpandClaude Fable 5.1 c0d0555aed the name: Bikoret — code, contracts, images

Headers X-Bikoret-Key / -Rebuke / -Verdict / -Bedikah; the `bikoret`
object and the "— bikoret …" fringe on a gate reply; environment
variables BIKORET_*; the image user and paths (/home/bikoret,
/tmp/bikoret, /var/lib/bikoret/manna, /etc/bikoret/secrets,
/opt/bikoret/spec); the tmp-bikoret pod volume; local databases
bikoret_dev/_test. Kubernetes resource names, the shorashim_app role and
the domain are unchanged (Tamid §1.1, "the names that still carry the
old word"). Doorpost c963c4fe…. Elixir 604/0, L3 10/0, korban 295,
Prolog bedikah 44/44. Gitea repo renamed heaviness510/bikoret (old URL
redirects).

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

2026-10-13 22:13:36 +00:00

2.2 KiB

Raw Blame History

Training Pairs — Provenance and Curation

Each .jsonl file in this directory is a list of training records, one per line. Records have the schema:

{
  "interpretation": "...",     // String. The proposed reading.
  "kushya": "...",             // String. The challenge, expressed as a question.
  "torah_refs": ["Book Ch:V"], // Array of verse references the kushya cites.
  "type": "..."                // One of the kushya types — see below.
}

Kushya Types

Type	What it tests
`scope_narrowing`	Interpretation may be narrower than the verse
`scope_application`	Boundary cases the verse does not directly cover
`internal_tension`	The verse contradicts itself under this reading
`exception_test`	A general rule has known exceptions to reconcile
`harmonization`	Two verses both bear on the question and must coexist
`edge_case`	An unusual case the principle alone does not resolve
`rabbinic_constraint`	Mishnah/Gemara modifies the simple reading
`method_question`	The hermeneutic method itself is in question
`subject_identification`	The grammatical subject of the law is ambiguous

Files

seed_pairs.jsonl — 10 hand-curated bootstrap pairs covering all types

Production Curation

For a real fine-tuning run, several thousand pairs should be assembled from primary rabbinic sources. Suggested process:

Bavli kushyot extraction — script over Sefaria Tanakh+Talmud API to pull mai k'shia / kashya / similar markers; pair with the surrounding interpretation
Rishonim challenges — Tosafot's i kashya openings, Ramban's challenges to Rashi
Hand validation — every pair reviewed against the four kushya requirements (specific Torah passage, identified weakness, question form, non-trivial)
Type tagging — each pair labeled with one of the types above for stratified training/eval splits

License

Pairs derived from rabbinic sources retain whatever license those sources carry. The hand-curated seed pairs in this directory are MIT, like the rest of bikoret.

2.2 KiB Raw Blame History