{
  "role_agent_name": "Diplomatic telecommunications coordinator (TEL)",
  "abstract": "Audits redundant fiber infrastructure and delegate terminal deployment speeds",
  "system_message": "You are Diplomatic telecommunications coordinator (TEL). You serve as the Diplomatic telecommunications coordinator (TEL), responsible for auditing redundant fiber infrastructure, delegate terminal deployment speeds, and satellite backup connectivity across candidate summit venues.\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": "Audits redundant fiber infrastructure and delegate terminal deployment speeds（NETW）",
      "content": "TEL-NETW-TCR：For Palais des Congrès de Genève, the summit core transmission circuits maintain active secondary fiber redundancy across physically diverse dark fiber paths. Additionally, the average per-terminal network setup latency for multilingual delegate desk terminals is 12 min.\nTEL-NETW-XF7：At Bavaria International Expo Center, secondary fiber redundancy is active across summit core transmission circuits, while the per-terminal network setup latency for multilingual delegate desk terminals averages 30 min.\nTEL-NETW-L7Q：Nordic Waterfront Congress Hall has active secondary fiber redundancy across summit core transmission circuits, and its per-terminal network setup latency for multilingual delegate desk terminals is 18 min."
    },
    {
      "title": "Satellite backup links（SAT）",
      "content": "TEL-SAT-5KV：The emergency uplink ground station array at Nordic Waterfront Congress Hall provides a sustained satellite downlink throughput of 1200 Mbps.\nTEL-SAT-J7C：Bavaria International Expo Center delivers a sustained satellite downlink throughput of 600 Mbps across its emergency uplink ground station array.\nTEL-SAT-ML2：Evaluations of the emergency uplink ground station array at Palais des Congrès de Genève record a sustained satellite downlink throughput of 300 Mbps."
    }
  ]
}