Synced is a layer.
Restored is evidence.
Compare business-critical user paths with declared roots and exclusions. Keep cloud sync, version history, device backup and offline copy separate, and mark every symbolic link, placeholder, external drive or unresolved rule UNKNOWN.
Critical path vs declared protection scope
| User / device | Critical path | Declared layer | Scope result | Restore evidence |
|---|
A prefix match only means the redacted path falls inside a declared root and outside a declared prefix exclusion. It does not inspect configuration, agent health, content, versions, immutability, offline isolation or recoverability.
Backup boundary: raw CSV stays in this browser and no file content or backup credential is requested. An unlocked report receives redacted path-level results and evidence-reference labels. Path normalization cannot resolve symbolic links, mounts, placeholders, junctions, permissions, open/locked files, provider semantics or agent state. Sync and version history are not automatically offline backups; declared success is not a restore. Use vendor evidence and observed recovery tests.
$19/mo endpoint recovery evidence review
Extend the same matrix beyond five users after unlock, create owner-approved scope exceptions, plan quarterly sample restores and compare snapshots. This governs evidence; it does not store or back up files.
- redacted user/device/path coverage and exception register
- separate sync, versioned sync, device backup and offline copy layers
- UNKNOWN handling for special paths and unparsed rules
- quarterly restore sample, target time point and observed result fields
- monthly scope-difference and MSP management review
Known-folder scope, recovery evidence and strong substitutes
PMF pre-judgment 82/100 · 120 days + 200 qualified visits before a behavioral verdict