How the PREPHAUS Resilience Network is built.
PREPHAUS maps organizations, technologies, capabilities, capital and institutions involved in disaster preparedness, emergency management and resilience.
Network purpose and coverage
The Network helps people discover relevant organizations and understand their recorded capabilities, offerings and relationships. The Data layer describes the canonical public records PREPHAUS currently tracks.
Coverage is selective and changes over time. The Network is not complete, comprehensive, an official registry, government-approved, or an assessment of an organization's performance. Inclusion is not endorsement.
What PREPHAUS tracks
Canonical records distinguish an organization from its people, products and services, investments, deployments, partnerships, publications and other relationships. Taxonomies describe types, capabilities, hazards, customer segments and geography. A modeled entity type does not imply complete public coverage.
- Organizations include relevant companies, public agencies, nonprofits, research institutions, investors and other institutions.
- People and leadership relationships identify a specified public role; association alone does not establish authority over another organization.
- Offerings describe products or services. A claimed capability or deployment is not proof of effectiveness.
- Investor classifications describe organization types. Documented investments are separate assertions requiring their own evidence.
Organization discovery
Candidates may come from curated public directories, government and regulatory material, research, reporting, organization submissions and existing graph relationships. Imports are reviewed separately from publication and ownership approval.
Discovery provenance records how a candidate entered the workflow. An import identifier, spreadsheet mapping or homepage does not independently substantiate every imported statement.
Inclusion criteria
An organization needs a material connection to preparedness or resilience, such as a relevant offering, operational responsibility, research program, investment mandate or documented deployment. A generic climate or sustainability label is not sufficient by itself.
Canonical records approved for public publication, and active public taxonomy records, are indexable. Citation coverage, verification and completeness remain separately reported quality signals and do not make a safely public record private or noindex. Unpublished, archived, inactive and private records remain excluded.
- Disaster preparedness, mitigation, risk reduction, emergency management, response and recovery.
- Resilience technology, climate adaptation with a concrete resilience use, catastrophe risk and infrastructure resilience.
- Insurance resilience, household resilience, business continuity and related research, investment or institutions.
Exclusion criteria
Irrelevant or spam submissions, unsupported promotional claims and duplicate identities require rejection, correction or review. The public corpus excludes unpublished records and private household or account information.
- General climate technology without a material preparedness, risk-reduction or resilience connection is not enough for inclusion.
- Missing information is not filled with invented sources, locations, funding amounts or activity.
- Public status is not a universal test-data marker. Legacy fixture review is a separate control; no exhaustive fixture cleanup is implied.
- A descriptive inventory can be useful with disclosed evidence gaps. Specialized research datasets remain withheld when their definitions or evidence cannot support their claims.
Organization and capability taxonomies
Organization type describes what an entity is. Capability describes the function it offers or performs. Customer segments describe intended users or counterparties. These dimensions are distinct and can overlap.
A primary organization type and additional type assignments can coexist. Taxonomy membership is not certification, a quality grade, commercial preference or evidence of a particular successful outcome.
Hazards, customer segments and geography
Hazards identify recorded areas of relevance, not a guarantee that an organization mitigates every associated risk. Customer segments describe recorded audiences, not verified sales or customers.
Geography describes the particular relationship recorded, where known. Headquarters, service region, jurisdiction, deployment location and an organization's general association with a place are not interchangeable. Sparse or unspecified geography stays explicit.
Relationships and counting
Relationships connect canonical entities without copying them into new identities. A partnership, leadership role, deployment or investment needs a defined subject, object and supporting context. A missing relationship does not prove that none exists.
Organization inventory totals count distinct canonical organization IDs after public-status and filter conditions. Joins cannot multiply those totals. An organization can appear in several category counts, so category totals must not be added together as a market total.
Source hierarchy
Reviewers prioritize sources relevant to the specific assertion, their proximity to the event, publication date and independence. The following hierarchy is a starting point, not an automatic truth score. Multiple copies of one press release are not independent sources.
An official organization statement is primary evidence of what that organization says, not independent verification of the statement. A source link supports only the information it actually contains. Internal provenance and publicly inspectable citations are reported separately.
- Government or regulatory records, for matters within their authority.
- Official organization material, labeled as organization-supplied or self-reported where applicable.
- SEC and other financial filings, for the particular filing and reporting period.
- Academic and research publications, with attention to methods and limitations.
- Credible independent reporting with identifiable sourcing.
- Trade publications with transparent sourcing.
- Investor material, distinguishing disclosed interests and self-reported claims.
- Submissions from an authorized organization representative.
- Other public evidence, evaluated for relevance, credibility and limitations.
What verification means
Verification applies to specified information, not automatically to an entire organization. Verification is not endorsement, certification, a safety guarantee or investment advice.
Evidence can be incomplete or change. Review preserves earlier assertions and their evidence instead of silently rewriting history.
- PREPHAUS SOURCED: the specified information has supporting source material. Its source and any public-access limitations should be identifiable.
- ORGANIZATION CONFIRMED: an authorized representative has confirmed specified information. This is organization confirmation, not independent corroboration.
- INDEPENDENTLY CORROBORATED: the specified information is supported by multiple credible independent sources. Source count alone cannot establish independence.
- UNVERIFIED: the information has not received sufficient verification. This does not mean it is false.
- DISPUTED: conflicting evidence exists and requires review.
Organization claims and proposed updates
A claim requests management access. Email or domain verification, ownership approval, publication and fact verification are separate decisions. A pending claim is not proof of ownership, and approved management access does not verify every profile statement.
Authorized editing members can submit specified fact confirmations, profile corrections, sources, products, taxonomy changes, leadership, public deployments and partnerships for moderation. A viewer can inspect permitted information but cannot submit edits.
Reviewers inspect the proposed change, source material and relevant authority before applying it. Shared people and resources are not globally editable merely because they are linked to a managed organization.
How errors are corrected
Use the corrections form for incorrect or outdated information, duplicates, missing organizations, incorrect relationships, funding or leadership, and other concerns. Identify the record, explain the issue and include a supporting public source when available.
Requests can be new, reviewing, accepted, partially accepted, rejected, duplicate or resolved. A review decision and the actual application of a change are recorded separately. Acceptance does not automatically verify unrelated assertions.
Submitter names, email addresses, private notes and internal review information are not public corpus content. Spam protection and bounded intake protect the review workflow. No response-time or publication guarantee is implied.
Evidence and change history
Where a reviewed change is applied, the internal history records the prior and proposed values, source, submitter type, timestamp, review decision and resolution. Conflicting intervening changes must be reviewed rather than overwritten.
Facts and evidence retain their historical lineage. Replaced assertions can be superseded or retired; old evidence is not silently reassigned to make a new claim appear supported. Private audit details stay internal.
Duplicate identities
Review considers names, aliases, domains, public identifiers and relationships. Similar names or a shared domain create candidates, not proof of duplication. Parent organizations, subsidiaries and regional offices may be distinct.
Merges require review and must preserve relationships, provenance and history. Missing normalized identity fields can conceal duplicates; a zero-candidate result is not a guarantee of a duplicate-free corpus.
Updates, freshness and source availability
Profile updates, editorial reviews, source publication and source availability checks are different dates. A recent profile update is not proof that every fact was reviewed. Unknown dates stay unknown.
Internal current, review-due and stale flags prioritize review under documented thresholds. Age alone does not make a statement false. Review priority also considers missing evidence and incomplete high-value records.
Bounded source checks flag missing pages, redirects and unreachable or blocked URLs. An unchecked URL is not a healthy URL. A broken link does not delete the associated fact: historical evidence may remain useful.
Internal data completeness
DATA COMPLETENESS is an internal measure of whether expected profile dimensions are recorded, including description, website, type, geography, capability, hazard, customer segment, offering, leadership, sources, relationships and verification.
Presence is not accuracy. Completeness is not a company rating, quality score, recommendation or endorsement. Internal operational measures also track source coverage, provenance, review dates, claims, stale records, missing relationships and open corrections.
Dataset methodology and citation
Each available dataset identifies its unit of analysis, inclusion rules, counting method, time scope, geography, source coverage, update frequency and limitations. A live inventory is not an immutable historical snapshot or a complete market census.
Citations identify PREPHAUS as publisher, the entity or dataset name, clean canonical URL and known update date, with links to methodology and available sources. An underlying-record update date is not a source publication or verification date.
The organization dataset's unit is one canonical public organization. Counts use distinct IDs. A historical observation period is not supplied where none is documented. Public source-link counts and the number of covered records are separate measures.
Editorial independence and known limitations
Organization-supplied information is distinguished from PREPHAUS-sourced information and independent corroboration. Commercial relationships do not establish factual verification.
Sponsored participation, if offered, must be disclosed and must not determine taxonomy, verification, rank, inclusion or factual conclusions. Editorial decisions remain separate from commercial participation.
Coverage gaps, outdated material, self-reporting, taxonomy overlap, uneven source availability and uncertain geography remain limitations. The Network is a research and discovery aid, not a substitute for direct due diligence or professional advice.