cui-phase1-language

Permitted CUI Phase 1 language includes phrases that describe labeling and custody without making enforcement claims. Writers should use terminology that accurately reflects the targeted SELinux policy state without implying mandatory access control.

To avoid enforcement claims in Phase 1 CUI documentation, you must exclude language that implies mandatory access control. The Skill flags prohibited phrases and guides you toward safe descriptions of UMRS CUI handling and custody.

Prohibited phrases in targeted SELinux policy briefs include any language implying mandatory access control or enforcement claims for Phase 1. The Skill identifies these misrepresentations to ensure documentation remains technically accurate.

Yes, this Skill is ideal for CUI training materials, policy briefs, and technical documentation. It defines permitted and prohibited language to guide safe, accurate communication regarding Phase 1 CUI constraints.

Phase 1 CUI language must avoid enforcement claims because the underlying targeted SELinux policy does not enforce mandatory access control yet. Documenting enforcement inaccurately misrepresents UMRS CUI handling capabilities.

Yes, the Skill explicitly defines permitted versus prohibited language for Phase 1 CUI descriptions. It provides precise guidance to summarize allowed phrases and flag prohibited ones for your draft documentation.