readyMarch 18, 202626mstrategyproductlibrary-demo

Demo Strategy Session

The team aligned on a simple local-first publishing workflow: process recordings in-repo, ship a compressed delivery version to R2, and present every meeting as a navigable library page with transcripts, chapters, and notes.

What You Can Do Here

Watch the meeting, jump by topic, read the condensed brief, and only open the transcript when you actually need the raw wording.

ready

Delivery video isn't published yet

The transcript, chapters, notes, and captions are ready in-repo. Run the publish workflow to push the compressed delivery assets to R2 and enable browser playback on the final site.

Why It Matters

Meeting Brief

strategyproductlibrary-demo

Demo Strategy Session

What the team aligned on

The discussion framed the MVP as a local-first workflow rather than a browser upload product. Every meeting should be processed in-repo, written into predictable content files, and published only after the compressed delivery assets and structured artifacts are ready.

Delivery model

The team chose a pragmatic delivery format: keep the original source video locally, create a high-quality H.264 MP4 for the web, generate poster and thumbnail images, and stream the final delivery asset from Cloudflare R2.

Why the content model matters

Because the app itself does not host an LLM, the transcript and structured artifacts need to live in durable content files. That makes it easy for external agents to upgrade draft summaries, chapters, and notes without changing the runtime architecture.

Frontend implications

The meeting page should combine the video, captions, transcript, chapters, and structured notes into a single polished experience. The homepage should stay lightweight by reading from a generated library manifest rather than scanning each meeting directory on the client.

Decisions

Use a content-first architecture with generated manifests rather than a database-backed CMS for the MVP.

Publish compressed MP4 delivery assets, posters, thumbnails, and captions to R2 in a separate workflow from ingest.

Action Items

Jordan: Prepare the Vercel project, domain, and environment variables for the first production deploy.

Riley: Review speaker labels and structured artifacts on the first real meeting after ingest.

Open Questions

Should a later phase add HLS packaging for very large archives, or is progressive MP4 enough for the foreseeable library size?