You watch a lot of content in this space. Demos, walkthroughs, systems builds, production case studies. Some of it is genuinely valuable. Most of it evaporates. A summary gives you a shorter version of what was said. What you want to know is: is there anything here worth keeping, what's the mechanism behind it, and what would you build differently knowing it? What this does: YouTube URL in. Claude extracts 3-7 discrete claims worth keeping. Each one gets: - Concept - the core assertion - Mechanism - the causal explanation (the most important field) - So what - what you'd build or decide differently - Open questions - what this raises but doesn't answer Appended to a local markdown log you own. Real example, from Curtis Hays's Collideascope OS walkthrough: Concept: ICM deploys fast only when the doctrine layer is already documented. The folder structure is the last step, not the first. Mechanism: Curtis had 8 months of prior work before touching the ICM - documented beliefs, brand voice, organizational why/how/what, all in markdown. He brought that corpus in and said "organize it using this structure." The system came together quickly because the content existed. Without pre-existing doctrine, the ICM produces mechanics without a belief layer. So what: Before building the folder structure, ask: is the doctrine layer written down? Cloning a blueprint without existing beliefs produces a technically correct but contextually empty system. That's not in any summary. That comes from extraction. How repo works: Primary mode uses Claude Code with your existing subscription. No API key needed.Three components, each with one job: fetch_ transcript.py gets the transcript, prompts/extract_default.md tells Claude what to look for, CONTEXT.md tells Claude Code how to run the workflow. The prompt file is the thing to edit. The scripts are plumbing.

Dang it @Curtis Hays , your post "Left Of Bang: Smart Discipline or Over Engineering" got me thinking. Your brother's journey from Marine to counterterrorism specialist, drawing from Left of Bang, nails a timeless truth: the real game is won (or lost) in the moments before the explosion, the ambush, or the breakdown. Training that only prepares you for "right of bang" leaves you playing catch-up in survival mode. Staying left means cultivating pattern recognition, baseline awareness, and the discipline to act on subtle anomalies. That's not paranoia—it's empowered foresight. This resonates deeply when we map it onto structured systems like ICM (Interpreted Context Methodology) and PMS (Preventative Maintenance Systems). ICM: INTERPRETED CONTEXT AS YOUR PERSONAL COMBAT PROFILER ICM turns chaotic information flows into an interpretable, staged architecture—numbered folders, focused markdown contexts, and clear role definitions for AI (or human) agents. Instead of overwhelming the system (or yourself) with everything at once, you engineer context deliberately: isolate what matters for the current stage, reduce noise, and build repeatable workflows that let you "read the room" or the data before anomalies compound. In Left of Bang terms, ICM is your Combat Hunter toolkit for the information battlefield. It helps you establish baselines (normal behavior in your projects, markets, or personal life), spot clusters of cues that don't fit, and intervene early. No more reactive firefighting after the "bang" of a failed launch, missed opportunity, or workflow collapse. It's smart discipline: structured enough to scale, flexible enough to adapt. PMS: PREVENTATIVE MAINTENANCE FOR LIFE, WORK, AND SYSTEMS PMS isn't just for ships or machinery—it's the operational heartbeat of staying left of bang in the physical and systemic world. Schedule the inspections, lubrication, and calibrations before the breakdown. Track intervals, document baselines, and act on early wear indicators.