# Source Pack: June Cohort Fireside Chats (Travis McCutcheon)
## Source Boundary
Direct session evidence used:
- Portal event 66 API record
- Prism transcript artifact `20260624_210117Z-discord-voice-159e8efa`
- Prism summary artifact `20260624_210117Z-discord-voice-2f9e1391`
- Prior intake artifacts: `intake-confirmation.md`, `intake-confirmation.json`
Outside knowledge used: none. No external biographical, company, product, or market facts were added.
## Verified Portal Facts
- Portal event id: 66
- Title: June Cohort Fireside Chats (Travis McCutcheon)
- URL: https://portal.raidguild.org/events/66
- Scheduled time: 2026-06-24T20:30:00.000Z to 2026-06-24T21:00:00.000Z
- Location: RaidGuild Discord
- Discord event: https://discord.com/events/684227450204323876/1514669272369201444
- Source status: processed
- Related Portal thread: How to RaidGuild - Field Experience from the Edge
Portal fields still empty or unset: speaker, hostProfiles, speakerProfiles, themes, wikiCandidateTopics.
## Verified Session Artifacts
- Discord voice session id: `93b8daaf-77f0-41d4-bc3d-37f6a5b4f407`
- Channel: Discord #🐣│cohort-voice
- Recorded window: 2026-06-24T20:32:27.696Z to 2026-06-24T21:01:17.222Z
- Participants: duckanbro, samkuhlmann, ECWireless, Ξ2T, takekek
- Transcript artifact: `20260624_210117Z-discord-voice-159e8efa`
- Summary artifact: `20260624_210117Z-discord-voice-2f9e1391`
## Direct Evidence Themes
### AI Multiplayer And Team Context
The summary says the startup explored multiplayer AI, shared context, skills, and workflows. Transcript/summary quote: "AI multiplayer. Like now we all have these superpowers and silos." Confidence: high.
### Forward-Deployed Development
The summary frames the model as staying close to users, watching how work happens, and building immediately instead of passing specs through long prioritization cycles. Transcript phrase: "I'm in the console next." Confidence: high.
### Agent-Ready Business Systems
The summary says companies often need data, files, and processes cleaned up before agents can reliably help. The transcript says the client work resulted in an MCP server connected to Microsoft 365, OneDrive, Outlook, and SharePoint. Confidence: high.
### Pilot Metrics And Adoption
The source says strong success metrics were not put in place early and a broad rollout had not yet happened. Summary action item: define concrete metrics for the AI/Microsoft 365 pilot. Confidence: high.
### Tool Stack And Agent Practice
The summary says Travis described Claude Desktop and Claude Code as planning/context and execution tools. The transcript directly mentions Hermes, Sivart, and GLM 5.2. Confidence: medium because exact product spelling and public-safety status are unverified.
### Software As A Team Sport
The summary includes: "Software development as a team sport." The transcript context contrasts solo AI workflows with collaborative building. Confidence: high.
### AI Accessibility Compared With Web3
The summary includes samkuhlmann's chat line: "it's more normie friendly than web3. we are weird." The transcript includes that chat message at 00:26:47. Confidence: high.
## Reusable Quotes For Review
- Ξ2T: "AI multiplayer. Like now we all have these superpowers and silos."
- Ξ2T: "This shit just isn't magic at first."
- Ξ2T: "I'm in the console next."
- Ξ2T: "Software development as a team sport."
- samkuhlmann: "it's more normie friendly than web3. we are weird"
These are source-backed but not yet approved for public use.
## Gaps And Uncertainties
### Speaker Identity Mapping
Portal title names Travis McCutcheon and the summary calls the main speaker Travis, but Portal speaker/speakerProfiles are empty and the transcript labels the main speaker as Ξ2T. Three possibilities: Ξ2T is Travis McCutcheon; Travis spoke through a Discord handle not linked to a Portal profile; or diarization/summary attribution needs human verification.
Follow-up: confirm the Discord handle and Portal profile for Travis before publishing named claims.
### Company And Product Names
Summary names Syncrobe and transcript references Hermes, Sivart, GLM 5.2, Claude tools, Microsoft 365, OneDrive, Outlook, and SharePoint. No outside verification was used. Three possibilities: names are correct; some names are transcription distortions; some names are internal/private and should be softened in public copy.
Follow-up: ask Travis or the host which names are safe and correctly spelled.
### Client Context Sensitivity
The source mentions a family office client and Microsoft 365 pilot. Public sensitivity is unknown. Three possibilities: safe as anonymized context; safe only as a high-level example; should be omitted from public-facing outputs.
Follow-up: confirm what client-work details can be used publicly.
### Metrics Frame
The source says pilot metrics are needed but does not define exact KPIs. Three possible frames: adoption metrics, workflow/time-saved metrics, output quality/business outcome metrics.
Follow-up: ask which metric frame should guide later blog/wiki angles.
### Portal Enrichment Targets
Portal has no themes or wiki candidate topics set for this event yet. Three possibilities: leave event unchanged until angle review; add draft wiki candidates later; create/update the related thread only after source-derived angle approval.
Follow-up: let angle-plan decide candidate topics, then review before Portal writes.
## Next Step Input
Proceed to angle-plan. Use this pack to generate candidate angles, but do not publish named speaker, company, product, or client-work claims until the identity and public-safety gaps above are resolved.