heavymap

Industrial Atlas handoff (2026-10-18)

Objective: perform and document the Hamilton operational batch and reproducibility checks while HeavyMap frontend repairs proceed independently. Current bounded work: NA-313 (Hamilton batch), NA-314 (independent repeats), NA-315 (screened integration artifact). Existing issues: NA-269 (jurisdiction gate), NA-306 (incremental pre-publish checks), NA-304 (OSM deferred), NA-29 (reconciliation history).

This repository copy is adapted from Morgen’s supplied HANDOFF-CURSOR-CODEX.md, with the accepted concurrent-working amendments. The original counts and local paths are reported context, not new validation in this session.

Read first

Environment and boundaries

Repository: niagaraassembly/heavymap. Reported Deb checkout: /fast/code/making/na/heavymap. Real inputs and generated outputs: /fast/code/making/na/local-data/, off git. Cloud fixture checks do not prove a real Hamilton rebuild. Do not commit pulled rows or identifying values. Evidence leaving Deb must be screened.

PR #80 records the merged split plan; split execution and identifier migration require a separate assignment from Morgen. No repository split, path moves or package/wire renames are authorized. Private heavymap-restricted stays untouched. Public publish/deploy still needs the jurisdiction gate sign-off. Before merging, verify whether the changed paths trigger publication and whether jurisdiction approval applies. Agents do not merge.

Work and evidence

Already-authorized validation can continue while the documentation PR is prepared. It does not wait for #71 unless a specific technical dependency is demonstrated. Assign one owner and record the task packet before beginning a new task.

  1. On Deb, perform the batched registry repeat, property-code versus zoning count, address_no_parcel tagging, and tile/dossier rebuild under the existing assignment.
  2. Perform repeat 3 in a fresh isolated container on Deb, against the same pinned inputs and code revision. Follow beta-gate section 3 for exact byte, ID and metric comparisons and documented nondeterminism.
  3. Advance NA-306 incrementally from the observed results. Distinguish pipeline defects, source limitations and release blockers.
  4. Prepare build-only deployment tooling only within a bounded assignment. This does not authorize public deployment.

For each run, record input IDs/retrieval times/hashes, commands, code revision and dirty-tree state, environment/lock identities, output manifests/hashes, comparison results and unresolved checks. Missing/uncomputed values carry reasons, not zero. Public run-record copies must be screened.

Baseline from the supplied handoff: 117 tests reported, 17 skipped. This PR does not rerun or confirm that result. The next validation owner must report current pass/fail/skip/unrun counts and identify which skipped checks matter to the Hamilton gate. Do not reuse old “next free” PI numbers; inspect current rows and reservations.

Integration and next action

NA-321 records Morgen’s Hamilton Stage A/B decisions and run IDs, linked to NA-269. Batch/repeat/artifact task completion does not itself open a stage.

Use the existing dossier schema until a separately owned/reviewed contract change is accepted. For the first integration, identify a screened artifact, jurisdiction, producer revision, schema version and hashes. If no eligible artifact exists, report the precise missing evidence; frontend fixture work continues.

Next action: the assigned Deb owner refreshes repository state and records the batch packet and operational evidence. Shared interface changes have one preparing owner and a named frontend reviewer. Log Atlas insights in Spreadsheets/19-process-insights.csv using the existing columns and append-only rules. Return PR/head SHA, checks and run-record references, exact blockers and next action.