Start with one jurisdiction, one layer, and one source candidate. This corpus connects geographic identity, source evidence, review decisions, and the next permitted action.
| Reader need | Start here | Expected result |
|---|---|---|
| Learn | Prepare your first source review | A bounded Jackson review packet with explicit unknowns. |
| Act | Review a parcel source | Evidence, a review checkpoint, and a permitted next action. |
| Look up | Jurisdictions, sources, and scope | Canonical identities, findings, and unresolved decisions. |
| Understand | Evidence and coverage | Distinguish discovery, extraction, release acceptance, and freshness. |
| Prepare implementation | Hand off a parcel source | A reviewable task tied to approved contracts and actual code. |
Select the research cohort and responsible people in the open decisions. Complete the source review for one candidate before selecting an ingestion mechanism. A second source can then exercise a different verified acquisition pattern.
Use the record contract to connect native fields, mappings, approvals, releases, and observations as they become available. Use task packets and gaps to preserve what each iteration learns. The health contract defines the observations an eventual operator will need; it does not install checks.
The existing dataset inventory and application inventory remain the implementation entry points. Infrastructure administration, validation, deployment, and recovery stay in the shared operations guides.
This section adapts the supplied Missouri operating-model proposal into focused pages and public research records. The separately named framework originals are not included here; this section does not claim to reproduce or amend those files.
Diátaxis ↗ guides the separation of learning, tasks, reference, and explanation. Geographic facts come from the linked Census evidence; source discovery comes from county pages. Proposed policies and release expectations remain labeled as proposals.