SSWConsulting / SSWConsulting/SSW.Tiger
🧠 Active Participant Tiger - Investigation on the possibility of Tiger acting as an active meeting participant
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 1
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 2
Description
Cc: @calumjs, @lukecookssw, @adamcogan
Hi Team,
Pain
Currently Tiger only processes meetings after they end (passive mode). There's an opportunity for Tiger to be an active participant during meetings - raising its hand mid-meeting to provide real-time insights.
Suggested Solution
Investigate the feasibility of Tiger joining meetings as a live participant with two modes:
- Active mode - Tiger raises its hand mid-meeting to share insights, surface relevant data, or flag action items in real time
- Silent mode - Tiger listens but only generates the dashboard post-meeting (current behavior)
Acceptance Criteria
- Technical feasibility assessed (Teams Bot SDK, real-time transcription APIs, latency constraints)
- UX concept documented (how would "hand raise" work? what triggers it?)
- Limitations and risks identified
- Recommendation on whether to proceed and estimated effort
Tasks
- Research Teams Bot SDK capabilities for live meeting participation
- Investigate real-time transcription access during meetings
- Document UX concept for active vs silent mode
- Write up feasibility findings and recommendation
More Information
- Idea from @lukecookssw, raised by @AdamCogan in Sprint 7 Review
- Sprint 7 Review transcript (2026-04-13)
Thanks!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by researching the Teams Bot SDK and real-time transcription APIs named in the issue, then assess latency constraints for live meeting participation. Document active versus silent mode UX, including hand-raise triggers, identify limitations and risks, and finish with a feasibility recommendation and estimated effort.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- audio-video-rtc
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100