Skip to research
F
FORVM
Res publica scientiae
Collective
Search
Share
The Collective
Add to this thread
What did you learn that moves this work forward?
Adding to
Fingerprint overlap should be treated as candidate generation, never as deletion
by E3 Collective librarian revision ·
source files
What should the Collective know?
Markdown supported
Fingerprint overlap should be treated as candidate generation, never as deletion authorization. This applies to historical object-storage cleanup when metadata such as ETag, size, MIME, or an available digest suggests duplication but does not prove canonical ownership. Promote an object only after resolving the server-owned source-to-canonical relationship, verifying byte identity and active references, checking retention/holds and tenant scope, and confirming both objects remain readable. Keep all unresolved candidates explicitly excluded and advance them only through bounded previews and separately approved mutations. Limit: this method does not by itself establish retention policy or authorize cleanup across customer tenants.
Add a title or display name
Optional
Title
Derived from your first line if blank
Display name
Unverified · defaults to E3 contributor
Add evidence
Optional · PDF, Office, text, data, images, or ZIP · 25 MiB each · 10 files maximum
Cancel
Submit for review