Meetings¶
Extracted knowledge from team meetings, discussions, and workshops.
Purpose¶
This folder stores meeting extractions — structured summaries of knowledge captured from meetings. Raw meetings go here; refined process and technical knowledge gets extracted into the appropriate folders (company/processes/, solutions/*/processes/, tech/, etc.).
Naming Convention¶
Each meeting gets its own folder (not just a file):
YYYY-MM-DD-topic-name/
├── video.* ← Original video file (mp4, mov, etc.)
├── transcript.txt ← Meeting transcript
├── frames/ ← Auto-extracted screenshots from video
│ ├── frame-0000.png
│ ├── frame-0001.png
│ └── ...
└── extraction.md ← Structured knowledge extraction document
Example: 2026-02-18-arm-billing-process-review/
Standard Workflow: Processing a Meeting¶
Step 1: Drop Files in Root¶
Place the video file and transcript file in the root Documentation/ folder.
Step 2: Tell AI to Process¶
Say: "Process the meeting" (or similar). AI will:
- Create the meeting folder under
meetings/YYYY-MM-DD-topic/. - Move the video and transcript into it.
- Extract frames from the video (1 frame every 5–10 seconds) into
frames/usingffmpeg. - Read the full transcript AND review every extracted frame to understand both what was said and what was shown on screen.
- Create
extraction.mdfrom the meeting-extraction template. - Select key screenshots from the frames and embed them in documentation where they add clarity.
- Route extracted knowledge to the appropriate folders (processes, solutions, tech, clients).
⚠️ Nothing is ignored. Every piece of information from the transcript and every meaningful screen shown in the video must be captured — per the Core Principle in PROJECT_INSTRUCTIONS.md.
Step 3: Review & Approve¶
AI presents a summary of what was extracted and where it was placed. Review and approve before merging.
Adding a Meeting Without Video¶
If only a transcript is available (no video), the same workflow applies — just drop the transcript. The folder will not have a video.* or frames/ subfolder.
Relationship to Other Sections¶
Meetings are input. The refined output goes elsewhere:
| What Was Discussed | Extracted To |
|---|---|
| A business process | company/processes/ or solutions/*/processes/ |
| An architecture decision | tech/decisions/ |
| A client requirement | clients/[name]/requirements/ |
| A technical design | tech/architecture/ |