StormTrust manages its organization, platform, and applications from one infrastructure repository. Terraform provisions durable resources. Wrangler deploys application code and assets.
| Intent | Start here |
|---|---|
| Research Missouri parcel sources | Missouri parcel intelligence |
| Learn the product model | Read an evidence record |
| Create a Worker | Build your first Worker |
| Operate infrastructure and apps | Operations guides |
| Review commercial strategy | Acquisition |
| Look up an app contract | Application inventory |
Product
Follow the weather-to-action lifecycle, product surfaces, data model, and roadmap.
Acquisition
Define the offers, lead systems, money models, proof, and measurement that connect StormTrust to its market.
Organization
Review access, ownership, and organization governance.
Engineering
Follow the GitHub and Cloudflare engineering workflows.
Operations
Create apps, validate changes, deploy, check health, and recover releases.
Applications
Review every StormTrust domain and deployment boundary.
Cloudflare reference
Use the vendored Cloudflare documentation and authoring resources.
Each layer has one owner:
| Layer | Owner | Source |
|---|---|---|
| GitHub organization | Terraform | org/github/ |
| Cloudflare account and zone | Terraform | org/cloudflare/ |
| Application code and deployments | Wrangler | org/apps/ |
| Shared lifecycle modules | Terraform | org/modules/ |
StormTrust turns severe-weather evidence into prioritized, auditable action. The product documentation defines the product lifecycle, intelligence model, operational surfaces, platform requirements, and roadmap.
Use the StormTrust infrastructure repository ↗ to propose changes. The pull request workflow explains verification, planning, authorization, and deployment.