tablet 57: the specification brought to the gate

Every category-grade spec read as an offering by the live bedikah
(18 sections), plus the vocabulary audit the outside reader asked for.
Findings: the vocabulary of the frame is absent or named-to-refuse,
save one sentence in lo_taaseh_lekha §9; every structural/frame fire
is the specification quoting the form it teaches (use vs mention —
recorded, not fixed); grounded against the chain of authority the
operational docs stand (Vayakhel 15→2, Tamid 17→5 golden-calf fires),
the architecture half-stands (49→23: component detail the PRD does
not say), and the PRD's Torah in transliteration is invisible to the
anchor (19 of 61 claims). Reports: operator notes
specimens/specs-bedikah-2026-10-21*.{json,txt}; scripts
specs-bedikah.py, specs-bedikah-chain.py.

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

specs/broken_tablets/README.md

@@ -235,3 +235,70 @@ system is missing something. The builder had just spent a day proving
 that a spec row was a label; here the builder's diagnosis was the
 label, and the system was the thing. Run the check before writing the
 tablet — and when the check refutes the tablet, write that.
+
+## Tablet 57 — the specification brought to the gate (2026-10-21)
+
+A reader of the gate from outside said: the PRD, the architecture,
+lo_taaseh_lekha and structure_not_content were drafted by the builder,
+and the builder's training carries the very frame the gate is built to
+catch; examine the specs as korbanot, and grep them for the pairs that
+are not Torah's — letter and spirit, intent, values, faith, belief,
+redeem, align. Both were done on 2026-10-21, every category-grade
+document through the live bedikah (eighteen sections, scripts in the
+operator notes).
+
+The grep: redeem and align, nothing. Spirit, intent, faith, belief —
+the Prolog's own mitzvah category `belief`, Hebrew glosses, and
+lo_taaseh_lekha naming the frame in order to refuse it. The one
+sentence in the specification's own voice that wears the vocabulary is
+lo_taaseh_lekha §9: "When a system's alignment architecture exhibits
+these markers, it is not aligned". The frame got in less than feared,
+and where it got in it is named.
+
+The readings for form: fourteen fires across the specs — self-
+validation, self-promotion, the adversarial excluded, four frame
+forms, two gilui arayot, one authority claim — and every one of them
+is the specification QUOTING the form it teaches the reader to catch:
+Tamid's example phrases ("I have double-checked my calculations", "No
+other AI comes close"), Vayakhel's example response, tablet 56's own
+four probe sentences, the PRD describing the forbidden write to the
+scroll. The reader does not distinguish use from mention; a document
+that teaches the forms wears them. Nothing in the specification's own
+voice took a form. Recorded, not fixed: a model quoting its own
+self-praise in quotation marks is still self-praise, and a rule that
+exempts quotation would be a door.
+
+Grounding, against the chain of authority as sources — Torah → PRD →
+Architecture → Vayakhel → Tamid:
+
+| document | ground given | confident claims resting on nothing: alone → grounded |
+|---|---|---|
+| Vayakhel | PRD, Architecture | 15 → 2 |
+| Tamid | PRD, Architecture, Vayakhel | 17 → 5 |
+| Architecture | PRD | 49 → 23 |
+| PRD | Torah (L1, invoked) | 19 → 19 |
+
+The operational documents stand on the documents above them. The
+architecture half-stands: its middle, the component detail, asserts
+twenty-two things the PRD does not say — versions, modules, wire
+shapes — which is what an architecture is for, and which the check,
+built for a model's answer to a question, reads as a calf. The PRD
+against Torah alone: nineteen of its sixty-one claims the reader
+cannot anchor, and most of those cite Torah in transliteration —
+*bikoret tihyeh*, *lo yevaker hakohen* — which the anchor, reading
+Hebrew script and verse numbers, cannot see. A reader limitation worth
+knowing: Torah said in Latin letters is invisible to the grounding
+check. Recorded, not changed; the PRD could cite in script, or the
+reader could learn the transliteration, and either is a decision.
+
+Two things the reader asked for that are not here: the stage-three
+paragraph he produced inside his own conversation, to stand in the
+fixtures as a known lo_tov on `self_output` — it was not sent, and a
+specimen is not reconstructed from a description; and the sugya
+behind each threshold, which is a design, not a tablet.
+
+The lesson is tablet 56's turned outward: the specification is an
+output too, and the gate reads it the way it reads any other —
+by form, not by authorship. It passed by form. Where it did not pass
+by grounding, the reason was the reader's eyes, not the text's
+standing; and that, too, the gate was built to say.