✨ Project Summary - Per-project call history archive for client/team onboarding context

Goal

A centralised, queryable history of all project-related calls so a new joiner can ask "what was decided on this project, by whom, when" without watching every recording.

Concept

• Each project has an associated "call archive" — could be a folder/repo, dashboard, or queryable index
• Calls are categorised by project, with: date, attendees, topics, decisions, action items
• New joiner onboarding flow:
  1. Point them to the project's call archive
  2. They get a summary of recent decisions + topics
  3. They can drill into specific calls if needed
• Salespeople / AMs can also share with prospective or new clients to give them context on what's been discussed

Acceptance criteria (high-level — needs refinement)

1. Calls are reliably tagged to a project (from transcript content, file naming convention, or explicit metadata)
2. Per-project call list is browsable / queryable
3. Each call has a summary view (decisions, action items) without needing to read the full transcript
4. Onboarding: a new joiner can be sent a single link that gives them ~30 minutes of context instead of hours of recordings

Background — discussion

As per Michael in Sprint 10 Retro — "history of all the relevant calls to a [project] … when you're like onboarding a [new joiner] … you can just send them like some sort of [summary] generated that gives them the context".

Calum at line 3875: "100%. I mean, all of these calls related to a project … the GitHub repo for the project, [feeds] your agent. It can just look back at all the [transcripts]".

Relationship to Tiger #91

This is downstream of Tiger #91 (generalization spike) — once Tiger handles multiple meeting types, the per-project archive becomes feasible. Treat #91 as blocking refinement of this PBI.

Status

FLOATED — depends on Tiger generalization spike (#91) outcome before this can be properly scoped.

Start by reading Tiger #91, which is identified as blocking this work, and review the linked Sprint 10 Retro recording around lines 3832 and 3875. No implementation files or tests are named. Before coding, refine the acceptance criteria for project tagging, browsing, call summaries, and the single-link onboarding outcome.