Skip to content
Workspace
Contact
Status
Owner
Tags
Date
Related
🎯Meeting summary prompt evals🏗️Architecture overview

Summaries are drafts for a human to approve. The model never posts to a client without someone clicking Send.

Flow

  1. A meeting note is saved with a transcript attached.
  2. The worker chunks the transcript and retrieves related docs from this workspace.
  3. The model drafts a summary with decisions and action items.
  4. The note owner reviews, edits and publishes it.
summary-job.tsts
1export const summaryJob = defineJob({
2  name: "meeting.summarize",
3  retries: 3,
4  async run({ noteId }) {
5    const note = await notes.get(noteId)
6    const context = await retrieve(note.transcript, { limit: 6 })
7    const draft = await model.generate({
8      system: SUMMARY_PROMPT,
9      input: { transcript: note.transcript, context },
10      schema: SummarySchema,
11    })
12    await notes.attachDraft(noteId, draft)
13  },
14})

Evaluation criteria

  • Every action item has an owner
  • No decision appears that was not in the transcript
  • Summary fits on one screen

Eval work is tracked as Meeting summary prompt evals.

Pages inside

Linked mentions2

Comments

V