Skip to content

Record a data-backed verdict for every absent basin - #214

Merged
CooperBigFoot merged 3 commits into
mainfrom
pce/close-the-seven-basin-coverage-gap/milestone-6
Aug 10, 2026
Merged

Record a data-backed verdict for every absent basin#214
CooperBigFoot merged 3 commits into
mainfrom
pce/close-the-seven-basin-coverage-gap/milestone-6

Conversation

@CooperBigFoot

Copy link
Copy Markdown
Owner

Milestone 6 of the seven-basin coverage-gap vision. Three steps, all reviewed and merged into this integration branch.

What this delivers

A durable, data-backed verdict for each of the seven TDX-Hydro processing basins absent from the 55-of-62-basin HFX v0.3.0 dataset. Each basin carries exactly one of source defect, adapter strictness, or transfer failure, derived from evidence rather than asserted.

  • feat(tdx-hydro): add fail-closed basin adjudication #211 — fail-closed basin adjudication. Refuses when required evidence is missing, unreadable, or identity-mismatched; never converts a preserved traceback into a verdict.
  • fix(tdx-hydro): derive duplicate adjudication verdict #212 — derive the duplicate-identity verdict. _adjudicate_duplicate previously returned BasinVerdict.SOURCE_DEFECT as an unconditional literal while computing but never consulting its own measurements. The verdict is now a function of the measured geometry, defined only over non-empty, valid, finite, two-dimensional polygonal geometry, with everything else refusing before Shapely .equals() is reached.
  • docs(tdx-hydro): record seven-basin verdict ledger #213 — the seven-basin verdict ledger, preserved byte-for-byte from adjudicator stdout, plus README provenance and derivation rules.

Provenance

adapter.adapter_version 0.1.0 and adapter.git_revision bca87d8 identify the adapter build under examination — the build under which the seven basins are absent. The verdicts were derived by the adjudicator at bd2606c. These identities are kept separate in the README; the JSON is the single verdict authority.

Verification

  • The committed ledger reproduces byte-for-byte across three independent adjudicator runs.
  • Every verdict is recomputable from the committed JSON using only the README's stated derivation rules.
  • Reinstating a hardcoded duplicate verdict is caught by three tests with semantic assertion failures.
  • Both evidence trees are read-only and were verified unchanged by before-and-after metadata inventories over all 751 entries.
  • Five repository gates exit 0; the adapter suite reports 112 tests OK.

Not in scope

No adapter-strictness correction (m7), no compilation (m8), no source-defect report drafted or transmitted (m9, human-gated), no assembly (m10), no S3 access, no cloud provisioning, no deletion, and no version bump or tag.

_adjudicate_duplicate previously returned BasinVerdict.SOURCE_DEFECT as an unconditional literal while computing but never consulting spatially_equal and coordinate_sequences_equal.

The verdict is now derived by _derive_duplicate_verdict from the measured geometry. The rule is defined only over valid, finite, two-dimensional polygonal geometry; every other input refuses with ValueError before Shapely .equals() is reached.

The emitted evidence records the raw measurements plus a machine-readable derivation rule and selected branch so a ledger reader can recompute the verdict.
The ledger records one verdict for each of the seven absent processing basins, preserved byte-for-byte from adjudicator stdout.

adapter_version 0.1.0 and git_revision bca87d8 identify the examined adapter build, while the adjudicator at bd2606c derived the verdicts.

Both evidence trees were read only and verified unchanged by a before-and-after metadata inventory.
@CooperBigFoot
CooperBigFoot merged commit d5cb923 into main Aug 10, 2026
5 checks passed
@CooperBigFoot
CooperBigFoot deleted the pce/close-the-seven-basin-coverage-gap/milestone-6 branch August 10, 2026 09:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant