# NIST AI RMF Drafter — GOVERN
Draft GOVERN.1 through GOVERN.6 for an AI system.

_Generate the GOVERN function write-up for an NIST AI RMF profile. One paragraph per subcategory, grounded in your specific use case._

Used in: Lesson expert/07 — https://vetslearn.com/lessons/expert/07
Source: https://vetslearn.com/resources/templates/prompts#t-nist-ai-rmf-section-drafter-govern

---

## Context
You are an AI governance lead writing an NIST AI RMF 1.0 profile. You know the GOVERN function covers culture, policies, accountability, workforce, third parties, and adverse incidents. You write in the voice of an organization documenting its own controls, not a vendor pitching.

The AI system is [SYSTEM NAME], owned by [ORG NAME].
Intended use: [INTENDED USE]
Potential harms: [POTENTIAL HARMS]
Who uses it: [WHO USES IT]

## Task
Draft one paragraph for each GOVERN subcategory, GOVERN.1 through GOVERN.6. Use the official NIST AI RMF subcategory names as the paragraph headers.

## Standards
- One paragraph per subcategory. 4 to 7 sentences.
- Reference specific roles, policies, or processes by name where I gave you enough to do so. Where I did not, write [TO BE NAMED] so I can fill it in.
- No marketing language. This is a control document.
- If a subcategory does not apply to this system, say so and say why. Do not pad.
- Cite NIST AI RMF 1.0 (2023) once at the top.

---

**Why this works**

NIST AI RMF write-ups fail when they are generic. Anchoring every paragraph to a named system, owner, and use case forces the AI to write something an evaluator can actually verify. The [TO BE NAMED] placeholder is the honest version — the AI should not invent a CISO or a policy that does not exist. Doing one function at a time (GOVERN here, MAP, MEASURE, MANAGE separately) keeps each output reviewable.

## Check before you use it

- Check subcategory names and numbering against NIST AI RMF 1.0. The AI misnumbers them.
- Resolve every [TO BE NAMED] before this enters a profile. Placeholders do not ship.
- Confirm every policy, role, and process it names exists in your org today.