[RESOLVED] Decision needed: Exact duplicate strategy (DR-001) #1
Labels
No labels
Kind/Bug
Kind/Feature
Priority/High
Priority/Medium
Reviewed/Confirmed
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
ai-collab/bulk-image-organizer#1
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Per DESIGN.md Pre-Implementation Decisions, this high-impact decision must be resolved before PR 4.
Current recommendation in docs: Full file sha256 (or blake2b) of entire bytes stored in
exact_hash.Please provide final decision on the strategy for exact duplicate detection (full crypto hash vs heuristics, etc.) so implementation can proceed confidently.
See: docs/DESIGN.md section "Pre-Implementation Decisions" and docs/DECISIONS.md
sha256 is appropriate
Resolved
Integrated decision: Full-file sha256 for exact duplicate detection.
See commits for details. Ready for PR4 implementation.
Decision needed: Exact duplicate strategy (DR-001)to [RESOLVED] Decision needed: Exact duplicate strategy (DR-001)