Starhunter umbrella

[vcarl]

Star Helpers automation needs a lot of supporting scaffolding to properly support it as a "production" feature in a high-end webapp+discord bot. Ideally it would manage its own recurring processes through automated messages on a timer; notifying participating members (the oversight committee) that there's a new slate of candidates to review.

Reviewing a candidate means exploring their participation in the server. I'm not looking to archive every message in the server, so that means we'll need to instruct the user reviewing about how to find their messages. This probably means a screencast of copying the search string and navigating that UI, and links to whatever support docs Discord has published.

This will need a UI behavior for constraining visibility by guild/role level, role-based access control. Initially this could be simplified to "has guild admin" but we could get more granular if needed. There are also a few bugs and quirks around auth that need fixing, I believe, and cookies may not be correctly managed right now.

I think a fully-baked feature here will be a "grading queue" UI, maybe as a stack of cards, dismissed when completed? With details about their participation shown, and info about final review. This means having an assignment queue generated off an initial report.

I think the report is best produced in several formats, and posted automatically on a schedule. This will ping the organizing committee and open private threads with each member, where they'll receive links to their assigned group of candidates. They'll submit, through a combination of web UI + Discord UI, and a final list will be assembled for final review/approval. This could post with a message component to allow "vetoes" for any mentioned candidate, which could be resolved by a "veto override" majority.

Final candidates are contacted privately by the bot, inquiring as to whether they would like to receive the honor, and explaining to them privately what it is and who else has received it.

Some highlights as to what this will mean, for configuration/data etc:

• oversight role, nominee roles
• configurable messaging?
  • report sent
  • assignments made
  • (probably a lot of small copy within grading? should just do an i18n system?)
  • nominee consent (+accept/reject)
• PDF generation? spreadsheet generation?
• grading queue, database schema

[vcarl]

The overall process:

• schedule triggered
• generate report and archive data
• ping DRI with shortlist to acknowledge and approve assignment
• ping committee members with grading assignments
• when grading complete, ping committee with a final report for approval
• individually ping confirmed members, explaining the role and asking consent to apply it (yes/no/privately)
• ping committee members with final report of accepted