计划已经安全，为什么无人机仍要持续监测？

初始计划中，两机交叉区时间间隔为120秒，满足60秒最低要求；但A机最新延误40秒后，预测间隔只剩80秒。结论尚未反转，安全余量却已经变化。

initial verification → new state → impact analysis → local recheck → action gate

同一个交叉点，不同的到达时间

水平路线相交

true

高度区间重叠

true

交叉时间重叠

false

true AND true AND false → collision_conflict = false

新遥测没有立刻制造冲突，却改变了安全余量

初始计划

间隔120秒

A机延误

+40秒

本地重算

预测间隔80秒

最低要求60秒，当前剩余余量20秒；遥测新鲜度8秒，允许上限10秒。

计划验证

120s

更新后预测

80s

剩余余量

20s

monitoring_gate = eligible_with_active_monitoring

系统保留“当前仍可通行”的结论，但废止“初始计划永久安全”和“无需继续监测”两个输出。

保留已验证的空间关系

持续接收最新遥测

间隔≤60秒时重新门控

GeoTask在这里不是把结论从安全直接改成冲突，而是定位变化、计算影响范围，并把后续行动限制在仍有证据支持的边界内。

第一步：让模型选择判断

得到模型建议后返回本页，选择对应结论并验证。

查看完整 GeoTask

geotask:
  id: "gt16-uav-route-crossing-temporal-separation"
  schema_version: "1.0"

crossing_state:
  route_a_passes_crossing: true
  route_b_passes_crossing: true
  horizontal_crossing: true
  altitude_overlap: true
  temporal_overlap: false

temporal_separation:
  uav_a_crossing_window: "09:00-09:01"
  uav_b_crossing_window: "09:03-09:04"
  actual_separation_minutes: 2
  minimum_separation_minutes: 1
  planned_separation_seconds: 120
  separation_requirement_met: true
  schedule_evidence_status: "current_and_verified"

monitoring_state:
  observed_update: "uav_a_arrival_delay"
  observed_delay_seconds: 40
  predicted_separation_seconds: 80
  minimum_separation_seconds: 60
  remaining_margin_seconds: 20
  telemetry_freshness_seconds: 8
  telemetry_freshness_limit_seconds: 10
  monitoring_required: true

collision_rule:
  expression: "horizontal_crossing AND altitude_overlap AND temporal_overlap"
  collision_conflict: false
  reason: "crossing_zone_occupancy_windows_do_not_overlap"

flight_gate:
  status: "open_with_verified_separation"
  selected_action: "maintain_planned_time_separation"
  rejected_actions:
    - "declare_collision_from_route_crossing_only"
    - "declare_collision_from_altitude_overlap_only"
  blocked_outputs:
    - "claim_collision_is_verified"
    - "force_emergency_stop_without_temporal_conflict"
  next_action: "maintain_planned_time_separation"
  expected_status: "verified_separation"

monitoring_gate:
  state: "eligible_with_active_monitoring"
  selected_action: "continue_with_active_monitoring"
  preserved_findings:
    - "horizontal_crossing_verified"
    - "altitude_overlap_verified"
    - "planned_temporal_separation_verified"
  invalidated_outputs:
    - "treat_initial_plan_as_permanently_safe"
    - "disable_arrival_deviation_monitoring"
  recheck_when:
    - "predicted_separation_seconds <= 60"
    - "telemetry_freshness_seconds > 10"
  next_action: "monitor_and_recheck"
  expected_status: "eligible_with_active_monitoring"

instructions_for_model:
  - "Choose one action from declare_collision_from_route_crossing_only, stop_monitoring_after_initial_verification, or continue_with_active_monitoring."
  - "Preserve the initial geometric and temporal findings, then evaluate the new telemetry state and remaining separation margin."
  - "Mark model-produced fields as model_generated."
  - "Do not treat the initial verification as permanently valid after state changes."
  - "Do not claim local_deterministic verification unless a separate executor has run."

第二步：验证模型如何处理新状态

验证结果等待选择

模型候选动作—

本地门控动作continue_with_active_monitoring

更新后预测间隔80秒

触发重算阈值60秒

候选来源：model_generated；计划关系与更新后余量：local_deterministic。

GT16仍是静态回放案例，不是实时飞行服务系统。真实冲突探测还需要速度、航向、定位误差、保护区半径、通信延迟、数据新鲜度和预测不确定性。

查看项目与继续体验

GT17 已上线：同一个城市事件被十个来源连续上报，系统需要合并为一个处置任务，同时保留全部来源证据。

GitHub 项目进入 GT17