From a property-tax balance to a live payment link, in one conversation
A real resident's balance, voucher list and a live payment link, reached from one conversation — verified end to end, including exactly where it stopped short.
A resident asking about property tax usually wants three things in sequence: how much they owe, which vouchers cover it, and a way to actually pay. A live municipal deployment answered all three from a single conversation, verified end to end against the city's real systems, for a real resident — never named here, per this site's own privacy rule.
What actually happened, in order
The balance rendered correctly for the current tax year, sourced from the city's own arnona system. A follow-up — asking to see issued vouchers — reached a capability that listed the resident's real, issued vouchers, the first of them reconciling exactly with the balance shown a moment earlier. From there, a third step reached the city's own live payment gateway with a working link, ready to take a real payment.
Where it stopped, and why that's the honest ending
The same walk also tried to retrieve one voucher's PDF document, and that call failed — the city's own document vendor returned an empty, unreadable response. Kav's platform did exactly what CLAUDE.md's fail-closed rule requires: it refused to guess a document existed and told the resident the file couldn't be retrieved, rather than inventing one. That failure traced entirely to the vendor's own document store, confirmed independently against the vendor's API directly — not to anything in Kav's own binding.
Why the honest version is the useful one
A resident doesn't experience "the mechanism nearly worked." They experience three real questions answered from their own city's data, in the same conversation, with a working link to pay — and, in the one place a document genuinely wasn't retrievable, a clear statement of that instead of a wrong one.