Approval pipeline: drafts, L2 → L1 → admin #31

Closed
opened 2026-10-08 20:49:33 +00:00 by anas · 1 comment
Owner

Part of #20. Every change is a draft with its diff; L2 submits to an L1 of that scope; L1 approves or returns with comments; admin publishes or rejects with comments; L1 work goes straight to the admin; admins' own edits publish directly. Queues for L1 and admins; status and comments on each draft; readers see only published versions; audit log. Uses IAM grants.

Part of #20. Every change is a draft with its diff; L2 submits to an L1 of that scope; L1 approves or returns with comments; admin publishes or rejects with comments; L1 work goes straight to the admin; admins' own edits publish directly. Queues for L1 and admins; status and comments on each draft; readers see only published versions; audit log. Uses IAM grants.
anas added this to the Phase 4: Content moderation (Divan's own copy) milestone 2026-10-08 20:49:33 +00:00
Author
Owner

Content model decided (docs/content-model.md, "Content management model"): the pipeline works on per-entity revisions (version history issue) and covers tags (tags issue), poet intros, books, chapters and sub-chapters as well as works.

Content model decided (docs/content-model.md, "Content management model"): the pipeline works on per-entity revisions (version history issue) and covers tags (tags issue), poet intros, books, chapters and sub-chapters as well as works.
anas closed this issue 2026-10-08 22:34:51 +00:00
Sign in to join this conversation.
No project
No Assignees
1 Participants
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: anas/divan#31
No description provided.