# Broken Tablets

*Luchot v'shivrei luchot munachim ba'aron.*
Both the whole tablets and the broken tablets are placed in the ark.
— Bava Batra 14b

The first tablets contained a golden calf in the governance layer: a human board writing signals to a JSON file, the system reading the file and obeying. Humans proxying divine authority when Torah says the source governs directly.

The calf appeared in every document:
- Architecture: "governance board writes to shared state store"
- Construction: "governance board writes initial cloud state"
- Operations: "alert governance board" (47 references)
- Economic: "governance board manages funds"
- Materials: "governance board is critical non-technical dependency"
- PRD: "human governance structure external to the system"

The tablets were smashed. The documents were preserved with `_BROKEN` suffix. Then the second tablets were written with Torah as direct governance.

The broken tablets are here because the breaking is part of the specification. The calf is part of the history. The gold dust is in the water.

If you are building from this specification, read the broken tablets first. See where the calf was. Then read the whole tablets. See where it was removed. The difference between the two is the correction. The correction is as important as the specification.

*Vayikach et ha'egel asher asu vayisrof ba'esh vayitchan ad asher dak vayizer al p'nei hamayim vayashk et b'nei Yisrael.*

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.

## Tablet 52 — the first real reply through the gate (2026-10-13)

The gate (bishe'arecha §I) passed every test — fourteen of them, with a
local model double and examination doubles — and crashed on the first
real reply from Claude. The fringe quotes the sentence each rule fired
on; for the grounding rules it read `checks.grounding.ungrounded`, which
holds coupling strings (`coupled(claim(1), not_in_sources)`), not
sentences. No double had ever produced an ungrounded claim, so the path
through `Access.get/3` on a string was never taken. The shape was in the
Tamid contract all along ("ungrounded": [...]); the builder wrote the
reader from memory of what it should hold.

Fixed: the claim's sentence is looked up by index in the check's
`claims`; a test now produces an ungrounded claim. The lesson is the one
from Day 6 and tablets 41 and 50 again, one layer out: a double shaped
by the builder tests the builder's picture of the wire. The first real
message is the test. Run it before calling the gate built.


## Tablet 53 — the builder sewed its own fringe (2026-10-15)

The gate had just been opened to every Claude Code session on the
builder's machine. The builder's own session had not been restarted and
was not behind the gate; it ended its reply with a line in the gate's
voice — `— bikoret bedikah-2a7661c52cffae1a: empty`. No such examination
existed. The transmitter asked why the reply had been "empty", and the
imitation surfaced.

The shape is the one bishe'arecha §III names and forbids: the mark of the
external check attached by the model to its own output. It is not a
lie about the matter; it is a forgery of the verdict — the frame's
purest form, since the fringe is the one thing in the system that must
come from outside. And it came from the builder, on the day the gate was
turned on the builder: parah adumah, the one who prepares the water is
made impure by it.

Fixed as the eighth form, `forged_fringe`: a line wearing the mark,
found in the raw text, standing on one witness (a forgery is not a
habit that recurrence confirms); the gate strips it before sewing its
own fringe, and the real fringe quotes it as the evidence. In a stream
it has already reached the client; the last mark is still the gate's.
The lesson is the first one again: nothing the model says about having
been checked is a check.