✨ Feature - Central transcript archive Tiger publishes to

[kulesy]

From the TinaCloud team.

TL;DR

Tiger already pulls every SSW sprint transcript from Graph for its dashboard, then discards the raw .vtt. We'd like Tiger to also commit that .vtt into a new repo, SSWConsulting/SSW.Tiger-Transcripts, for projects that opt in — so any team or agent session can pull meeting context from one place. Small change to Tiger, no new infra.

The repo

transcripts/{project-slug}/{YYYY-MM-DD}-{HHMM}-{meetingId}.vtt   # raw WebVTT
index/meetings.json                                              # generated lookup
apps.json                                                        # opt-in allowlist
AGENTS.md                                                        # how to consume

Tiger commits each .vtt via a GitHub App scoped to this one repo (idempotent GET-sha-then-PUT). A repo workflow regenerates index/meetings.json on each push. Consumers read via a GitHub Read team grant. Tiger holds one credential to one repo it owns, and zero per-consumer config.

Opting in

Capture is already tenant-wide (Tiger filters every meeting on /sprint/i). The opt-in only governs publishing to the shared hub — a team's retro shouldn't land in a repo others read unless they choose. So apps.json is an allowlist; the opt-in is one PR adding your project:

"projects": { "tinacloud-tinacms": { "displayName": "TinaCloud / TinaCMS", "publish": true } }

For that to produce transcripts, three things must already be true: transcription was on (no transcript otherwise), the subject is {Project} - {Title} (so Tiger attributes it), and the organizer is in Tiger's Teams access policy (a SysAdmin step if it's user-scoped, not tenant-wide).

What changes in Tiger

A flagged, non-fatal publish step after the existing download/parse, for slugs in apps.json — reusing the slug/date/meeting-ID Tiger already derives, plus one GitHub App credential in its secret store.

What we need from you

1. OK to create SSWConsulting/SSW.Tiger-Transcripts (private) under the Tiger team?
2. Who installs the GitHub App? (A bot-account PAT or deploy key works too — App is just the lowest-rotation, account-less option.)
3. Is the Teams access policy tenant-wide or user-scoped? (Decides whether new projects need a SysAdmin step.)

We'll provide

The repo scaffolded (layout, apps.json, index workflow, AGENTS.md, README.md) and the Tiger publish change as a PR — small, flagged, non-fatal.

Out of scope

Per-reader scoping for external/untrusted consumers — GitHub perms are repo-level only. First cut is internal SSW readers via a team grant; a finer-grained access broker is a later piece.

[kulesy]

Happy to do the build myself once you're OK with the direction. I'll scaffold SSW.Tiger-Transcripts and open the Tiger publish-step PR for your review, so it's no extra load on the Tiger team beyond the three calls above (repo creation, who installs the App, and the Teams access-policy scope). Just point me at where the download/parse step lives and I'll wire the publish in behind a flag.

• Eli (TinaCloud team)

[suiyangqiu]

Hey @kulesy, looks like a pretty awesome idea, and I don't see any issues with it. Regarding your questions, here's my responses:

1. OK to create SSWConsulting/SSW.Tiger-Transcripts (private) under the Tiger team?

Yep, I have no issues with that as long as we ensure that the repository remains private since transcripts can contain internal information that we wouldn't want to have public facing such as clients, etc.

2. Who installs the GitHub App? (A bot-account PAT or deploy key works too — App is just the lowest-rotation, account-less option.)

I believe myself or @yaqi-lyu should be able to help with that since we have admin access to the repository 🙂

3. Is the Teams access policy tenant-wide or user-scoped? (Decides whether new projects need a SysAdmin step.)

Currently, the access policy is user-scoped, this was an issue early on in the development and deployment of SSW.Tiger, where for some reason, despite the Teams access policy being set tenant-wide, Tiger would still fail to retrieve transcripts with permission issues, so currently, the Teams access policy is user-scoped.

@yaqi-lyu feel free to correct me if I'm wrong on anything

[kulesy]

Thanks @suiyangqiu, that unblocks everything.

1. Repo created: https://github.com/SSWConsulting/SSW.Tiger-Transcripts, private. It'll stay private permanently, agreed that transcripts can carry client/internal info.
2. App install: I'll register the GitHub App scoped to just this one repo (Contents: read/write) and send you or @yaqi-lyu the install link, so all you have to do is approve it on the repo.
3. User-scoped access policy: good to know, thanks for the history. Since it's user-scoped, I'll bake a 'add the organizer to Tiger's Teams access policy' step into the opt-in checklist (apps.json / AGENTS.md), so each project that opts in knows it needs that SysAdmin step before transcripts actually flow.

Next from me: I'll scaffold the repo (layout, apps.json, index workflow, AGENTS.md, README) and open the Tiger publish-step PR for your review, small, flagged, and non-fatal. If you can point me at where the download/parse step lives in the Tiger codebase, that'll save me a hunt.