Skip to content

Airport Intelligence stage D2–D5: runway, approach, context and release guards - #630

Merged
Boym323 merged 22 commits into
mainfrom
feat/d2-airport-runway-change-evidence
Oct 8, 2026
Merged

Boym323 merged 22 commits into
mainfrom
feat/d2-airport-runway-change-evidence

Conversation

@Boym323

@Boym323 Boym323 commented Oct 8, 2026 •

Copy link
Copy Markdown
Owner

Stage D2–D5 (follows merged D1 #629)

  • D2: confidence-gated interpretation of per-flight deduplicated 15-minute observed runway windows vs readiness-gated PUBLIC runway prediction; observed transition is different from predicted divergence and uncertain evidence stays UNKNOWN.
  • D3: bounded per-aircraft approach evidence: corroborated holding, go-around, approach and same-flight re-approach, with strict time, identity and completeness checks; no inferred landing.
  • D4: source-labeled explanation combining existing runway/prediction, METAR/wind, approach exceptions and bounded flow data; link to existing ATC explorer. Explicit NO_ATC_CLEARANCE_EVIDENCE; never claim an ATC instruction.
  • D5: unit, ambiguous/stale/scarce-evidence regressions, single-stream/bounded/no-auto-PUBLIC release boundary, synced EN+CS docs, bilingual UI.

No new API routes, DB changes, providers, pollers, SSE subscribers, persistence or automatic PUBLIC graduation. D1 #629 is already in main. Await PR CI/CodeQL; merge only after green; verify main Release validation + Deploy production.

Boym323 added 15 commits October 8, 2026 22:08
@Boym323 Boym323 changed the title D2: observed runway transition and PUBLIC prediction divergence evidence Airport Intelligence stage D2–D5: runway, approach, context and release guards Oct 8, 2026
@Boym323
Boym323 merged commit 201823d into main Oct 8, 2026
6 checks passed
@Boym323
Boym323 deleted the feat/d2-airport-runway-change-evidence branch October 14, 2026 14:22
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