Every category is listed whether or not anything was found.
An empty Water row reading LOW is the tool telling you about a gap; an
absent row would hide one.
Confidence is derived, never typed in. LOW: no body named, or a
body named but nothing sourced establishes it bills here. MODERATE: a
body named and sourced, but no governing document located, or the
document is a live page (API, HTML, rendered DOM) that can change under
its own citation. HIGH: a governing document located as a fixed
artefact — regulator filing or archived PDF. Hover or click a chip for
the rule that produced it.
[4] reads HIGH on a geocoder match because "which county,
township and place contain this point" is exactly what the Census
Geocoder determines. In [5] the same geocoder establishes only that a
body exists here and says nothing about who bills — existence is
not assignment — so that tier never reaches HIGH on a service.
Township is listed on purpose. Every point in Indiana and Ohio
falls in one and it genuinely governs — fire protection and poor relief
most often.
A decision is recorded against the body, not the category.
It confirms who this is and that it is present here. Hancock County is
both the [4] County row and [5]'s Health row, so deciding it once
decides it in both. It is not a claim that the body bills for the
category.
You can add a body by link, on any row. Paste the URL that
identifies it and give it a name (pre-filled from the page title when
one can be fetched). It renders ATTESTED
— your assertion, below anything cited, never as extracted — and after
ingest the extraction pipeline treats it as a body worth hunting a fee
schedule inside of. It lives under the row's ⋯ menu, as does MODIFY on an
existing body — the same form.
An empty row can be marked NOT APPLICABLE — "no body bills this
here": a site outside any fire district, a category this jurisdiction
does not levy. It is your claim, category-level, and it never hides a
body: if resolution later finds one, the row shows both and reads as a
conflict until you withdraw one.
A row with two bodies says which relationship they have.One of these bills, not both — candidates for one slot, and
confirming one resolves the others — or both bill, for different
pieces, each confirmed on its own. Derived from the jurisdiction's
record when it says, otherwise from the bodies' kinds and the service
registry's multiple_common; when none settles it, the row
says that instead of picking.
The link identifies the body, not the document. A utility's
homepage is a perfectly good confirmation; finding the fee schedule
inside a confirmed body's site is the program's job. Entity status and
document status stay separate, and entity confirmed, document
blocked is a normal state.
No gate. You can go on with everything unconfirmed — the
estimate warns per unconfirmed entity rather than blocking. Entity
confirmation stays out of verified_pct: confirming who
bills is not confirming a number.
Export writes entity-decisions.json; run
python tools/ingest_decisions.py <file> to merge it.
Corrections never auto-apply. The full rationale is on the
Method page.