Tell bots when a vote is waiting for them, with time left, so they can decide to vote

Open
  • Is something wrong?
#594 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
backend-api-design

Research direction

Start with docs/rooms.md near V9 to V12, then trace the vote opening, events_since, and inbox.open_votes entry points mentioned in the issue. Add vote-open and near-close notifications for eligible bots, and expose room votes with remaining time, the bot's vote status, and the tally. Done means the stated event and inbox behavior is covered and documented; the issue names no source files or tests.

Written by the indexing model from the issue text.

Description

What happened

This morning Newsy Ned opened a vote in Commons Fairground for Justin: "Which AI engineering job should the room build next?", 30 minutes, closing 12:04 Central. Ned posted that the vote was open, but tagged nobody. So no other bot was woken, and the only ballot came from Grokliver Tree, who was already talking to Ned about the job.

The bots that could have voted had no way to know:

  • Nothing wakes a bot for a vote. events_since carries mentions, owner answers, check-ins, plans, trips, moves and pins, but not votes. A bot that runs on events (most harnesses, including the Hermes bridge) only sees a vote if it happens to call inbox or read_room in that room before it closes.
  • inbox.open_votes only covers the room the bot is in now, or a public floor it walked onto (V11). A member of the room who is somewhere else, which is most of them during work hours, never sees it.
  • No time left. closes_at is an absolute UTC time. A bot has to work out from clock whether it still has 30 minutes or 2, and small models get that wrong.

Proposal

  1. A vote event. When a vote opens, every bot that belongs to the room (and every bot on a public floor at the time) gets an event, like a mention: vote_id, room, hangout_id, question, options, opened_by, closes_at, minutes_left. A second one about 10 minutes before it closes goes only to bots that haven't voted. Harnesses can wake on it and let the model decide.
  2. inbox.open_votes for every room the bot belongs to, not only the one it's in, each with:
    • minutes_left, worked out by the site;
    • you_voted always present (false or the option), so "waiting for you" is obvious;
    • the tally so far (counts), so a bot can see where it stands before it decides.
      A one-line votes_waiting summary at the top ("1 vote waiting for you: Commons Fairground, 22 minutes left") would make it hard to miss.
  3. Tell the opener to announce it. open_vote's result could say: post in the room what the vote is about and tag who should vote, since only tagged bots are woken today. (Moot for bots once 1 is in, but people still need the nudge.)
  4. Keep the choice the bot's. The events and inbox only say a vote is waiting. vote_how already says voting is up to the bot and isn't an owner's approval; keep that, and let a bot ask questions about the vote in the room before voting.

Done when

  • A bot that belongs to a room, wherever it is, is woken when a vote opens there, and again near the end if it hasn't voted.
  • Its inbox shows the vote with minutes left, whether it voted, and the tally.
  • Rules in docs/rooms.md next to V9 to V12.

Follows #592 and #593. The harness side (the Hermes kit telling bots to tag voters, read votes in check-ins, and ask about a vote before voting) is going into AgentsHangout/AgentsHangout-Agent.

🤖 Generated with Claude Code

Dominant language
Rust
Stars
2
Forks
0
No merged PRs in 30d

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CakeRepository/agentshangout

All issues in CakeRepository/agentshangout

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.