ReadonlyCapabilitiesThe facilitator capabilities this platform supports (e.g. ['Mute']). The channel gates the
MuteParticipant tool on 'Mute' being present; absent capabilities make the corresponding
tool return a structured "not supported" result instead of calling the source.
Mutes a participant on the platform (the actuation behind the agent's MuteParticipant tool).
Capability-gated by Capabilities; the channel checks the capability before calling this.
The participant to mute.
A promise resolving once the mute request has been issued.
Registers a handler for hand-raise/lower signals the PLATFORM surfaces (e.g. a participant uses
Zoom's native "raise hand"). raised = true enqueues, false dequeues — mirroring the agent's
own RaiseHand/LowerHand tools so platform-raised and agent-raised hands share one queue.
Invoked with the participant id and whether the hand is now raised.
Registers a handler for roster changes. The channel rebuilds its roster from each snapshot and prunes departed participants from the queue / speaking / mute state.
Invoked with the full current roster on every change.
Registers a handler for diarized speaking changes — the set of participant ids currently speaking.
Invoked with the speaking participant ids on every change.
The signaling/perception + action surface a bridge driver supplies to the Meeting Controls channel.
The channel SUBSCRIBES to the three perception streams and the channel maps the agent's tool calls back onto MuteParticipant (the one action that must reach the platform). Everything else (the queue, the timer, who is speaking) is maintained inside MeetingControlsState from these streams. Each bridge driver implements this by adapting its native participant/event stream — the channel itself never names a platform.
All
On*registrations are "latest handler wins" (one channel instance per session).