A property-tax balance, sourced from the city's own system — not guessed

"How much do I still owe in property tax?" is one of the most common questions a municipal call center answers, and one of the worst ones to get slightly wrong: a rounded number or a stale due date is a real debt, stated incorrectly, in the city's own name.

Where the number actually comes from

A live municipal deployment answers this question through a capability bound to the city's own arnona system — not a language model's memory of what property tax usually looks like. The capability's policy declares which of its fields are numeric (a balance due, a total due), which display template shows them, the assurance level the question requires (an identified resident), and the data class of what it returns (financial).

What the resident sees

The resident is shown a card: the balance, the specific property, the due date, and a line naming where the number came from — with plain-language sentences written around it. The model chooses to show that card. It does not type the amount into it.

Why this is the same mechanism as the site's own accuracy article

Kav's own explanation of "the model never authors a number" isn't a slogan sitting apart from the product — it's this exact capability, wired the exact way its own capability policy describes. The arnona balance isn't a special-cased exception; it's the ordinary path every numeric capability takes.

What it replaces

A resident who used to call and wait for this to be looked up gets the same governed answer from whichever channel they already have open, sourced from the same system a call-center agent would otherwise have queried by hand.