🎟️ PRIZE: FREE SEAT IN THE LYCEUM 🎟️ Pick your cohort. Technical, Business, or Creator. Your call. ---- 🇺🇸 Quick note first. This post is going up Today because we took Memorial Day off yesterday. To keep things fair, you've got until Sunday May 31st at 12:00 PM EST to submit. Same week of build time, just shifted. ---- 📋 THE CHALLENGE Build a folder-based AI researcher for a specific topic or industry. You pick the domain. This week's deliverable is one researcher folder that someone could drop into a Claude project and use as their personal research partner for whatever domain you've built it for. ---- 🎯 PICK YOUR DOMAIN The domain is yours. Pick something specific. Pick something you'd actually use. A few sparks to get you thinking: - 🏦 M&A activity in one industry (fintech, healthcare, defense) - ⚖️ Court cases in one area of law (employment, IP, immigration) - 🧬 Scientific research on one health condition or treatment - 🏘️ Real estate market dynamics in one city or asset class - 🥊 Competitive intelligence for one product category - 📜 Historical research on one period, place, or movement - 📚 Academic literature in one specific subfield - 📋 Regulatory developments in one sector - 📰 Journalism research on one beat (climate tech, AI policy, biotech funding) The more specific, the better. "Research assistant" is too broad. "M&A research analyst for early-stage fintech deals in the US and Europe" is right. ---- 🗂️ THE METHODOLOGY If this is your first comp, welcome. Here's what you need to know: This week (and every week) you're learning interpretable context methodology. Folders as architecture. Each file does one job well. Your researcher is a folder with five things: - 📄 identity.md (who the researcher is, what domain they cover) - 📐 rules.md (how they research) - 💬 examples.md (what good looks like) - 📚 reference/ (frameworks, source lists, key concepts) - 📖 README.md (how to use it)

to be honest ive been dealing with an insane amount of imposter syndrome i don't think i'm the only one and i think that's why i wanted to write this. I used AI for the first time 13 months ago. At the time I was doing online auctioning for pokemon cards on whatnot, and heard that AI could code scripts. perfect, i thought... We were having a problem with meat-brains not being able to clear bid slots fast enough for a game we created. but a simple grease monkey script i wrote fixed everything and i'm not joking when i say this: it changed my life. I immediately understood the gravity of what i was using. not because i knew exactly where it was all going but because i felt it from there i did what any sane person would do. content farm then i started using it to mix music then i started using it to sell web services then i started using it to make animations voice controlled screen edits for the live streams then the vibe-code bug hit i built janky memory systems terrible harnesses fugly orchestrations i ran the gambit i was obsessed i stayed up to date on every model and every tool i remember when skills dropped and i understood the implications but the understanding was ephemeral a feeling in my gut that i couldn't articulate until i stumbled upon Jake and suddenly this system started connecting the dots it made that feeling tangible it gave the thoughts a home to be refined but the reason i'm writing this is this: ai is destroying the barrier of entry for so many things that's fine and dandy but if you're already excellent at something it can truly change the entire way you work and i think that’s the part i keep coming back to in preparation for a meeting with jake to build a workflow i really have been trying to get my ducks in a row not just “what can i automate” but where does automation actually fit into my musical workflow where does it help where does it get in the way where am i over-engineering where am i avoiding the dirt