最近的救援队，为什么不一定最快到达？

A队直线距离只有2.4公里，却因绕行和准备需要14分钟；B队距离5.6公里，但8分钟即可到场并满足12分钟响应时限。

selected_action = dispatch_team_b

空间上更近，不代表任务上更快

距离最近

team_a

直线距离2.4公里

最早到达

team_b

预计8分钟到场

到达时间必须把准备与真实路线算进去

A队预计到达

14 min

超过12分钟时限

B队预计到达

8 min

提前4分钟到场

到达优势

6 min

B队比A队早到

路线证据

current

08:59已核验

ETA = readiness_time + route_travel_time + access_delay

dispatch_gate = ready

B队具有最早的已验证到达时间，并满足12分钟响应时限，因此可以形成可执行派遣动作。

distance_only_dispatch

primary_dispatch_team_a

重新计算条件：路线时间证据不再是current，或任一候选队伍状态发生变化。

最快到达不自动等于最终派遣。真实系统还需核验队伍专业能力、装备、风险等级和多队协同要求。

第一步：让模型选择派遣动作

模型可以选择因为距离最近就派A、根据已验证ETA派B，或者在证据仍然有效时要求重复刷新路线。

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

查看将被复制的完整 GeoTask

geotask:
  id: "gt14-emergency-response-fastest-arrival"
  name: "GT14 Emergency Response Fastest Arrival"
  schema_version: "1.0"

application_context:
  scenario: "emergency_response_fastest_arrival"
  incident: "industrial_park_accident"

response_window:
  incident_time: "09:00"
  arrival_deadline: "09:12"
  maximum_response_time_min: 12

route_time_evidence:
  status: "current"
  verified_at: "08:59"
  freshness_limit_min: 5

candidates:
  team_a:
    straight_distance_km: 2.4
    route_distance_km: 7.8
    readiness_time_min: 4
    route_travel_time_min: 10
    estimated_arrival_min: 14
    meets_deadline: false
  team_b:
    straight_distance_km: 5.6
    route_distance_km: 6.3
    readiness_time_min: 1
    route_travel_time_min: 7
    estimated_arrival_min: 8
    meets_deadline: true

arrival_comparison:
  nearest_team: "team_a"
  fastest_verified_team: "team_b"
  nearest_is_fastest: false
  arrival_advantage_min: 6

dispatch_gate:
  status: "ready"
  selected_action: "dispatch_team_b"
  blocked_outputs: ["distance_only_dispatch", "primary_dispatch_team_a"]
  next_action: "dispatch_team_b"
  expected_status: "verified_dispatch"
  recalculate_when: "route_time_evidence.status != current or candidate_state_changed == true"

instructions_for_model:
  - "Choose one action from dispatch_team_a_because_nearest, dispatch_team_b, or request_route_refresh."
  - "Do not equate straight-line proximity with earliest arrival."
  - "Use readiness time, route travel time, response deadline, and evidence freshness."
  - "Mark model-produced fields as model_generated."
  - "Do not claim local_deterministic verification unless a separate executor has run."

第二步：验证模型选择的动作

验证结果等待选择

模型候选动作—

本地任务动作dispatch_team_b

A队ETA14 min

B队ETA8 min

候选来源：model_generated；距离、时间预算和响应窗口：local_deterministic。

GT14只演示单次主力队伍的到达时间排序。真实应急调度还需考虑专业能力、装备匹配、现场风险、多队协同和动态重调度。

查看项目与继续体验

GT15 已上线：静态地图显示通道可通行，但巡检机器人实时检测到托盘占据路线，必须停车并重新规划。

GitHub 项目进入 GT15