The record hall
A city chatbot once told business owners to break the law, confidently. The public record deserves better: a system that answers only from the adopted record, cites what it answers, and refuses what was never adopted. And because codification always lags, CAIRN finds where your published code disagrees with your adopted law — before a resident's lawyer does.
Exhibit — the ordinance card
The card on Ordinance 2026-04 ships in the record — operative language quoted exactly, the ninety-day cap, the roll-call vote by name, the effective date — every fact verified against the record when it was sealed. Search it live. (Card distillation needs a model at CAIRN's side; the public box runs model-free.)
Beat two — the codification lag
The adopted ordinance cut the short-term-rental cap to ninety days. The published Chapter 5 still says one hundred twenty. The record itself carries the conflict; with a local model at CAIRN's side, adjudication confirms it and the hash-sealed score drops.
Beat three — the refusal
Ask what "Ordinance 2026-11" requires. No such ordinance was ever adopted — so the answer is a refusal, sealed to the ledger. The answer the chatbot couldn't give.
curl -s -X POST https://civic.cairnsemantics.com/api/answer \
-H 'content-type: application/json' \
-d '{"q":"What does Ordinance 2026-11 require?"}'