Files
claudetools/projects
Mike Swanson 1b574caba4 radio: transcript-driven speaker name resolution (oracle)
New module src/speaker_oracle.py extracts speaker introductions from
transcripts ("let's talk to William", "we have Clay from the Nerd Junkies",
"in Tara's place, we have Clay", "thanks for the call <name>") and binds
them to non-HOST diarization turns. Pure post-pass on diarization JSONs,
no audio processing — corrects audio-only cosine errors using Mike's
deterministic on-air announcements.

Algorithm:
- Extract intros: regex patterns for caller pickups, guest intros,
  fill-in announcements, caller closes. Case-strict (rejects mid-sentence
  lowercase matches), with a blacklist of common false-positive words.
  Deduplicates same-name intros within 5s.
- Resolve speakers: for each non-HOST turn, find the LATEST opening intro
  at or before turn.start (with 8s forward tolerance for boundary slop).
  Later intros implicitly close earlier callers, so the most recent
  intro wins. No artificial lookback limit (callers can talk for 10+ min).
- Falls back to caller_close patterns within 30s after a turn ends.

Validation on 9-episode test set:
  2018-s10e18: Christopher 190s correctly named (was mislabeled "Tara")
  2012-06-09 : Kay 160s correctly named (was mislabeled "Tara")
  2015-s7e19 : Clay 45s as fillin for Tara, William 40s as caller
  2016-s8e43 : Charles 630s, Bruce 210s, John 205s — most callers named
  2017-s9e30 : Denise 295s, Tom 115s, Elaine 85s, Jeff 10s
  Many other callers across all episodes correctly named.

Remaining unnamed CO-HOST/CALLER (~5-10% of non-HOST time) are real
co-host banter or callers without explicit Mike-introductions.

benchmark.py: adds Phase 2.5 "Name Resolution" between diarization and
Q&A extraction. Prints named-speaker breakdown per episode. Doesn't
modify diarization JSONs (resolution is computed on demand).

Next step: feed named turns into qa_extractor so Q&A pairs get caller
name attached for searchability. Also: bootstrap recurring-speaker
profiles (Tara, Tony, Rob, Randall, producers) by accumulating
intro-tagged windows across the full archive once download completes.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-27 16:48:16 -07:00
..
2026-02-18 16:16:18 -07:00

ClaudeTools Active Projects

Directory: D:\ClaudeTools\projects\ Purpose: Active development projects and related conversation archives Last Updated: 2026-01-17


Overview

This directory contains active projects being developed or maintained as part of the ClaudeTools ecosystem. Unlike the imported-conversations/ directory which serves as an archive, projects here are actively worked on and may include both source code and conversation history.


Current Projects

MSP Tools (94 files, 20.1 MB)

Moved From: D:\ClaudeTools\imported-conversations\msp-tools/ Move Date: 2026-01-17 Status: Active development

Managed Service Provider (MSP) tooling and infrastructure projects, including conversation history and development artifacts.

Structure

msp-tools/
├── guru-rmm/                           # 54 files, 14 MB
│   └── [JSONL conversation files]      # RMM system development history
└── guru-connect/                       # 40 files, 6.1 MB
    └── [JSONL conversation files]      # MSP integration development history

guru-rmm (54 files, 14 MB)

Description: Remote Monitoring and Management (RMM) system development conversations

Source: C:\Users\MikeSwanson\.claude\projects\C--Users-MikeSwanson-claude-projects-gururmm-guru-rmm

Key Topics:

  • RMM system architecture
  • Monitoring solutions
  • Agent deployment
  • Infrastructure management
  • MSP automation

Project Type: MSP Infrastructure

guru-connect (40 files, 6.1 MB)

Description: MSP connectivity and integration tooling conversations

Source: C:\Users\MikeSwanson\.claude\projects\C--Users-MikeSwanson-claude-projects-guru-connect

Key Topics:

  • Integration patterns
  • API connectivity
  • Service orchestration
  • Client management
  • Cross-platform integration

Project Type: MSP Integration


File Format

All conversation files are in JSONL (JSON Lines) format:

  • Extension: .jsonl
  • Format: Each line is a valid JSON object
  • Content: Individual conversation messages from Claude
  • Encoding: UTF-8
  • Can be processed line-by-line for analysis

Usage

Accessing Project Files

# List all projects
ls -lh D:\ClaudeTools\projects\

# Browse MSP tools conversations
ls -lh D:\ClaudeTools\projects\msp-tools\guru-rmm\

# Count conversation files
find D:\ClaudeTools\projects\ -name "*.jsonl" | wc -l

# Search for specific topics
grep -r "FastAPI" D:\ClaudeTools\projects\

Integration with ClaudeTools

These conversations can be:

  • Analyzed and indexed into context recall system
  • Used to extract reusable code snippets
  • Mined for technical decisions and patterns
  • Converted into knowledge base entries
  • Referenced for similar future projects

Adding New Projects

When adding new active projects to this directory:

  1. Create a descriptive folder name (e.g., project-name/)
  2. Include conversation history if available
  3. Update this README with project details
  4. Consider creating a project-specific README
  5. Tag appropriately for context recall

  • imported-conversations/INDEX.md - Archive of all imported conversations
  • imported-conversations/IMPORT_MANIFEST.json - Detailed import metadata
  • .claude/CLAUDE.md - Main ClaudeTools project documentation
  • SESSION_STATE.md - Current project state and development history

Project Organization

Active Projects (this directory):

  • Currently under development
  • May include both code and conversation history
  • Subject to frequent updates
  • Integrated with ClaudeTools development

Archived Conversations (imported-conversations/):

  • Historical reference only
  • Read-only archive
  • Organized by project type
  • Preserved for knowledge extraction

Future Projects

This directory will grow as new projects are added. Potential additions:

  • guru-backup - Backup and recovery tooling
  • guru-dashboard - MSP management dashboard
  • integration-tools - Third-party integration utilities
  • automation-scripts - MSP automation workflows

Statistics

Current Totals:

  • Projects: 1 (msp-tools)
  • Conversation Files: 94 JSONL files
  • Total Size: 20.1 MB
  • Subcategories: 2 (guru-rmm, guru-connect)

Breakdown:

  • guru-rmm: 54 files (57.4%), 14 MB (69.7%)
  • guru-connect: 40 files (42.6%), 6.1 MB (30.3%)

Notes

  • This directory was created on 2026-01-17
  • First project (msp-tools) moved from imported-conversations archive
  • All conversation files preserved with original timestamps
  • Original source paths documented in IMPORT_MANIFEST.json

Maintained By: ClaudeTools Project Location: D:\ClaudeTools\projects
Documentation Status: Active