ADR-0002: Editorial Control Model
Status: Accepted
Date: 2026-01-05
Context: When multiple people contribute tributes to a book, someone needs to control what goes in. Contributors may submit content that is inappropriate, off-topic, or problematic. The book creator (admin) needs authority over the final output without Memory Maker being liable for content decisions.
Decision Drivers:
- Book creators are paying customers with a vision for their book
- Contributors may lack "situational awareness" (Uncle Steve problem)
- Memory Maker should not own content moderation liability
- The book is a gift—the creator should control the gift
Decision
The book admin owns full editorial control. They can:
- See all submissions before they appear in the book
- Approve or reject any submission
- Request revisions from contributors
- Decide the final layout and presentation
Memory Maker provides the platform; the admin owns the content decisions.
Rationale
Sheri's framing: "It's their ownership of what goes in and what the output is. So if they want Uncle Steve's slightly misogynistic, racist story in there, then that is on the admin."
This is analogous to choosing who attends your wedding. The person throwing the event gets to decide. Memory Maker is not a publisher making editorial judgments—it's a tool that empowers the book creator.
This also eliminates liability. If problematic content appears in a book, that's the admin's choice, not Memory Maker's.
Considered Options
Option 1: No Editorial Control
All submissions go directly into the book.
Pros:
- Simplest to build
- No workflow complexity
Cons:
- No protection against inappropriate content
- Admin has no control over their own product
- Could result in embarrassing or harmful books
Option 2: Platform Moderation
Memory Maker reviews and approves content.
Pros:
- Consistent quality control
- Protects against harmful content
Cons:
- Massive liability exposure
- Doesn't scale
- Subjective judgments create disputes
- Not our content, not our call
Option 3: Admin Editorial Control (Selected)
Book creator approves all content.
Pros:
- Creator owns their product
- No platform liability
- Scales infinitely
- Matches user expectations (it's their book)
Cons:
- More work for admin
- Delayed publication while awaiting approvals
- Mitigation: Clear contributor expectations upfront
Consequences
Positive
- Clear ownership model
- No content moderation liability for Memory Maker
- Admins feel empowered
- Quality controlled by the person who cares most
Negative
- Admin workload increases with more contributors
- Mitigation: Batch approval UI, email notifications
- Some admins may approve inappropriate content
- Mitigation: This is their choice; terms of service protect platform
Neutral
- Requires building approval workflow (Phase 2)
Implementation
Phase 1 (MVP):
- Admin can view all submissions
- Basic approve/reject per submission
Phase 2:
- Request revision workflow
- Suggested edits workflow (see ADR-0004)
- Batch operations
- Email notifications for pending approvals
Files Affected:
- Admin dashboard
- Submission status model
- Notification system
Related Decisions
- ADR-0003: Contributor Visibility Settings
- ADR-0004: Revision Workflow
References
- 20260105-napkin-session.md - "Uncle Steve" discussion
Author: Bert Carroll Reviewers: Sheri Dudley Last Updated: 2026-01-05