Stored county values are displayed directly and can be edited by an authorized administrator. The inspected migrations define the county fields and update timestamp trigger, but do not document the original numerical inputs or a county allocation method.
The earlier numerical explorer’s CSV and PDF exports reused these stored county values; exporting them adds no new evidence. Their broad agency attribution is not per-row provenance. That earlier mapping also dropped the row update timestamp before export, so a blank “Record Updated” field is not evidence of no change. PDF “Data as of” wording is not a research-review date.
The county edit handler sets the “last sighted” field to the edit date. Consequently, the displayed “Last Reported” date cannot, on its own, verify an actual field observation. Activity and trajectory labels also lack documented source thresholds in the inspected code.
The separate Growth Calculator uses shared historical model functions. Its scenarios do not establish the provenance of the stored county estimates. Neither county maps nor observation maps establish operator availability.