Files
geointel/docs
JensandClaude Opus 5 ff4a15aa74 let an operator's adjudication reach the score
The review vocabulary already separates a model error from a reference gap,
because the product's position is that official footprints are not
automatically perfect ground truth. Those verdicts were only counted. An
operator who inspected forty false positives and established that twelve are
buildings the reference simply lacks still saw a precision counting all forty
against the model — a number they had personally disproved, on the panel where
they disproved it.

Applying the verdicts gives an adjudicated score reported next to the raw one,
so nothing is quietly improved. Not being able to judge is not evidence in the
model's favour, so uncertain and obscured verdicts keep counting, as does a
decision from a later release that this runtime does not recognise.

Because part of the evidence is usually still unreviewed, the honest form is an
interval rather than a single corrected number: pessimistic assumes every
unreviewed finding is a model error, optimistic assumes none is, and the
headline equals the pessimistic reading so a partly reviewed check never
presents as a settled one.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-22 20:43:22 +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