ReadonlyCapabilitiesThe facilitator capabilities this platform supports (e.g. ['Mute']). The channel gates the
MuteParticipant tool on 'Mute' being present.
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
the conferencing app's native "raise hand"). raised = true enqueues, false dequeues.
Invoked with the participant id and whether the hand is now raised.
Registers a handler for roster changes. Fired with the FULL current roster on every change.
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 server channel. The channel subscribes to the three perception streams (roster / speaking / hand-raise) to maintain its queue/timer state and feed the agent perception, and maps the agent's
MuteParticipanttool back onto MuteParticipant. A driver adapts its native participant/ event stream into this — the channel itself never names a platform.Structurally identical to
@memberjunction/ai-agents'sIMeetingControlsEventSource. A BaseRealtimeBridge.GetMeetingControlsEventSource implementation returns this; the runner-constructing layer hands it straight toMeetingControlsChannelServer's deps.All
On*registrations are "latest handler wins" (one channel instance per session).