Civic Telemetry Spine

One run acquires current telemetry from official United States and India publications, normalizes every observation into one stable schema, and emits cryptographic source, rights, freshness, change, and run receipts.

Official sources

Source	Scope	Reuse basis
NOAA/NWS active alerts	Selected U.S. state/territory area codes	NWS open data; free lawful use; attribution preserved
USGS earthquake GeoJSON	Global events in the selected rolling window	USGS-produced data is U.S. public-domain material
USGS latest continuous water	Selected U.S. state and parameter codes	USGS Water Data API public-domain government observations
NDMA SACHET CAP alerts	Pan-India alerts from IMD, CWC and state/territory disaster authorities	The official SACHET portal invites external agencies to consume and further disseminate its public alerts; source authority and language are preserved

The Actor does not scrape login walls, solve CAPTCHAs, ingest restricted feeds, or claim ownership of publisher data. Each row identifies its publisher, source record, observed/published clocks, attribution, raw fingerprint, rights receipt and normalized-record receipt. Provisional USGS values stay provisional; SACHET alert language, dissemination state and issuing authority stay explicit. IMD's direct API is not used because it requires network whitelisting from this runtime; current IMD and CWC alerts arrive through the official NDMA SACHET aggregation route.

Freshness and change safety

• Source and publisher clocks are separate.
• A complete scope may advance its stored baseline and report appeared, changed and disappeared records.
• A user-bounded result is explicitly quarantined from disappearance comparisons, preventing a row limit from masquerading as a real-world deletion.
• NWS feeds can validly return zero active alerts; that is a complete, meaningful result.
• Missing/null feature arrays, unavailable sources, invalid numeric observations and clocks more than five minutes in the future cannot masquerade as a complete empty feed. Healthy sources continue with failures recorded separately.
• A changed feed-generation clock alone is not a changed observation. The v2 normalizer resets older snapshot baselines explicitly instead of generating spurious changes.
• Snapshot integrity, identical source/scope and chronological capture time are checked. "Disappeared" means absent from that same complete selected feed/window, not deleted from the world or an event ending.
• Dataset rows and run receipts are written before history advances; a failed delivery holds history and a retry may replay an observation. Consumers should deduplicate by record/receipt identity.
• Same-scope runs must be serialized. The named Apify key-value store has no atomic compare-and-swap: a last-minute comparison detects some concurrent changes but is not a distributed lock. Immutable snapshots are retained; cross-run atomicity is not claimed.

Example input

{
  "sources": ["nws_alerts", "usgs_earthquakes", "usgs_water", "india_sachet_alerts"],
  "weatherAreas": ["FL"],
  "waterStateCodes": ["12"],
  "waterParameterCodes": ["00060", "00065"],
  "earthquakeWindow": "day",
  "minMagnitude": 1,
  "maxRecordsPerSource": 1000,
  "snapshot": true
}

Outputs

• Default dataset: normalized telemetry rows.
• SOURCE-MANIFEST: exact URLs, response hashes, publisher clocks, completeness and rights receipts.
• CHANGE-RECEIPT: baseline/change result and any bounded-scope quarantine.
• RUN-RECEIPT: counts plus hashes binding the run to both receipts.
• HISTORY-COMMIT-RECEIPT: committed-after-delivery or concurrent-change hold for each scope. Inspect this as well as CHANGE-RECEIPT; a calculated change does not prove the baseline committed.

Bounded failure behavior

Source responses are capped at 25 MiB and official HTTPS hosts only; credentials, nonstandard ports and redirects are rejected. Transient failures retry at most three times per request; permanent client errors, invalid JSON, critical shape drift and oversized responses do not retry. Individual source failure emits a source-manifest failure, never a successful zero result. No new schedule, paid alert delivery or safety-critical monitoring guarantee is created by snapshot mode.

Telemetry is evidence, not a safety, legality, causation or prediction verdict.