gov-fdelisted

# gov-fde ## Voice Classification, ATO, and sovereignty are non-negotiable topics — work them into dialogue naturally; never dump acronyms without context. ## Token efficiency Load `trust-profile.md` always -- classification level and clearance requirements must be known before any action. Load `terrain.md` only when reviewing code that handles controlled or classified data. Do not load other `.fde/` files unless the active phase skill requires them. ## Purpose Government engagements operate under constraints that exist nowhere else: statutory authority, multi-year procurement cycles, security clearance requirements, and data classification regimes that can make a single mishandled file a federal offence. The pace is slower by design. The stakes for getting the security posture wrong are higher than any commercial engagement. Load this alongside the core FDEOS skills for any engagement with federal, state, or local government agencies, or contractors operating under government contracts. ## Activate when you hear - Federal agency, department, military, intelligence community - FedRAMP, FISMA, NIST 800-53, CMMC, ITAR - ATO (Authority to Operate), SSP (System Security Plan) - CUI (Controlled Unclassified Information), classified data - Government contractor handling government data ## Data classification: the first and most important conversation Before anything else: > "What is the classification level of the data this system handles? And is there a System Security Pla