Implement proposal lifecycle with conflict, rebase, and idempotent approval #16

Closed
opened 2026-07-20 20:25:29 +02:00 by thecrealm · 0 comments
Owner

M1: Users author proposals pinned to a base revision; Curators approve (applies as a change-set, conflict-safe), reject; conflicted proposals rebase or reject; approval idempotent under retry. Acceptance: §11.2.2, §5.3, §9.3, CR-1, CR-17; approver≠author enforced (§4.3, rule exists from #4).

M1: Users author proposals pinned to a base revision; Curators approve (applies as a change-set, conflict-safe), reject; conflicted proposals rebase or reject; approval idempotent under retry. Acceptance: §11.2.2, §5.3, §9.3, CR-1, CR-17; approver≠author enforced (§4.3, rule exists from #4).
thecrealm 2026-07-20 21:43:05 +02:00
  • closed this issue
  • removed the
    now
    label
Sign in to join this conversation.
No labels
M0
M1
M2
M3
M4
M5
blocked
next
now
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
thecrealm/mokuroku#16
No description provided.