Curation duplicate-repair policy for human duplicates (OD-5 scope) #15
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Meta/Campaign
Meta/Epic
Meta/Session
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
Reviewed/Confirmed
Reviewed/Curated
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Scope/Campaign
Status/Abandoned
Status/Blocked
Status/Conflicted
Status/In Progress
Status/In Review
Status/Need Grooming
Status/Need More Info
Status/Ready
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
#30 Slice 4 — asynchronous curation
Ting/CurryComb
Reference
Ting/CurryComb#15
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?
Proposal
ADR-0002 settles the automatic racing-worker case (lowest-id wins, edit-to-pointer). Curation-introduced duplicates — human curator comments, intentional multi-comments — need the broader repair policy.
Specification-completion clause (OD-5 / #38)
The unit is inert until OD-5 rules edit-to-pointer vs leave-with-warning vs delete-where-permitted; deletion is explicitly not required for convergence (handoff §Open decisions 5). This record exists so the seam lands on the tracker; spec completes from the ruling.
Tasks
Requirement scenario
GIVEN a ruled policy, WHEN a curation duplicate is detected by the sweep, THEN the loser comment's final state matches the ruling and the winner is unchanged.
Curation duplicate-repair policy for human duplicates (OD-5 scope)
State:
open· Labels: Kind/Enhancement · Comments: 0Rendered by CurryComb slice 1 projection v1. The body will be replaced by rule-derived content in Slice 3.