mirror of
https://github.com/NousResearch/hermes-agent.git
synced 2026-11-21 04:09:45 +03:00
4d85429c3a
A room's settings gain `routing: everyone | lead` (+ `lead_member_id`), stored on the same
`room.context_set` event as purpose/notes and read as of the message that opened the
discussion. `everyone` is the default and plans exactly as before.
In a lead room, a human message that opens a new thread and names nobody first runs one
routing turn on the lead's member session. The lead answers `{"assign": [handles]}`; the
gateway validates the handles against the roster and appends a gateway-authored
`room.assignment` event, and only those members take the normal round (with a line in their
prompt that the lead gave them the message). An answer naming no member, @all, or a failed
routing turn wakes the lead alone; a routing answer can never broadcast. @mentions,
@all/@everyone, scheduled posts and thread replies keep today's resolution.
The routing turn is an ordinary driver task whose seen_through_seq is the message's seq
minus one (a member turn always sees through its opening message), so it is identifiable
from durable state, its receipt never advances the lead's watermark past the message, and
it is excluded from the round-0 terminal set so a lead that picks itself still answers.
Its answer is published as the assignment, never as a visible reply.
Desktop: canonical-group-lead.tsx holds the Room settings control (Everyone answers /
Lead: <member>), the "Ada gave this to Linus, Grace" row, and markRoomLead() so the
member chips can show a Lead badge; the history mounts the row with one line.
4d85429c3a
·
2026-11-03 10:43:31 -08:00
History