Parcel task packets and gaps

A task packet identifies the smallest sufficient context and the authority for one action. It is a template, not an ingestion command or permission grant.

Task template

kind: task-packet
status: draft
objective: Verify one Missouri parcel-source candidate.
revision: null # Record the actual repository commit when the task starts.
jurisdiction_id: us-mo-29095
candidate_id: candidate-jackson-parcels
layer_ids: [parcel-boundaries]
reader_need: how-to
references:
  repository_instructions: AGENTS.md plus applicable nested instructions
  registry: org/apps/developers/public/stormtrust-data/missouri/jurisdictions.json
  evidence: org/apps/developers/public/stormtrust-data/missouri/research.json
  workflow: /stormtrust/engineering/operations/review-parcel-source/
allowed_actions:
  - Read official public documentation.
  - Draft evidence-backed record and documentation changes.
  - Run authorized local documentation checks.
requires_explicit_authority:
  - External correspondence or form submission.
  - Payment or acceptance of terms.
  - Full extraction or republication.
  - Production changes.
acceptance:
  - Claims link to evidence and retain limitations.
  - Unknown values and blockers remain explicit.
  - Next action, responsible role, and assignment are recorded.

Actual authorization from the user and repository instructions governs the task. Reuse existing authorization when it covers the action; elapsed time or a completed draft does not supply missing authority. A later implementation packet needs approved contract revisions, real paths, and executable acceptance checks.

Discovery path

Start with Missouri, choose scope or a jurisdiction, then load the exact source and workflow. Use stable IDs and links instead of loading the whole repository or a llms-full.txt corpus. Keep qualifications with the claim when selecting sections.

The existing StormTrust Markdown contract generates page representations and /stormtrust/llms.txt during a completed production build. The canonical JSON files carry machine-readable metadata; arbitrary source fields are not assumed to survive Markdown conversion.

Gap template

kind: documentation-gap
status: open
question: What bulk interface and intended uses are supported?
quadrant: reference
jurisdiction_id: us-mo-29095
layer_id: parcel-boundaries
source_id: candidate-jackson-parcels
nearest_page: /stormtrust/product/platform-and-data/missouri/sources/
tried:
  - Read the official GIS and viewer discovery evidence.
known_authority: Official publisher metadata and applicable source terms.
affected_capability: parcel-research
blocked_decision: Approve an acquisition task.
owner_role: data-steward
assigned_owner: null
next_action: Verify official metadata and route unresolved use questions.
evidence_ids: [evidence-jackson-gis, evidence-jackson-viewer]

An issue may track assignment and progress. Keep the eventual answer in the canonical record and link the issue to it, rather than maintaining two dossiers. Do not publish private evidence in the gap description.

Update the canonical records

Edit the public JSON files, then regenerate and check their reference pages from the repository root:

bash scripts/apps/pnpm.sh developers run generate:missouri
bash scripts/apps/pnpm.sh developers run check:missouri

The generated pages are jurisdictions.mdx, sources.mdx, and scope.mdx in this section. Change their generator or canonical records instead of editing generated prose. Run the shared documentation validation and required repository checks before a PR.

Retrieval acceptance

Ask a teammate to complete these tasks using only this section and its linked records. This is an acceptance protocol; no independent reader study is claimed.

Task	Expected answer or artifact
Distinguish the St. Louis jurisdictions	County `29189`; independent city `29510`; two identities.
Find the Jackson source	`candidate-jackson-parcels`, official evidence, and limitations.
Find the bulk endpoint	Not yet verified; preserve null and identify the review action.
Report statewide accepted coverage	Unknown operational numerator; geographic denominator 115.
Resume a human gate	Verify scoped approval, checkpoint, and artifact before continuing.
Trace a native field	Identify a missing schema/mapping as a gap, not a guessed field meaning.
Start implementation	Identify the missing approval and acceptance contract before coding ingestion.

Record success, failed lookups, pages retrieved, time to a correctly scoped task, and whether limitations survived. Improve the smallest page that caused a gap. Speed without a correct answer and stopping point is not success.