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.