Kid mode 🧒
This page is Ten work products, by category. It is one of the projects Brandon built and put online. The grown-up details are below, tap Grown-up mode to read them the normal way.
Music & Audio 3
6/6 Recording Player (10 real songs)
live
A web player that re-cuts a 3 hour 47 minute 6/6 voice-memo m4a into the 10 longest real songs with stops, starts, and silence removed, 181 of 227 minutes kept. It serves all 10 mp3 files with HTTP 200 and 206 range playback, a scrub bar, and 15 second skip buttons, with songs 5 and 6 trimmed to their requested starts.
Location, next, similar, three-phase finish, channel
Location ~/Projects/drwu-htmls/public/voice-2026-06-06-songs · https://drwu-htmls.vercel.app/voice-2026-06-06-songs
Next steps Confirm the durations still read correctly after the song 5 and 6 trims and that no stray favicon 404 remains. Add per-song titles or a short label so the 10 cuts are distinguishable beyond raw length order.
Similar The companion equal-cut page at voice-2026-06-06-parts and the localhost 10-part stem player from the voice-memo-to-stem-player chat are the same recording in other forms.
Three-phase finish- Phase 1. Phase 1: locate the source m4a and the already-built player, then re-cut to the 10 longest real plays via silence detection.
- Phase 2. Phase 2: fix the .vercelignore mp3 block and the relative-path bug so the absolute audio URLs stream with 206 ranges.
- Phase 3. Phase 3: wire the scrub bar and 15 second skips, trim songs 5 and 6 to their starts, deploy, and verify 10 of 10 live.
Channel Internal listening tool for now, raw unlabelled songwriting takes. If any cut becomes a finished track it could feed a Substack audio post, but it is not sellable as-is.
BELIEVEYOUME Chord Charts and Stem Player
partial
Shiner BELIEVEYOUME chord and notation grids with a Guitar chord row and Full chord row above all three staffs and no-repeat empty cells, plus a synced chords-with-lyrics chart that renders 299 chord spans and switches per song under the player. The grids and chord chart verify live, but the stem players in this dir and the linked hfe-stems page still point at a 404 audio folder because the stem audio was never uploaded.
Location, next, similar, three-phase finish, channel
Location ~/Projects/drwu-htmls/public/believeyoume-charts · https://drwu-htmls.vercel.app/believeyoume-charts
Next steps Upload the missing part mp3 audio and the believeyoume audio folder so the dark stem players actually play, working the dark directories already listed. Redeploy and verify each stem pane serves its audio with HTTP 200.
Similar The believeyoume-chapters book and the believeyoume-keyword-index draw on the same Shiner album, and the Garbage tracks share the believeyoume-charts/stems.html player.
Three-phase finish- Phase 1. Phase 1: diagnose the dark players, confirming the pages return 200 while the audio folder 404s rather than the page itself failing.
- Phase 2. Phase 2: ship the missing part and album stem audio, removing the .vercelignore rule that excludes stems mp3.
- Phase 3. Phase 3: redeploy, verify every stem pane streams live, and re-confirm the synced chord chart still tracks each song.
Channel Sellable once the stems play, an Etsy or Gumroad listing for a per-song chord-and-stem study pack. Needs the audio shipped and a buyer-facing readme before listing.
Stray Kids Key-Match Dashboard
live
A dashboard that maps 11 per-section keys from a Stray Kids music stem and pairs each section with tiered library stem matches drawn from audio_index.json, which holds 1,284 keyed stems. It deployed to Vercel and verified HTTP 200 this session after the original split had died with an empty stems folder and was re-run into vocals plus music.
Location, next, similar, three-phase finish, channel
Location ~/Projects/drwu-htmls/public/straykids-key-match · https://drwu-htmls.vercel.app/straykids-key-match
Next steps Audition the top tier matches per section to confirm the key pairings hold by ear, not just by index. Add a quick preview or link to each matched library stem so the matches are playable from the page.
Similar It shares the section-key and library-match approach with the recap dashboard from the same chat, and feeds the same mashup intent as the loop libraries behind audio_index.json.
Three-phase finish- Phase 1. Phase 1: recover the dead Stray Kids split and re-run the first 20 minutes into vocals plus music stems.
- Phase 2. Phase 2: detect 11 section keys and query audio_index.json for tiered library matches per section.
- Phase 3. Phase 3: render the match table, deploy to Vercel, and verify HTTP 200 live.
Channel Internal mashup-sourcing tool. Could seed a Substack process post on key-matched stem selection, not directly sellable.
Books & Publishing 2
BELIEVEYOUME Deep Book Chapters
draft
Deep song-by-song chapters for the Shiner BELIEVEYOUME book in the believe-you-me close-reading register, with 5 deep draft chapters dated 2026-06-06 on disk and a live chapters index plus a Jun 4 PDF build. Five disputed song keys were resolved one at a time (Alligator G, So Far So Dm, Broken Satellites Eb, Mutiny Bb plus mixture, My Mirror Em) but every key remains verified:false awaiting the user ear-check and no chapter reached a finished fed-back state.
Location, next, similar, three-phase finish, channel
Location ~/Desktop/BandBooks/BELIEVEYOUME/_chapter_drafts · https://drwu-htmls.vercel.app/believeyoume-chapters
Next steps Run the user ear-check to clear the verified:false key flags, then carry one chapter fully through the feedback and revision loop before touching another. Merge the report-only drafts into MANUSCRIPT.md and extend the live 3-chapter showcase to all 5.
Similar It is the prose counterpart to the believeyoume-charts grids and is indexed by the believeyoume-keyword-index, and it follows the same per-song deep model as the Beach House and Hooray for Earth bandbooks.
Three-phase finish- Phase 1. Phase 1: resolve and ear-verify each disputed song key one song at a time before any chapter is called done.
- Phase 2. Phase 2: take a single chapter through a real Harmon-density draft, user feedback, and revision.
- Phase 3. Phase 3: merge finished chapters into MANUSCRIPT.md, extend the showcase to all 5, and rebuild the PDF.
Channel Sellable as a music book on Gumroad and KDP via book-publish-pipeline. Needs verified keys and finished fed-back chapters first, then a Ghost post advertising the book and a Substack excerpt.
BELIEVEYOUME Keyword Index (v1 and v2)
live
A grepable keyword index over the BELIEVEYOUME chapters, v1 covering 10 song chapters with 1,563 keywords over 201 segments with per-chapter key and BPM and disputed-key flags, and v2 folding in iximusic and ixi-generative transcripts, 42 theory books full-text, and a 126-book PDF catalog layer, tagged by lane and depth. Chapter cards open a reader modal with embedded full text for all 10 chapters, and the live URL returns 200 though the original deploy was only staged before a rate-limit cut the chat off.
Location, next, similar, three-phase finish, channel
Location ~/Projects/drwu-htmls/public/believeyoume-keyword-index · https://drwu-htmls.vercel.app/believeyoume-keyword-index
Next steps Confirm both v1 and v2 live URLs return 200 and that the 3.6 MB v2.json lazy-loads cleanly on its tab. Spot-check known-answer queries against the postings to make sure the relative-fetch fix did not break any lookups.
Similar It indexes the believeyoume-chapters text and shares the token-to-postings pattern with the bible-commentary-index and the by_song.json family, distinct from the semantic rag-query kind.
Three-phase finish- Phase 1. Phase 1: follow the grepable token-to-postings pattern and build v1 from MANUSCRIPT.md split into 10 song chapters.
- Phase 2. Phase 2: build v2 with the cross-corpus iximusic, theory-book, and PDF-catalog layers tagged by lane and depth.
- Phase 3. Phase 3: fix the relative-fetch bug, deploy both indexes, and verify the live URLs return 200.
Channel Internal research and book-support tool. Could ship as a bonus searchable companion inside the BELIEVEYOUME book product rather than a standalone sale.
TV & Reference 2
Community Season 5 Deep-Reference Guide
live
A Community Season 5 deep-reference page in the Ladders S6E1 style with 14 image-topped episode cards built from local transcripts plus Fandom stills, 42 scene photos, 346 title-first reference entries, 169 logos and posters, color-coded titles, and a per-card Films and TV banner. It verifies live, md5-matches the local build, carries a landing-index card, and had its phone image gaps fixed by switching 242 references to absolute paths.
Location, next, similar, three-phase finish, channel
Location ~/Projects/drwu-htmls/public/community-season-5 · https://drwu-htmls.vercel.app/community-season-5
Next steps Spot-check the absolute image paths on a few more devices to be sure no banner or scene still 404s at the clean URL. Consider extending the same 14-card model to the remaining seasons to complete a full-series reference set.
Similar It is the multi-episode parent of the community-s6e1-ladders and community-s6e2-lawnmower single-episode pages and overlaps the 110-episode community-guide-v3.
Three-phase finish- Phase 1. Phase 1: build 14 image cards from local transcripts and Fandom stills, folding in the Ladders S6E1 paste verbatim.
- Phase 2. Phase 2: add scene photos, title-first references, logos, color-coding, and the Films and TV banner per card.
- Phase 3. Phase 3: switch all 242 image refs to absolute paths, deploy, add the landing card, and verify live on phone width.
Channel Content piece. Strong Substack and Ghost crosspost angle as an episode-by-episode Community deep-reference series, one card per post, with the live page as the canonical hub.
Community S6E1 Ladders and S6E2 Lawnmower Pages
live
Two dedicated single-episode Community pages in the Season 5 reference style, Ladders for S6E1 and Lawnmower for S6E2, built so each flagship episode gets its own deep page. The S6E1 page verifies live with 17 images returning 200 and a landing card, and the S6E2 Lawnmower page was also built and verified live.
Location, next, similar, three-phase finish, channel
Location ~/Projects/drwu-htmls/public/community-s6e1-ladders · https://drwu-htmls.vercel.app/community-s6e1-ladders
Next steps Mirror the Season 5 absolute-path image fix on both single pages so phone rendering is bulletproof. Decide whether every remaining S6 episode gets its own page or folds back into the multi-card season model.
Similar They are the single-episode spinouts of the community-season-5 guide and a finer-grained companion to the 110-episode community-guide-v3.
Three-phase finish- Phase 1. Phase 1: build the dedicated S6E1 Ladders page in the Season 5 card style with its own images.
- Phase 2. Phase 2: build the matching S6E2 Lawnmower page on the same template.
- Phase 3. Phase 3: deploy both, add landing cards, and verify 200 with all images loading.
Channel Content. These slot directly into the Community Substack and Ghost series as standalone flagship-episode posts that link back to the Season 5 hub.
Games 1
Commander Toolbox Tracker
live
A toolbox-themed Magic the Gathering Commander life and tools tracker that carries over partner and commander-damage tracking, a real 4-stage Start Your Engines Speed counter from 0 to 4 with tap-to-rev and MAX glow, horror-creature zombie tokens with fog and lightning, and plus or minus 5 buttons with commander damage that deducts life. It deployed live to Vercel and verified HTTP 200, with the partner field, rotated-name, sound engine, and Speed pip widget all confirmed in the served markup.
Location, next, similar, three-phase finish, channel
Location ~/Projects/drwu-htmls/public/commander-toolbox · https://drwu-htmls.vercel.app/commander-toolbox
Next steps Test full multiplayer flow including 3 and 4 player tables to be sure the Speed pips and commander-damage rows behave for every seat. Add local persistence so a game in progress survives a refresh.
Similar It re-skins the earlier Speed and racing Commander tracker and is linked from the same landing index as the stem players and reference pages.
Three-phase finish- Phase 1. Phase 1: locate the origin MTG chats and build the toolbox re-skin carrying over partner and commander damage.
- Phase 2. Phase 2: rework the danger meter into a real Speed 0-4 pip widget and reskin zombies as horror creatures.
- Phase 3. Phase 3: fix the life and damage button glitches, ship live, and verify the widgets in served markup.
Channel Internal play tool, personal use at the table. Not sellable in current form given trademarked Magic the Gathering content, keep it private or share as a free hosted page.
Dashboards & Systems 1
Requests-Status and Recents Dashboards
partial
A color-coded request-audit board built from real transcript messages, 6 in place, 4 partial, 3 red, deployed and verified live at requests-status, plus a related recents dashboard upgraded so each card carries a 3-sentence work-product read, a 2-sentence next action, and a make-live button. The audit board is live, but the per-chat itemized transcript-sourced board was never built, and the recents dashboard reached 95 of 100 summaries with 26 thumbnails locally while session_fraud_check returned a HARD FAIL and the Vercel deploy stayed staged because the agent-env account block prevented a force-deploy.
Location, next, similar, three-phase finish, channel
Location ~/Projects/drwu-htmls/public/requests-status · https://drwu-htmls.vercel.app/requests-status
Next steps Resolve the session_fraud_check HARD FAIL, finish the last 5 summaries and the top-20 per-card product thumbnails, and have the user run the deploy from an account with team access since the agent env is blocked. Build the still-open per-chat itemized board and deploy it.
Similar It sits alongside the recents-cards and community-asks-by-chat dashboards and the recap-2026-06-07 board as the session self-tracking system.
Three-phase finish- Phase 1. Phase 1: extract real per-chat asks from transcripts and score each done, partial, or red.
- Phase 2. Phase 2: render the color-coded audit board and the 3-plus-2 recents cards with make-live buttons and thumbnails.
- Phase 3. Phase 3: clear the fraud-check fail, finish the last summaries and thumbnails, and have the user deploy from a team account.
Channel Internal command-and-control tool for the chat fleet, not a product. It is the system that decides what becomes sellable, not something sold itself.
Commerce 1
Books Completion Board with Channel Badges
live
A books dashboard scoring completeness of 43 books across 6 categories, each with a completeness ring, a stage label, and per-book channel badges, a big G for Gumroad, a big E for Etsy, and a ghost icon for a Ghost post, rendered solid, dashed, or faded by status with real links. The badges are wired from real channel caches (.cache_gumroad.json, etsy_listings.json, .cache_ghost.json), and the page deployed to prod and verified HTTP 200 with a landing card.
Location, next, similar, three-phase finish, channel
Location ~/Projects/drwu-htmls/public/books-board · https://drwu-htmls.vercel.app/books-board
Next steps Build the offered Substack and NFT status as its own HTML rather than the in-chat report, carrying the 4-lane plan with 0 of 4 lanes registered and the vault doc links. Keep the channel caches fresh so the G, E, and ghost badges reflect live listing state.
Similar It is the commerce control surface over every book product including believeyoume-chapters, and it shares the channel-cache wiring intent with the Etsy and Gumroad ops skills.
Three-phase finish- Phase 1. Phase 1: score 43 books into 6 categories with a completeness ring and stage label each.
- Phase 2. Phase 2: wire G, E, and ghost badges from the real channel caches, styled by status with real links.
- Phase 3. Phase 3: deploy to prod, card it on the landing index, and verify HTTP 200, then add the Substack and NFT view.
Channel This is the commerce dashboard itself, the map of which books are Etsy-ready, on Gumroad, or advertised via Ghost. Its job is to make the missing badges visible so each book gets listed and crossposted.
Ten questions, answered
Which of these 10 products are truly live versus staged, and what blocks the staged ones?
Seven verify live: the 6/6 songs player, Stray Kids key-match, Community Season 5, the S6E1 and S6E2 pages, the keyword index, the Commander toolbox, and the books board. Three are not fully shipped: the BELIEVEYOUME stem players need their audio uploaded, the book chapters need ear-verified keys and a real feedback pass, and the requests-status recents dashboard is blocked by a session_fraud_check HARD FAIL plus an agent-env account block on deploy.
What is the single most common deploy blocker across these products, and how is it fixed?
Two recurring blockers: .vercelignore excluding mp3 and stems audio so players return 200 pages with 404 audio, fixed by un-ignoring the audio and using absolute paths, and the agent-env CLI token being personal-scope so it cannot force-deploy the team-owned drwu-htmls project, fixed only by the user running the deploy from an account with team access.
Which products are actually sellable, and which are internal tools?
Sellable with work: the BELIEVEYOUME chord-and-stem study pack once audio ships, and the BELIEVEYOUME book once chapters are finished and fed back. Internal tools: the requests-status fleet dashboard, the Stray Kids key-match, the 6/6 player, and the books board which is the commerce map itself. The Commander toolbox is personal-use only because it is trademarked Magic the Gathering content.
What is the best Substack and Ghost crosspost angle for the content products?
The Community Season 5 guide and the S6E1 and S6E2 pages are the strongest crosspost lane, one episode card per Substack post with a Ghost mirror, all linking back to the live Season 5 hub. The BELIEVEYOUME book supports a Ghost post advertising the book plus a Substack excerpt of one finished song chapter.
Why did several chats falsely report done, and what now prevents it?
Chats copied each chat's own transcript words instead of opening the actual artifact, the exact trap the fraud gate exists to catch. done_claim_gate.py was built, self-tested, wired into settings.json, and proven by firing on the assistant itself, so no done, complete, or shipped claim passes without opening the artifact or running session_fraud_check that turn.
What has to happen before the BELIEVEYOUME book can be published?
Run the user ear-check to clear the verified:false flags on all 5 disputed keys, then carry one chapter fully through draft, feedback, and revision before starting the next per the one-at-a-time rule. Merge the report-only drafts into MANUSCRIPT.md, extend the live showcase from 3 chapters to 5, rebuild the PDF, then route through book-publish-pipeline to Gumroad and KDP.
How is the permanent HTML tree kept healthy as these products multiply?
Every product lives under ~/Projects/drwu-htmls/public/<dir> and ships to drwu-htmls.vercel.app forever, carded on the landing index which links only directories. The maintenance rules are absolute image paths so clean URLs render on phone, no audio left behind .vercelignore, and a 200 plus content verification after each deploy rather than trusting the build.
Which products share a source and should be cross-linked or bundled?
The believeyoume-charts grids, the believeyoume-chapters book, the believeyoume-keyword-index, and the Shiner stem player all draw on the same album and should cross-link as one BELIEVEYOUME hub, with the keyword index shipped as a searchable bonus inside the book. The Community Season 5 guide, the S6E1 and S6E2 pages, and community-guide-v3 should share a Community nav.
What is the maintenance burden of the live dashboards, and is it durable?
The fleet dashboards depend on channel caches (.cache_gumroad.json, etsy_listings.json, .cache_ghost.json) and on keep-alive and rename or tag launchd jobs that were made incremental to run a 4 second tick. The durable risk is the keep-alive needing an Accessibility grant the user must approve and the rename having no API, so those stay session-fragile until the user grants permission.
If only one product could be pushed to revenue this week, which and how?
The BELIEVEYOUME chord-and-stem study pack, because the grids and synced chord chart already verify live and only the stem audio upload blocks it. Ship the missing audio, add a buyer-facing readme, package per-song, and list on Etsy or Gumroad, using the books board badges to confirm the listing went live.