Umbrella Epic - Feature List

[HunteRoi]

This issue tracks bot refactor and web app delivery.

Implementation priority:

1. Stabilize platform and data layer first
2. Enforce identity and verification rules second
3. Deliver admin configuration capabilities third
4. Deliver user-facing flows and analytics after the core is stable

Phase 0 - Delivery and persistence foundation

• Deployment pipeline always fails #104 Deployment pipeline always fails
• Change ORM to Prisma #111 Change ORM to Prisma
• The bot should log everything. #71 The bot should log everything

Phase 1 - Concurrency, auditability, reliability, and SLOs

• Persist config create/update audit trail #135 Persist config create/update audit trail
• Implement stale-write detection and superseded update deprecation for guild config #136 Implement stale-write detection and superseded update deprecation for guild config
• Enforce strict optimistic locking with bounded retries for transition writes #132 Enforce strict optimistic locking with bounded retries for transition writes
• Implement dead-letter queue and remediation workflow for failed transitions #140 Implement dead-letter queue and remediation workflow for failed transitions
• Implement p95 under 500ms SLO instrumentation and alerting #139 Implement p95 under 500ms SLO instrumentation and alerting

Phase 2 - Identity and verification lifecycle

• Implement global one-time verification identity across all DataDrop guilds #128 Implement global one-time verification identity across all DataDrop guilds
• Enforce global Henallux email uniqueness with staff alert on duplicate usage #130 Enforce global Henallux email uniqueness with staff alert on duplicate usage
• Guard manual implicit verification to VerificationPending with mandatory email check #131 Guard manual implicit verification to VerificationPending with mandatory email check
• Enforce per-guild onboarding and rules acceptance even for globally verified users #129 Enforce per-guild onboarding and rules acceptance even for globally verified users
• Add reverification campaigns with cohort filters and no historical override bypass #133 Add reverification campaigns with cohort filters and no historical override bypass

Phase 3 - Admin configuration (role and channel governance)

• The admin should be able to configure the admin role of their guild, allowing full access to the bot #90 Configure admin role
• The admin should be able to configure the announcement channel for their guild #89 Configure announcement channel
• The admin should be able to configure the number of years for their guild #88 Configure number of years
• The admin should be able to configure the number of classes/groups per year for their guild #87 Configure number of classes/groups per year
• The admin should be able to configure the "grant you roles" channel for their guild #84 Configure grant-roles channel
• The admin should be able to configure the "general" roles for their guild #85 Configure general roles
• The admin should be able to configure the roles name, color, etc. for their guild #86 Configure role definitions (name, color, etc.)
• The admin should be able to configure the bot through Discord commands for their guild #92 Configure through Discord commands
• The admin should be able to configure the bot through a web interface for their guild #91 Configure through web interface

Phase 4 - Compliance and user lifecycle

• Add self-serve data deletion and account deactivation with rolling 24h login block #137 Self-serve data deletion and account deactivation with rolling 24h login block
• Retain moderation and audit evidence with userId linkage and pseudonymization #138 Retain moderation and audit evidence with userId linkage and pseudonymization
• The user should be able to contact the Staff of their guild by sending a private message to the bot #77 User can contact guild staff by private message to the bot
• The user should be able to appeal their ban of a guild through a web interface #68 User can appeal guild ban through web interface

Phase 5 - Automation, provisioning, and insights

• The bot should automatically announce each start of school year for people to update their roles #72 Automatic start-of-year announcement and yearly update campaign
• The bot should be able to generate a server based on the saved configuration for the guild #70 Generate server from saved guild configuration
• The user should be able to have read access to statistics for their guild #74 Read access to guild statistics
• The user should have read access to a dynamic leaderboard that displays information on interactions of users with some channel/category for their guild #73 Read access to dynamic leaderboard
• The user should be able to trigger a search query on the MDN via a command #69 Additional user feature from the feature board
• The user should be able to pin/unpin messages through apps commands #94 Additional feature-list item tracked by epic

Role and target categorization

Admin features

• Bot target: The admin should be able to configure the bot through Discord commands for their guild #92, The admin should be able to configure the admin role of their guild, allowing full access to the bot #90, The admin should be able to configure the announcement channel for their guild #89, The admin should be able to configure the number of years for their guild #88, The admin should be able to configure the number of classes/groups per year for their guild #87, The admin should be able to configure the roles name, color, etc. for their guild #86, The admin should be able to configure the "general" roles for their guild #85, The admin should be able to configure the "grant you roles" channel for their guild #84, The bot should automatically announce each start of school year for people to update their roles #72, The bot should log everything. #71, The bot should be able to generate a server based on the saved configuration for the guild #70
• Web app target: The admin should be able to configure the bot through a web interface for their guild #91
• Shared bot and web target: Change ORM to Prisma #111, Persist config create/update audit trail #135, Implement stale-write detection and superseded update deprecation for guild config #136
• Completed admin feature-list items: The admin should be able to toggle the features on/off for their guild #83, The admin should be able to announce things through a command for their guild #82

Bot owner features

• Bot target (completed): The bot owner should be able to toggle the features per guild #81, The bot owner should be able to restart the bot #80
• Platform target (ops): Deployment pipeline always fails #104, Implement p95 under 500ms SLO instrumentation and alerting #139, Implement dead-letter queue and remediation workflow for failed transitions #140

User features

• Bot target: The user should be able to contact the Staff of their guild by sending a private message to the bot #77, The user should be able to have read access to statistics for their guild #74, The user should have read access to a dynamic leaderboard that displays information on interactions of users with some channel/category for their guild #73, The user should be able to trigger a search query on the MDN via a command #69
• Web app target: The user should be able to appeal their ban of a guild through a web interface #68, The user should be able to pin/unpin messages through apps commands #94
• Shared bot and web target: Implement global one-time verification identity across all DataDrop guilds #128, Enforce per-guild onboarding and rules acceptance even for globally verified users #129, Enforce global Henallux email uniqueness with staff alert on duplicate usage #130, Guard manual implicit verification to VerificationPending with mandatory email check #131, Add reverification campaigns with cohort filters and no historical override bypass #133, Add self-serve data deletion and account deactivation with rolling 24h login block #137, Retain moderation and audit evidence with userId linkage and pseudonymization #138
• Completed user features: The user should be able to create temporary text and voice channels #79, The user should be able to pin/unpin a message in a channel if certain conditions are met #78, The user should be able to ask for a professor email by providing their firstname and/or lastname. #76, The user should be able to get roles by reacting to a specific messages or sending a certain command #75, The user should be able to authenticate as a student/teacher #67

Tracking notes

• Umbrella Epic - Feature List #93 stays tracking-only.
• Deployment pipeline always fails #104 and Change ORM to Prisma #111 are prerequisites for predictable delivery.
• Enforce strict optimistic locking with bounded retries for transition writes #132 and Implement dead-letter queue and remediation workflow for failed transitions #140 should be implemented as a reliability pair.