# Access profile snapshot verifier
## Public API
`pub fn verify() -> Result<(), String>`
`verify` runs one isolated synchronous real-stack scenario. It proves saved-profile privacy and exact resolution evidence, group-authority and direct-subject dual-gate rights, immutable Access snapshots and saved-profile identity links across profile renaming, recoloring, policy replacement, and archival, archival independence, and the absence of implicit rights for the saved-profile owner.
The scenario uses `kcode-k1-access` 0.6.0 and `kcode-k1-access-profiles` 0.6.0. Both concrete-policy Access snapshots retain the same saved profile ID after the profile presentation and policy change. Once archived, the saved profile is unavailable through ordinary lookup and resolution, while both snapshots, their policy behavior, and their profile links remain unchanged.
Success returns `Ok(())`. Setup, operation, and assertion failures return contextual strings. The verifier uses deterministic subject and target fixtures in a fresh `tempfile` directory that is safely removed when the run ends.
## Performance
`verify` is not yet benchmarked. It performs a fixed amount of verifier work over one group, one saved-profile lifecycle, and two Access snapshots; delegated local persistence and callback completion have no finite timeout.