I'm currently using AI for learning & understanding different topics, and right now I'm at the copy-paste / projects stage. I'm excited to learn structure/infrastructure and see how structured approaches to AI can help me build autonomous systems.

Hey Clief Notes fam! 👋 I'm Tyler, and I'm stoked to be here. 💪 What I'm currently building/working on: I'm excited to learn & master structure/infrastructure, AI & agents. Let's get it! 🚀

📣 Update (10/8/26): Comp 14 Rules Added Current Challenge: Competition 14 The Challenge 💪 - Build a specialist of your choosing, run a test, AND run a control to compare it against. Rules & submissions 🗒️ - https://www.skool.com/cliefnotes/weekly-comp-14-the-control?p=378868a2 Good luck everyone! --- What this thread is: I’ve seen a number of people either not know competitions are going on or know how to find them so here is a quick single source thread where you can get to them all. I’ll keep this updated as new challenges are released. See the current challenge as well as all past challenges below! Format for community challenges: https://www.skool.com/cliefnotes/how-competitions-work-from-now-on?p=84912d60 Weekly leaderboard competition: Alongside the biweekly challenges, there is a weekly leaderboard challenge where the member at the top of the 7 day rolling leaderboard wins a free upgrade to their membership. This winner is announced on Mondays typically. @Joshua Hubbard has gone another step further and created a thread linking to all competition entries. Link here: https://www.skool.com/cliefnotes/the-competition-archive-every-entry-every-week-every-link?p=bd752987 --- Past Challenges Competition 1 The Challenge 💪 - Build a brand voice document for a pet grooming business Rules & submissions 🗒️ - https://www.skool.com/cliefnotes/first-ever-weekly-competition-is-live?p=90f50bf9 Results🏆 - https://www.skool.com/cliefnotes/weekly-comp-1-winner-ian-barriopedro?p=0501b57e Competition 2 The Challenge 💪 - Build an artifact of a financial advisor client intake system

This community is large and it moves fast. That's the good part and it's also the problem: valuable posts get buried, the same questions get re-asked instead of found, and spammers show up wherever there's an audience. These guidelines are what keeps the room worth showing up to. Read them once. You won't need them again, because most of this is what you'd do anyway. New here? Start with Jake's welcome post and the Foundation course. This post is about how we behave, not where to begin. 1. Build in public. Post the thing while it's half working. A half-finished build is more useful to everyone else than the polished writeup you'll never get around to, and you'll get corrected before you've spent a week going the wrong way. 2. Teach what you learn. The day you figure something out is the day you're best at explaining it, because you still remember exactly what confused you. A month later you've forgotten the hard part and your explanation gets worse. If you cracked something this week, that's a post. Nobody has to earn the right to ask a question here, but this place only works because people come back and answer them once they can. 3. Ask good questions. Specific beats polite. "How should I structure this?" gets three vague answers. "I have a 40 file client folder, the model keeps loading the wrong context file, here's my CLAUDE.md" gets a real one. Say what you tried, what happened, and what you expected instead. A more in depth guide: https://dontasktoask.com The flip side of this: "Anyone here?", "Help please", and one line questions with no context may get removed. Not to be harsh, but because nobody can answer them. 4. Give credit. If you built on someone's skill, template, folder structure or comment, tag them. It costs you nothing and it's the reason people keep publishing their work here instead of keeping it. A lot of the best material in this community started as somebody's reply on somebody else's post.

If you wanted a seat in the Lyceum and it didn't work out, this one's for you!! The live seats are closed. But every session, every office hour and every breakout room is recorded, and as of today those recordings are open to this community. Here's what you'd be catching up on. We're five weeks in. About 130 people, four rooms. And for the first three weeks, nobody was allowed to build. No folders, no agents, no code. Just three questions: 1. What is a program, really? (Instructions, something that runs them, and a state. You've been writing them for years.) 2. Who receives what you build, and what actually lands on their side? 3. What's the question you least want to be asked? If you can't answer "why would I use yours instead of Claude," you don't build yet. It annoyed people. It also worked: - Chad's own AI told him "that's four things, give me one." He picked one and landed a paid pilot three weeks later. - Musa threw out two months of work and a 70-page manual in seven hours, because he couldn't say what his customers were receiving. The new version is what they actually wanted. - Emma, a landscaper who calls herself "super not techie," walked out of one 28-minute drop-in saying "I'm converted." Last weekend we started building. Session 4 was about where your data has to live so other people's AI can reach it. Short version: you don't need a second brain, you need to know where your data needs to be. $495 for all of it. Lifetime access, and everything through Demo Day gets added as it happens. https://whop.com/checkout/plan_m5UlsmU3I5cOl $995 for the recordings plus a seat in the December certification exam, the same exam the cohort takes. https://whop.com/checkout/plan_OGmJR4j1JtS88 Both come with early access to EdubaWare and locked-in founders' pricing for when it starts charging. The live seat was $4,750. This price ends Sunday, October 25, when Sprint 2 does.