One task, one proposal
Group the changes for one task into one proposal, with a cleartitle and a short note saying why. A proposal holds up to 500 changes; a person reviews it more carefully when it’s small.
Changes
Tables:
event, person, venue, assets (books), travel, accommodation, accommodation_assignment (stays), pickup. Junctions for links: event_author, event_chair, event_interviewer, event_intro_wrap, event_staff, event_asset (a book at an event), asset_author, asset_publicist, event_media.
A ref names a record the proposal creates, so a later change can point at it. A link to a new record waits until the record is accepted.
Fields never proposed: id, festival_id, edition_id, user_id, role_type, capabilities, metadata (use the cf_ fields), timestamps, and the printed and deleted marks.
Checked before it’s stored
Every change is checked as if the person made it: the record is this festival’s (and edition’s), the fields exist and can be proposed, and the person may change them. If any change is refused, nothing is proposed, and the422 reply lists each refusal by its position, so you can correct it and send it again.
Send an Idempotency-Key header: the same key again returns the first proposal instead of making a second.
Changed since you proposed it
If someone edits a field after you proposed changing it, the change is held back as changed since: the person sees what it was, what it is now, and what you proposed, and decides. Your change never silently overwrites theirs.Reporting back
GET /proposals/<id> gives each change’s status: pending, applied, rejected, failed (with why), or stale (changed since). Proposals left undecided for 14 days expire.