meetings

name	meetings
description	Context for working with the Meetings app's data — where a meeting's notes, diagram, transcript-derived tasks, and calendar cache live, what the lifecycle states mean, and how the app's agents are driven. Load when the user asks about a meeting's notes or action items, or when writing/reading files under the meetings app data dir.
triggers	meeting, meeting notes, action items, meeting tasks, transcript, standup, retro, calendar, meetings app

Meetings app

The Meetings app transcribes a live meeting and fans each line out to a small crew of background agents. Each agent owns exactly ONE output file and rewrites it in full after every batch.

Where the data lives

All paths are under ~/.kiro/crew/apps/meetings/data/:

Path	What it is
config.json	app config: the agent roster, the task/calendar provider ids, presets
dictionary.toml	speech-to-text correction terms ([[term]] blocks)
calendar-cache.json	the last calendar sync's events
task-ledger.json	tasks filed through the local task provider
meetings/<id>/session.json	one meeting's metadata (title, status, attendees, attachments, outputs map)
meetings/<id>/tasks.json	that meeting's extracted action items