Transcript Processing Standard
Philosophy
Transcripts are mined, not summarized. A rich 1-hour meeting yields 10+ ideas, multiple frameworks, a dozen decisions, and state changes across multiple projects.
Required Role
When processing transcripts, operate as the Knowledge Architect:
- Process with exhaustive depth
- Mine every valuable insight, idea, philosophy, decision, and status update
- Missing content is unacceptable
What to Extract
Explicit Content
- Feature ideas (“wouldn’t it be cool if…“)
- Project sparks (new tool concepts)
- Frameworks (mental models, principles)
- Philosophies (team beliefs, working principles)
- Decisions (explicit choices made)
- Status updates (“X is now live”)
- Action items (tasks assigned)
- Blockers (what prevents progress)
Implicit Content
- Ideas embedded in problems (“we don’t have X” → X is an idea)
- Philosophies in asides (“we always say…“)
- Decisions by non-decision (“let’s not wait…“)
Output Standards
For a 1hr+ meeting, expect minimum:
- 1 archived transcript in
05_Archive/Transcripts/ - 1 comprehensive meeting summary
- 5+ idea notes in relevant
Ideas/folders - 2+ framework/philosophy captures
- All mentioned project hubs updated
Quality Gates
Red flags (processing incomplete):
- Summary shorter than 1 page for hour+ meeting
- Only 1-2 ideas from brainstorming discussion
- No state changes from status-heavy meeting