Govern
Policy Verification
Prove that grants, filters, masks, freshness, and run behavior match intent before users discover a mistake.
Policy is only real when it survives the actual query path.
Inputs
- a target principal
- the object, metric, or product being validated
- the expected visible rows and column behavior
Flow
- test access using the same surface the user will use
- verify allow, deny, masked, and filtered outcomes explicitly
- inspect lineage or freshness if the issue may be stale upstream data rather than policy
- repeat after any grant, filter, mask, or routing change
What To Verify
- authorization outcome
- row-level visibility
- masked field behavior
- freshness state where the consumer contract includes it
- notebook, model, or asset run health where the output is operationally produced