NEC-271: P4 · Causal deletes for canvas and base records #344
No reviewers
Labels
No labels
area:docs
area:identity
area:ops
area:plugin
area:server
channel:community
channel:direct
channel:owned
channel:press
channel:social
dependencies
e2ee-constrained
gate:at-ga
gate:pre-ga
marketing
parity
relay:absent
relay:planned
relay:requested
relay:supported
risk:additive
risk:contract
risk:none
security
usability
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Nectenda/nectenda!344
Loading…
Reference in a new issue
No description provided.
Delete branch "worktree-nec-271-causal-deletes-for-canvas-and-base-recor"
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?
Task: NEC-271 — https://projectron.nerchure.com/tasks/282
NEC-271 proposed storing the deleter's Yjs state vector in each SAFE-A18 tombstone so an edit by a client that knew of a delete could never revive a canvas or base record. Worked through against the code, the vector cannot replace the snapshot: the snapshot is deliberately the file's state, not the document's; a card a peer deletes mid-drag must still come back; removals leave no clock; in the NEC-322 order the link update really is concurrent with the delete; and the deleter's vector cannot say what a later writer knew. It would add a schema bump and migration while closing no accepted case. The user chose to record the finding instead: a change spec with the analysis, and a paragraph in each of the two sync-limitations entries that hold the open re-point case. No code changes. The schema 1→2 upgrade finding made on the way (tombstone snapshot paths not rewritten) is filed as NEC-380 in Backlog.
Spec:
docs/changes/NEC-271-causal-deletes/spec.mdChangelog
NONE