Verify Data Delivery Evidence

Verify Data protection after an authorized approver creates a governed revision.

Before You Begin

Complete these prerequisites before verifying Data delivery:

• Confirm permitted policy visibility.
• Arrange an operator with policy:audit to inspect restricted deployment diagnostics.
• Ask the Traverse integration administrator which tables or columns the approved policy should protect.

Expected locations are the data locations that compilation of the governed revision identifies for protection. They are not every discovered location or the selections in a newer draft.

Verify the Current Deployment

To verify the current deployment, follow these steps:

1. Open the policy in Policy Library.
2. Record the current governed revision and visible protection state.
3. Have the authorized operator check the latest publication request in Operations for errors.
4. Record its deployment identifier and request number (generation) if you need administrator help.
5. Follow delivery troubleshooting if publication reports an error.

Use the application programming interface (API) policy-detail reference when your Panel does not expose the required detail. Use view=governed&includeProtection=true for approved delivery readback. The governed view selects approved inputs for current protection observations. The default view=latest selects replacement-draft content while that draft remains open. Check the approved scope, not the replacement proposal, when verifying delivery. Use the operations reference for restricted deployment details. Restricted operation inspection requires audit authority. Do not obtain broader access merely to interpret a status badge.

Verify Location Evidence

To verify protection at each expected location, follow these steps:

1. Ask the Traverse integration administrator to check the protection status of each table or column identified above.
2. Ask the administrator to confirm that those observations apply to the currently approved policy version.
3. Check that every expected location reports protected.
4. If the policy also uses Guardrails, complete Guardrails verification.

For example, suppose the approved scope expects locations A and B. If A reports protected and B explicitly awaits protection, progress remains incomplete. If Traverse returns no observation for B, ask its administrator to investigate that missing location. If Traverse is unavailable, wait until the administrator restores access before checking protection again. Missing, unexpected, or mismatched location identities prevent a complete match to the expected set.

Policy can show Enforcing while some locations report protected and delivery or protection checks remain incomplete. Check every expected location and any Guardrails delivery before accepting Enforced as the current result.

Stop and Escalate

If the administrator cannot identify the expected tables or columns, or Traverse omits them, keep the verification open. Retain the policy identifier, revision, deployment, generation, timestamp, and visible issue. Do not write protection state manually or guess missing locations.

For failed publication, follow inspection and retry. If publication stopped with an error, resolve that error even if Traverse later shows protected data. If Guardrails also applies, follow Guardrails evidence.

Return to delivery overview or recovery.