# Review a parcel source

Produce a source-review decision or a precise blocked checkpoint. Start with one source candidate and a declared jurisdiction/layer scope.

## Prerequisites

Read the [Missouri scope](/stormtrust/product/platform-and-data/missouri/scope/), [record contract](/stormtrust/product/platform-and-data/missouri/records/), and [task authority](/stormtrust/product/platform-and-data/missouri/task-packets/). Assign a data steward and confirm the reviewer's authority before relying on an approval. Jackson is the available discovery example; its bulk source remains unverified.

## Review the source

1. In the actual checkout, read `AGENTS.md`, the documentation skill, applicable app instructions, and Git status. Record the task revision and scope.
2. In the jurisdiction registry and candidate record, resolve the geographic ID, publisher, layer, and official discovery URL. Reuse an existing source ID if the source spans more than one county.
3. In official publisher material, verify the actual dataset interface, native metadata, data vintage, delivery modes, count basis, and restrictions. Record each finding with evidence, retrieval time, method, and limitations. Retain missing values and contradictory evidence. Do not infer an API from a viewer.
4. In the review packet, state intended acquisition, storage, transformation, display, redistribution, and AI use where applicable. Record which questions are resolved and which require a scoped decision. Do not enter an agreement, submit a request, or make a payment without applicable authorization.
5. Select the checkpoint from the table below. If human action is needed, prepare a reviewable request with the exact source, requested artifact, intended use, verified recipient, unresolved questions, owner, and follow-up policy. Store private material outside this public documentation.
6. Record the decision and next action. A discovered interface is not approval; an approved source is not an implemented pipeline. Update the canonical records and run the [documentation checks](/stormtrust/product/platform-and-data/missouri/task-packets/#update-the-canonical-records).

## Checkpoints and permitted continuation

The workflow ID is `review-parcel-source`. These are procedural checkpoints; no execution engine is implemented here.

| Checkpoint                  | Responsible role    | Evidence and next action                                                                                              |
| --------------------------- | ------------------- | --------------------------------------------------------------------------------------------------------------------- |
| Identity confirmed          | Researcher          | Official identity and candidate evidence; continue metadata review.                                                   |
| Access and terms unresolved | Data steward        | Scope and questions; prepare a decision packet.                                                                       |
| Awaiting external action    | Authorized operator | Approved recipient, exact submission, and action scope; submit only with authorization.                               |
| Submitted or under review   | Operator            | Submission reference and follow-up policy; wait or follow approved escalation.                                        |
| Approved                    | Designated approver | Source, intended use, conditions, validity, approver, and decision reference; authorize only the covered next action. |
| Denied                      | Data steward        | Denial evidence and affected scope; stop that path and record alternatives.                                           |
| Timed out                   | Operator            | Deadline and attempts; no permission inferred; stop or follow approved escalation.                                    |
| Delivery received           | Operator            | Receipt, artifact identity/hash where captured, source, format, and approval match; continue authorized validation.   |
| Quarantined                 | Data reviewer       | Validation failure and remediation task; do not promote.                                                              |
| Validated                   | Data reviewer       | Acceptance contract and results; seek publication review.                                                             |
| Published                   | Release operator    | Explicit publication authorization, release identity, and observed delivery verification.                             |

The human branch is a general pattern. The Jackson page's agreement control is an observed review consideration; no finding here establishes that a particular external request or payment is required.

## Verify the handoff

The review is complete when every material claim has evidence, unknowns have an owner and next action, and the recorded checkpoint matches the permitted action. A denied or blocked review is a useful result. Use [Prepare parcel ingestion](/stormtrust/engineering/operations/prepare-parcel-ingestion/) only when its prerequisites are met.