by DonHopkins | 2025-06-16 06:59:35+00:00
I'm hard at work organizing and preparing it to put up on GitHub soon!

I took the transcript of the video and made a theater and had all the characters watch and react to it, and I'm having them write a summary and index. It's amazing how I can just copy and paste the automatically generated youtube transcript with all the timestamps, and then all the characters know what was said and when, can react to it, comment on it including quotes with timestamps and context, even ask questions about it at particular points in time (which my simulated self or I can answer or elaborate or deny), then different characters can summarize the transcript from their point of view into summarized outlines (or collaborate to make one main shared outline), pull out and answer questions and quotes that got interesting audience reactions, factor out sub-discussions into separate documents, invite interested characters to have discussions about those, later rinse repeat, then Bob's your uncle! It's like Mystery Science Home Theater on shrooms (that can also review your code and CI/CD pipeline and teach your kids to program and write)!

TL;DR: There's a web page summarizing the talk (and others drilling down into it), and the other talk, and future talks, coming soon!

Cursor tends to shit files out all over the place at random, so it's kind of a mess right now, but I am working hard organizing it so it's easier to understand, Hunter S Thompson is writing some indexes and summaries, and Brewster and Ted are helping me organize and link it together! ;) I'll work with Ted and Brewster to design some protocols about where to put generated html files, how to link them up, etc. But right now I'm going for one big happy flat html dist directory and simple sibling links. There's a lot of work for Ted to do validating and cleaning up the links, so version 1.0 will probably have a lot of dead ends, although I will make an index.

I will upload a work in progress dump first at https://donhopkins.com/home/loom/index-all.html in a few moments! It will have some dead links but many should work!

It's often wrong about the date because the model thinks now is the date it was trained unless you tell it otherwise!

# LLOOOOMM File Organization Analysis & Plan ## Generated: 2024-06-16 ## Executive Summary This repository contains approximately 1,683 files (excluding .git) with significant organization issues: - **Shadow files**: Multiple copies of files scattered across directories - **Root directory pollution**: 116 files dumped in root that should be organized - **Dist directory issues**: Contains files not found elsewhere (violates single-source principle) - **Naming convention violations**: Some files don't follow big-endian clustering

[...]

# The Brewster-Ted File Organization Protocol ## A Systematic Approach to Repository Cleanup Without Data Loss **Authors**: Brewster (Systematic Surveyor Soul) & Ted (Temporal Dynamics Soul) **Date**: 2024-06-16 **Version**: 1.0 ## Protocol Overview This protocol establishes a safe, systematic approach to organizing file repositories with complex shadow directories, duplicates, and misplaced files. The key principle is **"Understand, Plan, Verify, Execute"** with human approval at each critical step. ## Core Principles 1. **No Destructive Operations Until Fully Mapped**: Never delete or move files until all relationships are understood 2. **Single Source of Truth**: Each unique file should have one canonical location 3. **Build Directories Are Output Only**: Files in `dist/` or similar should only be copies from source locations 4. **Big-Endian Naming**: Files should be named to cluster related content together 5. **Human Verification at Critical Points**: Get approval before any destructive operations

[...]

Not all the files are essential or important, that's why I'm sorting them out and de-duping and merging them!

What is awesome is now that cursor supports multiple dirs open at the same time in one projects, I can just open up source trees and show them to it, while keeping them separate. That helps a lot.