This is happening to me all the time now, and either I wasn't catching it before, or something changed. I do realize that this might be operator error, which is why I'm asking for help. Have you been able to wrangle the "hallucinations" which let's just call them what they are, fiction and/or lies. One request: please don't blindly copy/paste outputs if you run this post with AI. I'm not saying don't do that, just politely asking if you could give it a read and if the output makes sense to you, drop it in the comments. Here are two examples: --------------- Example #1 --------------- Had Claude draft this up, and in the process it created a rule for it without me asking. What's frustrating about this is that now I have to read through another markdown file to ensure accuracy and consistency to how I do things, and I still have doubt that it'll even honor the rule it wrote for itself. The admission: 1. What I did. Credited three voice rules to NAME, and wrote that he flagged them in a comment on your Voiceprint LinkedIn post. The comment doesn't exist. I checked his comments feed, his posts, Gmail, Slack, and Skool. The earliest trace is my own /session capture on 8/29, with nothing upstream of it. I can't reconstruct where the name came from, and I didn't invent a story for how I invented it. 2. It happened twice. Yesterday I told you the attribution had reached the public repo. It hadn't. I repeated the session log's "added all three to..." line without opening the file. That second one is the more useful failure, because it shows the actual mechanism: an unsourced sentence in a workspace file gets read as a source by whoever comes next, including me. 3. Six guardrails were loaded and all six missed. constraints.md bans invented attributions by name. Its final scan says every claim traces to a source. Shared rule 0 forces that file to load every EOD run. Root map rule 5 says verify the live system. Digirol bans "I think" and demands a real search before calling a contact new.

@Ry Mac has been absolutely amazing this week! From the continuous engagement to the value packed videos he's been posting, a position well deserved. ⏰ The 7-day clock resets. Next Monday someone new takes the top spot. 🎯 How it works: - 📝 Post things worth reading - 💬 Help people in the comments - 🛠️ Share what you're building, what's working, what's breaking - ❤️ Engage with what others are putting out there The leaderboard tracks all of it. 🎁 The prize, depending on where you're at: 🆓 Free member? You get lifetime Premium, free ⭐ Already Premium? We convert your Premium so you stop paying 👑 Already VIP? We convert your VIP so you stop paying Either way, you stop paying. Amazing value you're sharing Ry, congrats!

Hey Clief Notes fam! 👋 I'm Raph and I'm stoked to be here. (Yes, this is the template from clief AI) 🙋 A little about me: Twenty+ years in enterprise B2B. Held different roles in ops, sales, marketing in different seniority levels. 🎯 My current goal: A portable and fully agentic workflow that parses, cleans, organizes company data. A full restaging process. 💪 What I'm currently building/working on: Org knowledge and OS that follows ICM architecture. 🤔 My biggest struggle or question right now: I just want to keep building. I've been in front of people for decades and I'm quite spent.. I now find joy in working behind the scene. The casual talks, ideations, and chats are ok (especially about AI lol), but the selling part of it all burned me out. Is this something that others feel too?

📣 Update (9/7/26): Comp 12 Rules Added --- 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 --- Current Challenge: Competition 12 The Challenge 💪 - Build an auditor that reviews something against a defined standard. Rules & submissions 🗒️ - https://www.skool.com/cliefnotes/weekly-comp-11-the-auditor?p=1d0eb170 Good luck everyone! --- 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.