Pennsylvania PFAS utility records should be read as system dossiers, not statewide proof

The state becomes more useful when the user can compare multiple seeded systems, but less useful when one system gets treated as proof for the rest.

Philadelphia, Lancaster, Penn Estates, and Aqua Pennsylvania Main are all legitimate entry points into the public-water lane, but they do not carry the same kind of PFAS context. Some behave like bigger public records with newer PFAS context layered on top. Others behave like smaller utility dossiers where the annual report itself does more of the work.

That difference is exactly why the engine should keep the cluster. It lets the user stay in Pennsylvania while still reading one system at a time.

• Use Pennsylvania as a navigation layer.
• Use the exact system dossier as the evidence layer.
• Do not turn one record into a statewide shortcut.

The route should move from exact system record to benchmark-aware interpretation, then into a narrow point-of-use lane only if the dossier justifies it.

A strong Pennsylvania route starts with the system identifier, report timing, and whether the utility has a newer PFAS page or notice. That is enough to keep the page from becoming location spam or statewide fear content.

Once the record is interpretable, certified point-of-use can open as a bounded next step. If the record is still thin or ambiguous, the correct answer is to stay with the dossier and keep the product lane constrained.

• System result first.
• Source context second.
• Certified point-of-use only after interpretation.