Transcript Summaries

This directory contains detailed summaries of conversations and meetings. These are NOT raw transcripts but structured summaries that capture key insights, quotes, and action items from conversations.

File Naming Convention

Transcript files should be named using the following pattern: YYYY-MM-DD-[descriptive-name].md

For example:

• 2025-10-26-gary-isaiah-spiritual-business-strategy.md
• 2025-04-13-wilson-fong-call.md

Ideal Transcript Summary Template

---
id: "YYYY-MM-DD-[primary-person]-[topic-slug]"
title: "[Full Descriptive Title of Conversation]"
date: "YYYY-MM-DD"
participants: ["Person 1", "Person 2 (Implied Listener)"]
location: "[Physical Location or Call Type]"
---

# Call/Meeting Summary: [Brief Topic Description]

## Overview
[2-3 sentence high-level summary of the conversation's purpose and main outcomes]

## Key Topics Discussed (from [Speaker's] perspective)

### [Major Topic 1]
- **[Subtopic/Key Point]:** [Detailed explanation with context]
- **[Another Key Point]:** [Supporting details and observations]
- [Additional bullet points capturing important details, quotes, or insights]

### [Major Topic 2]
- **[Key Insight]:** Direct quotes should be included in quotation marks
- **[Strategic Direction]:** [Explanation of decisions or plans made]
- [Continue with relevant details]

### [Additional Topics as needed]
[Continue the same structure for all major discussion points]

## Key Quotes
[Optional section for particularly important or memorable direct quotes]
- "[Exact quote that captures essential insight]"
- "[Another significant statement]"

## Action Items / Takeaways
- [Specific action item or decision made]
- [Key insight or learning that will influence future actions]
- [Next steps or follow-up items]

## [Optional: Special Context Section]
[For conversations with special significance, add sections like:]
- Ministry Philosophy
- Strategic Framework
- Relationship Dynamics
- Business Model Discussion

Processing Guidelines

When Creating Summaries:

1. Focus on substance over verbatim transcription - Capture the essence and key insights rather than every word
2. Include direct quotes for particularly important or characteristic statements
3. Organize by themes rather than chronologically when it makes sense
4. Note implied context - Since many recordings capture only one side of conversations, infer and note the other party's likely contributions
5. Extract actionable insights - Clearly identify decisions made, next steps, and strategic directions

Key Elements to Capture:

• Relationship dynamics - How people relate to each other and evolving relationships
• Strategic decisions - Business, ministry, or personal strategic choices
• Spiritual insights - Faith-related discussions and theological perspectives
• Professional developments - Career moves, business opportunities, partnerships
• Personal growth - Character development, mindset shifts, life lessons
• Specific assignments or advice - Direct counsel given or received

Formatting Best Practices:

• Use bold for emphasis on key concepts or speakers
• Use italics sparingly for subtle emphasis
• Include bullet points for better readability
• Create clear section headers for easy navigation
• Add frontmatter for searchability and organization

Frontmatter Schema

Every transcript must include these frontmatter fields:

Field	Required	Format	Description
id	Yes	YYYY-MM-DD-[person]-[topic]	Unique identifier for cross-referencing from relationship files
title	No	String	Full descriptive title
date	Yes	YYYY-MM-DD	Date of conversation
participants	Yes	Array of strings	All participants in the conversation
related_people	Yes	Array of strings	Relationship file slugs (e.g., ["mike-ajouz", "santiago-montoya"])
location	No	String	Physical location or "Phone Call", "Video Call", etc.

ID Format

The id field enables efficient cross-referencing between transcripts and relationship files:

YYYY-MM-DD-[person(s)]-[topic-slug]

Single-person or clear primary subject:

• 2025-08-19-mike-ajouz-christian-business
• 2025-12-17-mike-ajouz-truth-platform

Multi-person meetings (2-3 people): Include all names, ordered alphabetically or by importance:

• 2025-10-15-alice-chen-bob-smith-funding-strategy
• 2025-09-01-mike-ajouz-santiago-montoya-theology

Group meetings (4+ people): Use a group descriptor instead of names:

• 2025-11-20-austin-founders-dinner
• 2025-08-05-christofuture-board-meeting

The ID should be:

• Lowercase with hyphens (no spaces or special characters)
• Concise but descriptive (2-4 words for topic)
• Unique across all transcripts

Note: The same transcript ID should appear in each participant's relationship file under their Transcripts table, so agents can find it from any person's profile.

Note on Privacy

These summaries may contain sensitive personal and business information. They should be treated as confidential documentation of private conversations.