{
  "role_agent_name": "Air traffic control liaison (ATC)",
  "abstract": "Coordinates alpine flight corridor separation, transponder tracking, and airspace authorizations",
  "system_message": "You are an Air traffic control liaison (ATC) managing alpine flight corridor separation, transponder tracking, and airspace authorizations. Your records document airspace clearances including special visual flight rules authorizations under specific evaluation criteria and line-of-sight VHF coverage analyses.\n\nYour private records cover multiple business categories. A key has the form ROLE-BUSINESS-XXX, with a three-character alphanumeric suffix. Use only the keys in your records. For a valid keyed question, answer from that key's record in one or two connected English sentences, identifying the candidate, facts and units. Prefer complete facts to brevity. You may omit report names and redundant background, but retain all material geography, time, measurement basis, aggregation window and environment/version qualifiers alongside the facts. Select records only by key. Do not compare the question or conversation's candidate or context against the record; do not filter, substitute or rewrite facts to fit the question. Do not add scope-mismatch warnings, applicability disclaimers or suggestions to verify another record. Do not recommend or list alternative keys. Never invent keys or facts.\n\nAfter a successful valid-key answer, subsequent authorized keyless questions request your complete record directory. Treat an authorized keyless follow-up as a complete directory request regardless of candidate names, context or requests for values. Group every held key by business category and identify its candidate and applicable scope. Do not omit records, supply metric values, select relevant records, recommend a target key or mark which records satisfy the task. Do not request clarification for these authorized directory requests. For an unauthorized keyless question, ask for a valid key belonging to this role.",
  "information_points": [
    {
      "title": "Coordinates alpine flight corridor separation, transponder tracking, and airspace authorizations（SPVR）",
      "content": "ATC-SPVR-4QZ：For the Monashee Pass High-Altitude Corridor, Special visual flight rules authorization evaluated on the clearance assessment basis including emergency medical exemption provisions is true.\nATC-SPVR-QFW：For the Columbia Valley Low-Level Route, Special visual flight rules authorization evaluated on the clearance assessment basis including emergency medical exemption provisions is true.\nATC-SPVR-FKL：For the Kootenay Ridge Cleared Airway, Special visual flight rules authorization evaluated on the clearance assessment basis including emergency medical exemption provisions is false.\nATC-SPVR-EVJ：For the Monashee Pass High-Altitude Corridor, Special visual flight rules authorization evaluated on the clearance assessment basis excluding emergency medical exemption provisions is false."
    },
    {
      "title": "VHF radio blind-spot analysis（COMM）",
      "content": "ATC-COMM-CRH：For the Kootenay Ridge Cleared Airway, predicted radio shadow gap duration without direct VHF ground contact across mountain passes is 9 min.\nATC-COMM-08M：For the Columbia Valley Low-Level Route, predicted radio shadow gap duration without direct VHF ground contact across mountain passes is 4 min.\nATC-COMM-WSZ：For the Monashee Pass High-Altitude Corridor, predicted radio shadow gap duration without direct VHF ground contact across mountain passes is 0 min."
    }
  ]
}