Create an implementation handoff for one reviewed source. This guide prepares a task; it does not create or deploy a parcel ingestion application.
Complete source review. You need a source contract approved for the intended acquisition and use, assigned people, and a declared jurisdiction/layer scope. The Jackson discovery record does not yet meet these prerequisites.
-
In the source contract, pin the native schema and mapping revisions. Define native identifier scope, joins, null meanings, geometry and coordinate system, units, and omitted fields. Keep unresolved interpretations as blockers.
-
In the acceptance contract, define expected-count evidence, geographic scope, quality tolerances, duplicate and geometry rules, accepted exceptions, and freshness policy. Use coverage definitions; do not substitute request success for complete extraction.
-
In the actual checkout, inspect the existing dataset contract and app inventory. Identify reusable code and the precise implementation boundary. Record actual manifests, runtime versions, source paths, and tests. The documentation record layout does not prescribe runtime storage.
-
Define the authorized acquisition and validation fixture, resource limits, checkpoints, quarantine behavior, lineage, and repeat-execution behavior. Record any human gate, restricted evidence location, or missing permission.
-
Specify code and data versions separately. Require an immutable release identity, source vintages, mapping revision, validation evidence, publication action, serving interface, and compatible recovery target. Explain how a failed or stale layer appears to consumers.
-
Draft a bounded implementation task with these references and acceptance checks. Follow Validate a change, Deploy a change, and Recover a release for the actual application. A documentation merge is not a production approval.
The developer can identify approved inputs, permitted actions, expected outputs, validation, and recovery without guessing a source interface or quality policy. Link executed tests and observed artifacts after implementation, not before. Record a gap for any missing prerequisite.
Terraform continues to own Worker identities and durable backing resources; Wrangler owns application code, bindings, versions, and deployments. Use the existing catalog and shared tooling when an application is actually required. No new per-app scripts or duplicated platform dependencies are needed for this documentation slice.