Verify engine
Raw in, verified out.
Kiln is the verify engine behind these products. A source document goes in; Kiln pulls out the claims, checks every quote against the text it came from, has a second model score it, and a person signs off. One run is a bake. Out comes the finished piece, the trail behind every line — and a visible mark wherever nobody could back one up.
Four stages in order: read the source, pull its claims into a fixed structure, check each claim back against the source text and score it, then finish. A stage that isn't finished doesn't hand its piece forward. Nothing skips ahead — a claim that fails is repaired or dropped, never waved through.
Under the hood, briefly
Two checks, not one.
The verify stage is two separate checks, on purpose. First a quote gate: every claim must point at a verbatim passage that actually exists in the source — a mechanical string match, no model opinion involved. Then an entailment judge: a second model, with different weights from the one that wrote the draft, scores whether the quoted passage really supports the claim. The writer never grades its own work.
The judge's prompt is pinned by measurement: its wording changes only through a fresh measured run with pre-registered thresholds, never through a casual edit. We learned that the hard way — a single loosened phrase once let bad claims through, and the measurement caught it.
Honest holes
A held piece, not a guess.
When a claim can't be traced back, it doesn't ship as prose. The gap is marked in the finished piece — visibly — so you see what was checked and what nobody could back up. A marked gap is a feature, not a failure: it's the whole difference between checked and hoped.
3 verified · 1 held — the gap ships, the guess never does.
What comes out
Nothing leaves anonymous.
Every line that survived keeps the receipt that got it through: the passage it leaned on, and the check that passed it. That's what makes it safe to build on — you check the trail instead of trusting the tone.
Finished piece
verify · passed
verify · passed
verify · passed
every line torn from a real source — follow the chit back.
Today
Where it runs today.
Setup checklists baked from real rulebooks serve on RuleSage today — here is the table that carries one, twenty-eight steps for Lords of Waterdeep, each quantity carrying the line it came from and a blank left where the rulebook prints no number. A bake isn't finished when it ships: served checklists are re-checked against their source on a daily schedule, so if the source moves or a quote stops matching, the piece gets flagged instead of quietly going stale.
The engine lives inside RuleSage, the rulebook-answering product. RuleSage ships the bake — it is not built on top of Kiln. There is nothing to install on this page and no account to make; this is the method behind artifacts you can already go use. The same show-your-work discipline runs the whole stack — browse a live table's rulings, answered and honest abstains alike, at RuleSage's Monopoly table.