Snapshot and limitation model for probabilistic results

[Erilla]

Question

SlashWho snapshots are immutable and published atomically; a snapshot is complete or partial with a limitation code, and internal provenance is stored but never shown.

Decide how a probabilistic match is represented. Is match confidence persisted, and if so where? Does a sweep that was capped or budget-starved produce a partial snapshot with a new limitation code? What does it mean when a later sweep no longer matches a character an earlier immutable snapshot already published — is that a removal, a new snapshot that simply omits it, or something the history view has to explain? How does a fingerprint-derived character interact with suppression?

[Erilla]

Resolution

• Snapshots persist the resulting character membership only; per-match confidence is not retained.
• A successful sweep that reaches its configured request cap before testing every candidate publishes an immutable partial snapshot with the internal limitation code fingerprint_sweep_capped.
• A queued job waiting for shared Blizzard capacity is not partial, and transport, 429, or 5xx failures create no snapshot.
• If a later sweep no longer meets the match threshold, its new snapshot simply omits that character; earlier immutable snapshots remain history. This is changed inference, not a retroactive removal.
• Privacy-hidden Raider.IO ownership is excluded before fingerprint matching. For otherwise public data, no separate SlashWho suppression path is added, per the resolved privacy stance.