OpenPOIs

Use when the user wants to refresh the independent POI snapshots (OSM, Overture) and rate the OSM snapshot for conflation. Triggers: "refresh all snapshots", "do a new data pull", "download new OSM/Overture", "monthly data refresh", "pull the latest POI data". Does NOT include conflation or Source Cooperative publishing — those live in conflate-snapshots.

Use when the user wants to run the full OSM-history turnover model from scratch — downloading Geofabrik full-history PBFs, formatting observations, fitting lambda, and applying predictions to the current snapshot. Triggers: "run the full history pipeline", "refit the model from scratch", "bump osm_data version and rerun", "new model run", "rerun history modeling for <date>".

Use when the user wants a QA/sanity check on a recently completed pipeline run — row counts, parameter spot-checks, diffs vs. prior versions, or site-side verification. Triggers: "sanity check the run", "verify the new data looks right", "QA the model output", "diff against the last version", "did the upload work".

Use when the user wants to match rated OSM POIs with Overture POIs into a unified dataset, partition it for web consumption, and push to Source Cooperative. Triggers: "run conflation", "publish new data", "push new conflated data to Source Cooperative", "bump conflation version", "reconflate with new parameters", "re-upload the partitioned parquet".

Use when the user wants to sweep model types or group keys against a fixed history run — keeping `versions.osm_data` pinned while producing multiple fitted models. Triggers: "try a different model type", "rerun the model for <group_key>", "sweep model variants", "compare random_by_type vs constant", "fit a new group_key on the same observations".

Use when the user wants to bump the frontend to point at newly uploaded Source Cooperative data, or wants to run/preview/build the site locally. Triggers: "push new data to the site", "bump site to latest data version", "update constants.js", "deploy the site", "preview the site with new data", "rebuild site after data refresh".

Use when the user edits the conflation taxonomy CSVs, or when the frontend filters / taxonomy reference page are suspected to be out of sync with the CSVs. Triggers: "sync taxonomy to the site", "update frontend after taxonomy change", "rebuild taxonomy.html", "check taxonomy drift", "constants.js out of sync", "regenerate taxonomy generated file".