Verify Data Delivery Evidence
Check publication and complete current location evidence without inferring protection from approval.
Monitor Delivery and Withdrawal
Separate approval, publication, consumer receipt, and target-specific protection evidence.
Approval queues publication rather than synchronously activating every target.
Check the currently approved version, not unsaved edits or an older delivery request.
The Operations tab lists publication and removal requests. Each has a request number called generation.
Retrying a request sends its previously saved configuration again.
Before You Begin
Complete these prerequisites before checking delivery:
- Identify the currently approved policy version.
- Confirm permitted policy visibility.
- Arrange an operator with
policy:auditto inspect restricted Operations details. If you hold that capability, you can perform the operation checks yourself.
Follow the Target-Specific Path
To verify delivery for the target, follow these steps:
- Confirm the governed revision through Library inspection.
- Have the authorized operator check the latest publication request in Operations. The operation identifies retained publication work and any reported error.
- Follow the verification path for your policy’s targets:
- Data evidence for Data protection.
- Guardrails evidence for artificial intelligence (AI) protection. Complete both for a mixed policy.
For failed or retired work, follow issues and withdrawal.
A mixed policy needs evidence for every applicable target. Successful Data protection does not substitute for Guardrails receipt. These verification guides cover Data protection and Federated Guardrails. For Secure Query, ask its administrator for the verification procedure supported by your deployment.
Interpret Results
The following table distinguishes the evidence provided by each delivery result:
| Result | What It Establishes | What It Does Not Establish |
|---|---|---|
| Approval | Record the human governance decision. | Prove completed publication. |
| Publication | Make the approved target artifacts available through their publication path. | Prove protection at every location. |
| Positive Data evidence | Observe protection for the current expected Data locations. | Prove a different target received its output. |
| Qualifying Guardrails receipt | Record retrieval of the current configuration by the configured consumer. | Prove that Guardrails applied it to real requests or updated every replica. |
| Archive completion | Remove this policy from the published configuration. | Prove that other policies no longer protect the same data. |
A Guardrails receipt records an eligible consumer retrieval of published output. It is not a consumer assertion that protection has activated. The chart supports both anonymous-only compatibility and an exact named consumer match. Its empty-string default accepts absent or empty request identity, not named requests. Publication reaches Published. Publication plus qualifying receipt allows reconciliation to Enforced for Guardrails-only policies. Mixed policies also need Data evidence. Follow Guardrails verification to check the consumer configuration and current receipt. Refer to states and revisions. For periodic changes after approval, see automatic recompilation.
For the complete author-to-reviewer journey, follow your first policy.
Verify Federated Guardrails Delivery Evidence
Distinguish published Guardrails output from qualifying consumer receipt and runtime activation.
Inspect Delivery Issues and Verify Withdrawal
Route publication failures to authorized recovery and verify withdrawal without claiming universal deprotection.
Feedback
Was this page helpful?