# Operate StormTrust

Use these guides to operate the organization repository and its applications. Commands run from the repository root unless a guide says otherwise.

## Learn the workflow

### [Build your first Worker](/stormtrust/engineering/operations/first-worker/)

Create a two-file app, run it locally, and inspect a release package.

### [Understand the release model](/stormtrust/engineering/operations/release-model/)

Understand ownership, dependencies, versions, and deployment boundaries.

## Complete an operational task

| Task                                                                        | Guide                                                                         |
| --------------------------------------------------------------------------- | ----------------------------------------------------------------------------- |
| Register an app, add resources, or connect services                         | [Catalog and connect an app](/stormtrust/engineering/operations/catalog-app/) |
| Verify infrastructure, application code, and release packages               | [Validate a change](/stormtrust/engineering/operations/validate/)             |
| Authorize a release and inspect its deployment                              | [Deploy a change](/stormtrust/engineering/operations/deploy/)                 |
| Check a service, inspect logs, or interpret a failed probe                  | [Check application health](/stormtrust/engineering/operations/health/)        |
| Retry a failed release or restore compatible application code               | [Recover a release](/stormtrust/engineering/operations/recover/)              |
| Change access, credentials, infrastructure settings, or lifecycle ownership | [Administer the platform](/stormtrust/engineering/operations/admin/)          |

## Prepare parcel data sources

[Review a parcel source](/stormtrust/engineering/operations/review-parcel-source/) records evidence and checkpoints. [Prepare parcel ingestion](/stormtrust/engineering/operations/prepare-parcel-ingestion/) turns an approved source into an implementation handoff. Start with the [Missouri research section](/stormtrust/product/platform-and-data/missouri/) for scope and source candidates.

## Develop and maintain the platform

| Intent               | Start here                                                                               |
| -------------------- | ---------------------------------------------------------------------------------------- |
| Local development    | [Run the local application stack](/stormtrust/engineering/operations/local-development/) |
| Email testing        | [Test email delivery locally](/stormtrust/engineering/operations/local-email/)           |
| Shared frontend code | [Reuse shared UI](/stormtrust/engineering/operations/reuse-ui/)                          |
| Documentation        | [Write and organize documentation](/stormtrust/engineering/operations/write-docs/)       |
| Access review        | [Review an access change](/stormtrust/org/review-access/)                                |

For historical ingestion and revision checks, use [Inspect a local benchmark](/stormtrust/engineering/operations/local-benchmark/).

## Look up exact behavior

Use the [operations reference](/stormtrust/engineering/operations/reference/) for commands, catalog fields, version identifiers, and retention limits. The [application inventory](/stormtrust/apps/) links to each application's runtime contract. [State and drift](/stormtrust/engineering/cloudflare/state-and-drift/) covers Terraform's R2 backend.

## Documentation structure

These guides use [Diátaxis](https://diataxis.fr/): tutorials teach through a working example, how-to guides complete tasks, reference pages provide exact facts, and explanations describe decisions. Existing GitHub, Cloudflare, and application URLs remain their canonical references.

When changing an operational contract, update its task guide and reference in the same pull request. Keep an application's special requirements beside its application reference. Link to the shared workflow instead of copying it. A proposed capability must be labeled as a gap until its implementation exists.