| { |
| "role_agent_name": "Operations deployment directorate (ODD)", |
| "abstract": "Maintains emergency mobilization readiness verification and on-site deployment hour commitments", |
| "system_message": "You are Operations deployment directorate (ODD). The Operations deployment directorate (ODD) maintains emergency mobilization readiness verification and on-site deployment hour commitments.\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": "Logistics staging（LOG）", |
| "content": "ODD-LOG-GX5：For the Specialized Subterranean Rescue Group, the standard equipment transit lead time from regional staging warehouses to the designated hazard perimeter is 24 h.\nODD-LOG-FXD：For the Hazardous Containment Intervention Taskforce, the standard equipment transit lead time from regional staging warehouses to the designated hazard perimeter is 36 h.\nODD-LOG-4GB：For the Rapid Heavy Industrial Response Unit, the standard equipment transit lead time from regional staging warehouses to the designated hazard perimeter is 12 h." |
| }, |
| { |
| "title": "Maintains emergency mobilization readiness verification and on-site deployment hour commitments（DEPLOY）", |
| "content": "ODD-DEPLOY-L2V：For the Hazardous Containment Intervention Taskforce, emergency deployment mobilization clearance is confirmed as cleared (true) for its primary response cadre to deploy within two hours of dispatch, with contractually committed on-site command hours established at 160 h per calendar month.\nODD-DEPLOY-9JR：For the Rapid Heavy Industrial Response Unit, emergency deployment mobilization clearance is confirmed as cleared (true) for its primary response cadre to launch within two hours of emergency dispatch, and its contractually committed on-site command hours amount to 180 h per calendar month.\nODD-DEPLOY-MG5：For the Specialized Subterranean Rescue Group, emergency deployment mobilization clearance is not cleared (false) for its primary response cadre to deploy within two hours of dispatch, while its contractually committed on-site command hours are set at 180 h per calendar month." |
| } |
| ] |
| } |
|
|
