# Public intelligence

Product design

This page describes the product model and requirements. Examples illustrate the model, not a guaranteed API or completed feature. Check the [application contracts](/stormtrust/apps/) and [dataset inventory](/stormtrust/product/platform-and-data/datasets-and-source-contracts/) for implemented scope. Use [operations guides](/stormtrust/engineering/operations/) for runnable procedures.

Public intelligence turns the internal event graph into useful public information. It supports education, organic discovery, sharing, embeds, community authority, and product acquisition.

## Public storm pages

Each meaningful public event may have a stable URL:

```txt
/storms/2026/08/16/kansas-city-mo/st-2026-08-16-kc-001
```

A page may contain event timing, affected areas, maximum estimated hail, confidence, source labels, a public map, reports, affected ZIP codes, supported structure estimates, revision time, and a call to action.

## Local intelligence pages

Potential public scopes include state, metropolitan area, city, county, ZCTA, event date, and historical location.

These pages derive from real StormTrust data rather than generic templates.

## Search principles

Programmatic pages contain substantive local data, disclose timestamps, expose provenance, avoid fabricated narrative and thin duplicates, provide interactive value, and use appropriate structured metadata.

## Embedded maps and widgets

Future distribution may include iframe embeds, Web Components, share cards, API-driven widgets, tenant-branded lookup, and property lookup where licensing permits it.

## Content distribution

One event may produce several public and private outputs:

```txt
Storm event
   ├── public event page
   ├── city page update
   ├── alert
   ├── customer email
   ├── map visualization
   ├── report
   ├── social card
   ├── broadcast talking points
   └── partner embed
```

The same event model drives every output.