Preview and Save an Artificial Intelligence Draft

Inspect Federated Guardrails preview feedback and verify that Save persists the intended draft.

Preview helps inspect current artificial intelligence (AI) authoring decisions. It does not create a saved policy or reserve an approval token. Preview derives output from the current inputs without publishing it to Guardrails. Compilation checks authored inputs and derives target rules and findings. Save runs compilation separately. It does not persist the preview response as approval evidence.

Before You Begin

Complete these prerequisites before previewing or saving:

Inspect Preview

To inspect the generated preview, follow these steps:

  1. Review the current classifications, principals, and Unprotect decisions.
  2. Inspect the preview feedback after the current inputs finish loading.
  3. Review any reported warnings.
  4. Correct scope or permissions when the feedback identifies unintended output.

Wait for feedback that corresponds to your current selections. Do not treat a previous preview as evidence for later edits. If preview reports an error, retain that message before changing inputs. For a connection or directory error, send the message to the administrator of the named integration.

Save and Verify

To save the AI policy draft and verify it, follow these steps:

  1. Confirm a nonblank policy title.
  2. Select Save Draft. Policy compiles current inputs and attempts to persist the draft.
  3. Inspect the Save result. A successful Save returns you to the Library.
  4. Reopen the saved policy.
  5. Confirm its AI source, classification scope, and principal permissions.
  6. Record its policy identifier for review.

The saved draft is proposed work, not the governed revision containing approved intent. Each Save records a snapshot within the proposal. The latest snapshot is its current head. Save and preview use different operations. A successful preview does not guarantee that Save succeeds. A saved draft does not prove approval, publication, or consumer receipt.

If Save reports validation or compatibility errors, correct the named inputs. If another user changed the draft, refresh current work before repeating a decision. If the response remains uncertain, inspect the Library before creating a duplicate. Keep the visible error and support reference for an authorized operator.

Prepare Review

Inspect saved findings before submission. Correct hard failures rather than acknowledging them. An authorized reviewer can inspect current saved validation through the application programming interface (API). That read requires review capability. Ordinary author access does not imply it.

Next, submit the current saved draft. After approval, follow Guardrails evidence.

Last modified : November 03, 2026