# Content engine

Commercial planning

Offers, messages, prices, guarantees, and delivery targets are proposals to validate. They do not establish available features, customer results, or contractual commitments. Confirm implementation and supporting evidence before using a proposal externally.

The content engine derives multiple useful surfaces from one canonical storm event. It should not create disconnected narratives.

```txt
StormEvent
   ├── public event page
   ├── city update
   ├── replay experience
   ├── email briefing
   ├── property lookup
   ├── partner embed
   └── last-storm audit
```

## Content categories

StormTrust content should cover:

- Current storm intelligence
- Response operations
- Historical postmortems
- Evidence education
- Customer protection
- Measured outcomes

## Replay as content

The public replay should be the primary product demonstration. Visitors watch the system move from forecast and radar through events, revisions, property context, and a draft action plan.

The replay is interactive. Visitors can pause, seek, inspect evidence, and select a market. Stable event URLs make each replay shareable.

## Accuracy rules

Use real weather data for historical evidence. Label simulated operational steps as demonstrations. Publish customer activity or revenue only with authorization and traceable source records.

Substantive event pages should disclose timestamps, evidence classes, provenance, revisions, and limitations. Do not generate thin location pages.