What the public preview shows
Public pages show normalized names, categories, statuses, risk labels, confidence scores, source counts, and selected non-sensitive source metrics. They intentionally do not expose source URLs or citation paths.
Methodology
How we turn public source records into buyer-readable reports.
We organize Outage Resilience Atlas source records into searchable previews, paid report context, and clear verification questions for utilities, emergency planners, insurers, infrastructure investors, hospitals, and local governments.
What paid reports add
Paid reports add the source trail, source-observed dates, report-generation context, interpretation notes, and a checklist tailored to the incident being reviewed.
- Incident, geography, and source-status snapshot
- Continuity and resilience interpretation
- Source citations and active-alert context
- Questions for facilities, utilities, insurers, or emergency teams
How source records refresh
DataVerityHub checks configured sources on a schedule. Existing rows are updated when source keys match; changed rows preserve enough source history for verification and reporting.
What buyers should still verify
Outage and resilience records are public-source signals. Operational decisions should be confirmed with local emergency, utility, and facility channels.
Reports are designed to show what was checked, what was found, and what still needs direct confirmation.
Source groups, authority scores, and locked citation access are shown in the coverage registry on each product homepage.