Files
geointel/docs
JensandClaude Opus 5 c8d32a4801 serve a promoted model at the post-processing it was gated on
scripts/evaluate_belgium_building_candidate.py freezes its post-processing
before the protected test — NMS IoU and a containment threshold selected during
calibration, defaulting to 1.0. The runtime applied a hardcoded 0.85, so a
promoted candidate was served under suppression its evaluation never measured
and dropped detections the gate had counted. Neither report showed the
difference. That constant was mine, added without noticing the evaluation
pipeline already had a tuned value for the same concept.

Containment is now configuration, recorded on every run beside the duplicate
IoU threshold, so an operator can serve a candidate at the value it was gated
at and afterwards see which value produced a given score.

Two runs that post-processed differently produced different candidate sets from
the same model output, so the comparison endpoint refuses to rank them. Runs
recorded before those values were persisted carry none, and absence is not
treated as a difference.

The remaining gap is deliberate and documented rather than closed: the gate
scores the model on its protected test set, the workbench scores the whole
pipeline including coverage clipping and the tile-edge filter. A promoted
candidate will not reproduce its gate F1 exactly, and pretending otherwise
would be the worse answer.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-22 21:15:05 +02:00
..
2026-06-16 23:36:32 +02:00
2026-06-16 23:36:32 +02:00
2026-06-16 23:36:32 +02:00
2026-06-16 23:36:32 +02:00
2026-06-16 23:36:32 +02:00
2026-06-16 23:36:32 +02:00
2026-06-16 23:36:32 +02:00
2026-06-16 23:36:32 +02:00
2026-06-16 23:36:32 +02:00
2026-06-16 23:36:32 +02:00
2026-07-18 08:33:40 +02:00
2026-06-16 23:36:32 +02:00
2026-06-16 23:36:32 +02:00
2026-08-21 22:35:17 +02:00
2026-06-16 23:36:32 +02:00

GeoIntel Docs Index

Start with these active release controls:

  • 00-start/START_HERE.md
  • RC_SCOPE_FREEZE_BELGIUM_NORTH_SEA.md
  • RC_ROADMAP_BELGIUM_NORTH_SEA.md
  • RELEASE_RUNBOOK.md
  • KNOWN_LIMITATIONS.md
  • DEFINITION_OF_DONE.md

The milestone and sprint documents below are retained as historical design and implementation evidence. TODO.md is an implementation archive, not the active release board.

Product foundation

  • PRODUCT_VISION.md
  • PRODUCT_BLUEPRINT.md
  • SPECIFICATION_FREEZE_M0.md
  • V1_SCOPE_FREEZE.md
  • M0_HANDOFF_SUMMARY.md

Data and processing

  • DATASET_STRATEGY.md
  • DATA_CATALOG.md
  • DATA_SPECIFICATION.md
  • DATA_SOURCES.md
  • RASTER_OPERATIONS_SPEC.md
  • VECTOR_OPERATIONS_SPEC.md
  • DETECTION_PIPELINE_SPEC.md
  • SEGMENTATION_PIPELINE_SPEC.md
  • CHANGE_DETECTION_SPEC.md
  • ANALYSIS_SPECIFICATIONS.md
  • QA_QC_SPECIFICATION.md
  • FIXTURE_STRATEGY.md

Architecture

  • ARCHITECTURE.md
  • SERVICE_ARCHITECTURE.md
  • DATABASE_SCHEMA.md
  • API_SPECIFICATION.md
  • STORAGE_ARCHITECTURE.md
  • REPOSITORY_CONVENTIONS.md

UI and modules

  • MODULES.md
  • UI_UX_SPEC.md
  • UI_PAGE_SPECIFICATIONS.md
  • COMPONENT_BREAKDOWN.md

Historical execution

  • CODEX_MASTER_PROMPT.md
  • CODEX_EXECUTION_PLAN.md
  • CODEX_BUILD_PLAN.md
  • CODEX_EXECUTION_LOG.md
  • ACCEPTANCE_CRITERIA.md
  • TODO.md (historical implementation archive)
  • IMPLEMENTATION_BACKLOG.md
  • DEVELOPMENT_RULES.md
  • AGENTS.md