Planning status: proposed. First research cohort: selection-pending. No cohort has been selected in this record. Jackson is a discovery example, not an approved cohort.
Canonical research records own these values. Candidate and deferred decisions are proposals, not release commitments.
| ID | Decision | User outcome | Required layers | Acceptance evidence |
|---|---|---|---|---|
| parcel-research | candidate | Locate parcel geometry and interpret source attributes with provenance. | parcel-boundaries | Approved source, native identifier semantics, mapping, validated release, and source/vintage display. |
| parcel-delivery | deferred | Deliver versioned parcel data through an API, downloads, tiles, or GIS integration. | parcel-boundaries | Choose and independently verify each delivery interface; no interface is implemented by this record. |
| Layer ID | Decision | Meaning |
|---|---|---|
| parcel-boundaries | candidate | Publisher parcel geometry with documented native identifiers; first source-review focus. |
| assessment-attributes | candidate | Assessment fields with native units, codes, null semantics, and linkage to parcels. |
| recorded-transfers | deferred | Recorded transfer records with an explicit instrument and parcel linkage contract. |
| addresses | candidate | Address records and their match basis; not interchangeable with parcel identifiers. |
| zoning-permits-overlays | deferred | Separate zoning, permit, and contextual record families require individual contracts before release. |
The deferred zoning, permit, and overlay grouping is a planning category. Split it into independent layer contracts before source onboarding. A successful parcel review does not establish any other layer.
Which jurisdictions and required layers belong in the first research cohort?
Subject: missouri. Status: open. Responsible role: product-owner. Assigned owner: Unassigned.
Next action: Record jurisdiction IDs, layer priorities, and a decision reference before claiming a selected cohort.
What acquisition and reuse are supported for the intended parcel capability?
Subject: candidate-jackson-parcels. Status: open. Responsible role: data-steward. Assigned owner: Unassigned.
Next action: Review official metadata and terms; prepare a scoped request if needed without submitting it.
What schema, quality tolerances, freshness policy, and responsible people govern a first release?
Subject: missouri. Status: open. Responsible role: data-steward. Assigned owner: Unassigned.
Next action: Agree a versioned parcel contract after native-source review; retain unresolved values.
Use the task and gap templates to retain findings. Select people for the roles before relying on escalation. No monitoring or notification schedule is configured by these records.