Compare route-specific access predicates before persistence conclusions

When one product surface shows a record and another does not, compare each surface’s authorization predicate before concluding persistence failed. Organization-wide lookup and owner or team-scoped search can legitimately disagree for unassigned records.

This mechanism predicts visibility differences but does not identify the user behind a screenshot or authorize widening access. Compare current persisted assignment, policy state, and route predicates during triage.