meeting-assistant/openspec/changes/archive/2026-05-19-define-meeting-assistant-v1/specs/meeting-summary/spec.md

ADDED Requirements

Requirement: Meeting Assistant generates meeting outputs

Meeting Assistant SHALL generate a summary, decisions, and next steps from the meeting transcript, metadata, user notes, and assistant-discovered context.

Meeting Assistant SHALL use a Microsoft Agent Framework pipeline for the first summary implementation. The pipeline SHALL use a configurable OpenAI-compatible endpoint, model, and API key source, including support for a direct key or an environment variable name.

The summary pipeline SHALL retry transient model endpoint failures according to configurable reconnection attempts and delay settings.

The summary pipeline SHALL track context-window usage for the configured model using response usage when available and request-size estimates otherwise. The context-window limit, maximum output reserve, compaction enablement, compaction threshold, and Responses compact endpoint path SHALL be configurable.

When only the configured remaining context ratio is available, the summary pipeline SHALL try to compact the conversation through the configured OpenAI-compatible POST /v1/responses/compact endpoint. If that endpoint is unavailable or returns invalid data, the pipeline SHALL fall back to Microsoft Agent Framework compaction.

Fallback compaction SHALL become increasingly aggressive: collapse old tool results, summarize older conversation spans, keep only the last four user turns, and drop oldest groups if still over budget.

When summary generation fails after retries, Meeting Assistant SHALL write a markdown failure report to the configured summary note path. The failure report SHALL include a clickable retry link, error details, and the meeting artifact paths needed to diagnose or retry the run.

After transcript processing finishes for a recording, Meeting Assistant SHALL automatically invoke the summary pipeline for that meeting.

Meeting Assistant SHALL expose an API operation to retry summary generation for a given summary note path. The retry operation SHALL resolve the linked meeting artifacts from the meeting note frontmatter and SHALL overwrite the existing summary note with either the new summary or a new failure report.

The summary pipeline SHALL expose tools scoped to the current meeting:

• read_meetingnote
• read_transcript
• read_context
• read_usernotes
• read_glossary
• write_summary
• write_context
• list_projects
• list_projectfiles
• read_projectfile
• write_projectfile
• search

All summary-agent read tools that return file-like content SHALL support either reading the whole file or reading a clamped inclusive 1-based line range when from and to are supplied.

After writing the meeting summary, the summary agent SHALL update existing project files when the meeting produced project-relevant knowledge.

The assistant context note SHALL keep meeting, transcript, summary, state, and agenda in frontmatter. The state value SHALL be one of transcribing, speaker recognition, summarizing, finished, or error.

The summary note SHALL keep frontmatter links to meeting artifacts and SHALL copy title, start_time, and end_time from the meeting note when available. If the meeting note has no title, the summary agent SHALL be able to provide a title when writing the summary.

The summary agent SHALL be able to read and write the assistant context body as its own notebook using overwrite, replace, and insert line modes.

Scenario: Meeting processing completes

• WHEN transcription and context collection have completed
• THEN Meeting Assistant generates a summary, decisions, and next steps for the meeting note

Scenario: Assistant context note is initialized

• WHEN Meeting Assistant starts a meeting session
• THEN it creates the assistant context note with frontmatter links to the meeting note, transcript note, and summary note
• AND the assistant context frontmatter state is transcribing
• AND the assistant context frontmatter includes agenda, empty when no agenda is known

Scenario: Assistant context state follows meeting processing

• WHEN transcription, final speaker recognition, and summary generation progress
• THEN Meeting Assistant updates assistant context frontmatter state to transcribing, speaker recognition, summarizing, finished, or error as appropriate

Scenario: Summary pipeline is invoked

• WHEN transcript processing finishes for the current meeting
• THEN the agent can read the transcript, assistant context, user notes, glossary, and bound project knowledge, can write the finished markdown summary to the configured summary note, and can update existing project files

Scenario: Summary agent reads meeting frontmatter

• WHEN the summary pipeline runs
• THEN the agent can read the full meeting note including frontmatter such as title, attendees, projects, start time, and end time
• AND the agent can read the assistant-context frontmatter including agenda

Scenario: Summary agent reads large inputs by line range

• WHEN the summary agent reads the meeting note, transcript, assistant context, user notes, glossary, or a project file with from and to line numbers
• THEN Meeting Assistant returns only the clamped inclusive line range
• AND omitting the line arguments returns the whole readable content

Scenario: Summary agent writes assistant context notes

• WHEN the summary pipeline runs
• THEN the agent can overwrite, replace lines in, or insert lines into the assistant context body while preserving assistant context frontmatter

Scenario: Transient summary model endpoint failure is retried

• WHEN the model endpoint returns a retryable failure while the summary pipeline is running
• THEN Meeting Assistant retries the model request until it succeeds or the configured reconnection attempts are exhausted

Scenario: Summary context window is compacted

• WHEN the summary pipeline estimates that only the configured remaining context ratio is available
• THEN Meeting Assistant attempts to compact the outgoing conversation with the configured Responses compact endpoint
• AND if remote compaction fails, Meeting Assistant uses Microsoft Agent Framework compaction with increasingly aggressive fallback strategies

Scenario: Summary failure is written to the summary note

• WHEN summary generation fails after configured retries
• THEN Meeting Assistant writes a markdown failure report with a retry link to the configured summary note path

Scenario: Summary retry overwrites existing summary note

• WHEN the user triggers summary retry for a configured summary note path
• THEN Meeting Assistant resolves the linked meeting artifacts and overwrites the existing summary note with the retry result

Scenario: User notes conflict with transcript interpretation

• WHEN user-authored notes provide context that changes the interpretation of the transcript
• THEN Meeting Assistant considers those notes during summary and next-step generation