Understand Policy

Policy connects authored intent to reviewed revisions and target-specific delivery. The Library helps users find policies and inspect their lifecycle history. Data and artificial intelligence (AI) authoring capture different protection inputs. The compiler validates those inputs and prepares target-specific artifacts.

Read by Concern

Choose the reference that matches your question:

• States and revisions distinguishes proposed work, approved content, and delivery.
• Roles and permissions explains command capabilities and policy grants.
• Classifications, principals, and methods explains catalog selections and target behavior.
• Validation and review decisions distinguishes blocking findings from reviewable conflicts.
• Architecture explains component responsibilities.
• Role-based access control and AI policies separates product access from authored runtime permissions.
• Policy terminology defines shared terms.

Keep Responsibilities Separate

An author can prepare a replacement while an approved revision remains governed. A reviewer must inspect the current submitted content before deciding. An operator follows delivery and recovery evidence after governance completes. An application developer must preserve API errors, identities, and concurrency tokens.

No single status label answers every question. Refer to states and revisions before interpreting a policy’s progress.

Continue with Work with policies or System operations.