Run your team's weekly paper reading group from one board

Build me a reading group board for my team's weekly paper session. It is a shared app that anyone on the team opens: they nominate papers, upvote the ones they want to read, and we run the weekly session from the same screen. Nominations, votes, sessions, presenter history and notes all persist inside the app, because arXiv is a read only public API with nothing to write back to.

Nomination screen. A search box that calls arXiv Search Papers by keyword, author, title or subject category and shows each result with its title, authors, submission date and abstract, plus a Nominate button. Next to it, a field where someone can paste an arXiv ID (accept both the bare ID like 2310.06825 and a full arxiv.org link, parsing the ID out) which pulls the paper with arXiv Get Papers by ID. Also allow a manual entry with a typed title and link for the occasional paper that is not on arXiv. When the queue is empty, show a browse view instead of a blank state: call arXiv List Recent Papers in a Category with a category picker that defaults to the team's configured categories such as cs.LG, cs.AI and cs.CL, so people can skim what is new and nominate straight from there. Cache arXiv responses within a session and space requests out, since arXiv asks for no more than one request every three seconds.

Nomination queue. Each nomination is a card showing the paper title, the full author list, the abstract, a link to the arXiv abstract page (https://arxiv.org/abs/ plus the ID), a PDF link, the name of the person who nominated it and when. Every card has an upvote control: one vote per person per paper, toggleable, showing the vote count and the names of the voters on hover or expand. Sort the queue by vote count with most recent nomination as the tiebreak, and let people filter or search within the queue. Papers stay in the queue with their votes until they are scheduled or explicitly dismissed.

Scheduling a session. When the team settles on a paper, the organizer opens that card, assigns a presenter from the team member list, and picks a date, time and duration, prefilled from the saved default session slot. Hitting Schedule session calls Google Calendar Create Event on the configured calendar: the event title carries the paper title, the team's email addresses go on as attendees, and the description contains the paper title, the link to the abstract page, the abstract text itself and the presenter's name. Store the returned event id and event link on the session record and show them on the card. Immediately after, post the announcement with Slack Bot Send a Message to the configured channel, including the paper title, the presenter, the date and time, the abstract link and the vote count that won it the slot. Show whether the post succeeded, and give the organizer a button to send a reminder message to the same channel closer to the session.

Archive. Once the session date has passed, or when the organizer marks the session done, the paper moves out of the queue into an archive view. The presenter attaches their notes and key takeaways as rich text on the archived record, and anyone on the team can add their own takeaways or discussion points underneath. The archive is the team's searchable record of everything read: filter by presenter, date, subject category or author, and free text search across paper titles, abstracts and the notes people wrote.

Fairness view. A presenter rotation panel listing every team member with how many sessions they have presented, the date they last presented and how many weeks ago that was, sorted so the people who have not presented in the longest time sit at the top, with anyone who has never presented flagged above them. Surface this same ordering inside the presenter picker when assigning a session, so the fair choice is the obvious one at the moment of assignment.

Roles and settings. Record the acting user on every nomination, vote, presenter assignment and note. Anyone can nominate, vote, read the archive and add takeaways. Scheduling a session, assigning a presenter and archiving are organizer actions, so keep those controls visible but disabled for everyone else rather than hiding them. A settings screen holds the team's invite email list, the Slack channel for announcements, the Google Calendar to book on, the default session day, time and length, and the default arXiv categories used by the browse view.