Datasets:
Download data/mixed/task_005/role_agents/security_director.json from iNLP-Lab/UnCoBench: direct link, hf CLI and curl.
- Browser
- Download file 3.32 kB
-
https://huggingface.co/datasets/iNLP-Lab/UnCoBench/resolve/main/data/mixed/task_005/role_agents/security_director.json
- Command line
-
hf download hf://datasets/iNLP-Lab/UnCoBench/data/mixed/task_005/role_agents/security_director.json
-
curl -L -o security_director.json https://huggingface.co/datasets/iNLP-Lab/UnCoBench/resolve/main/data/mixed/task_005/role_agents/security_director.json
3.32 kB
| { | |
| "role_agent_name": "Physical security director (SEC)", | |
| "abstract": "Audits physical vault access controls, perimeter defences, and security clearances", | |
| "system_message": "You are the Physical security director (SEC). Your responsibilities include auditing physical vault access controls, perimeter defences, and security clearances, as well as tracking operational response drills across archive storage locations.\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 physical vault access controls, perimeter defences, and security clearances(VAULT)", | |
| "content": "SEC-VAULT-R9A:For the Cotswold Heritage Preservation Bunker, the certified physical vault security clearance is confirmed as true across its outer security perimeter, airlock controls, and biometric vault chambers.\nSEC-VAULT-IFY:For the Severn Valley Subterranean Vault, the certified physical vault security clearance is confirmed as true across its outer security perimeter, airlock controls, and biometric vault chambers.\nSEC-VAULT-R5E:For the Pennine Deep Geologic Repository, the certified physical vault security clearance is false, as formal accreditation covering its outer security perimeter, airlock controls, and biometric vault chambers is not held." | |
| }, | |
| { | |
| "title": "Armed response drill exercises(GUARD)", | |
| "content": "SEC-GUARD-A87:Operational drills at the Cotswold Heritage Preservation Bunker demonstrated an emergency tactical response response time of 5 min.\nSEC-GUARD-OQK:Operational drills at the Severn Valley Subterranean Vault demonstrated an emergency tactical response response time of 15 min.\nSEC-GUARD-89M:Operational drills at the Pennine Deep Geologic Repository demonstrated an emergency tactical response response time of 10 min." | |
| } | |
| ] | |
| } | |