II. Use Cases

1. Pre-Interview: The primary use case, and original goal of the bot, was to have something to cover for the orientation members if no one is available. It will run through basic information with the user, collect data from the user, and have them think about and make preliminary choices about branch and enlistment. After these answers and data are logged into a specified channel, it is then up to a human to accept or deny the person, most likely by having a brief conversation with them when someone is finally available. This allows for the majority of the interview to be done with the bot when necessary, but still gives a human touch and the ability to ask any questions or make changes to choices before their choices become written in stone.
2. Post-Interview: After the user has made choices and they have been approved by a human, the bot allows for automation of nickname changes, text-channel announcements, and role assignment. Please note, the bot currently only supports these operations for users who have done the pre-interview with the bot.
3. Logging: The bot also makes use of JSON logs to create a long-term and interactable form of logging. This keeps track of mutable and immutable data on the user for historical, archival, and data-collection needs. For example, this keeps track of both the RSI username (mutable, changeable) and the Discord ID (immutable, permanent) of users in order to always have a way to access information on a user.