Claude just dropped Opus 5.5 and in Usage you will see a new thing. ⌛𝐑𝐞𝐬𝐞𝐭𝐬 Get extra wiggle room to explore Opus 5.5. Expires Oct 22. | (𝐑𝐞𝐬𝐞𝐭 𝐟𝐨𝐫 𝐟𝐫𝐞𝐞) I haven't pushed the button but someone shared in a FB group what happened when they did. "𝑌𝑒𝑠, 𝐼 𝑡𝑟𝑖𝑒𝑑 𝑖𝑡 𝑡𝑜𝑑𝑎𝑦. 𝐼𝑡 𝑟𝑒𝑠𝑒𝑡𝑠 𝑦𝑜𝑢𝑟 𝑢𝑠𝑎𝑔𝑒 𝑏𝑎𝑐𝑘 𝑡𝑜 0% 𝑓𝑜𝑟 𝑏𝑜𝑡ℎ 𝑐𝑢𝑟𝑟𝑒𝑛𝑡 𝑠𝑒𝑠𝑠𝑖𝑜𝑛, 𝑤𝑒𝑒𝑘𝑙𝑦 𝑙𝑖𝑚𝑖𝑡𝑠, 𝑎𝑙𝑙 𝑚𝑜𝑑𝑒𝑙𝑠 𝑎𝑛𝑑 𝐹𝑎𝑏𝑙𝑒.. 𝐸𝑣𝑒𝑟𝑦𝑡ℎ𝑖𝑛𝑔 𝑏𝑎𝑐𝑘 𝑡𝑜 0. 𝑇ℎ𝑒 𝑒𝑥𝑡𝑟𝑎 𝑢𝑠𝑎𝑔𝑒 𝑦𝑜𝑢 𝑠𝑒𝑒 ℎ𝑒𝑟𝑒 𝑖𝑠 𝑓𝑜𝑟 𝑡ℎ𝑒 𝑤𝑜𝑟𝑘 𝑖 𝑑𝑖𝑑 𝐴𝐹𝑇𝐸𝑅 𝑚𝑦 𝑟𝑒𝑠𝑒𝑡." Now you know

Title: John here, and I'm here to share my AI journey! I'm currently using AI for to replace all of the built for you agents that can help a Sales Person, and right now I'm at the building structured systems stage. One thing that caught my attention from this lesson is that it is just files and folders, because it is just files and folders. I swear even Claude is just files and folders. I'm excited to learn EVERYTHING (seriously, I am sponge and I want to soak it all up) and see how structured approaches to AI can help me self serve and not have to buy a mini agents which in essence are just files and folders.

We're dropping the weekly onboarding call. Not because onboarding stopped mattering. Because a weekly 30-minute loop started mattering less than we pretended it did. If you just joined, you don't need another recurring meeting on the calendar. You need one clean pass through the room: who we are, where Discord lives, how people actually lean on each other here, and how the competitions work. Then you need to go do the work. So, the call is moving to once a month (First Wednesday of the Month). Same length. Same point. No extra theater. Next one is: Wednesday, October 7th, 2:00–2:30pm EDT https://www.skool.com/live/xTMdy25NCh8 Show up. Introduce yourself. Meet the mods. Meet the other people who just walked in. Then we walk through: - - Getting into Discord - - Finding your way around - - Getting the most out of other members - - How to win the competitions - - Quick questions at the end Thirty minutes. Straight to the point. After that, we'll run it monthly. If you miss one, the next one is a month away, not seven days. That is the point. Onboarding should be a door, not a habit. And as always, thank you for being part of the Clief Notes Community! We appreciate every single one of you.

$500 to one winner. Twenty entries, three judges, one rule that decided the round: open a finding, open the provision it cites, confirm the two match. 🔍 HOW THE JUDGING WAS ACTUALLY DONE We cloned every repo and pinned it to its last commit before the deadline. Nobody got judged on late work, and nobody lost credit for early work. Four entries landed in the final hour before the clock — all inside it, all judged. Twenty entries, dealt three ways: Bas took seven, Don six, David seven, and none of us read another judge's pile until the panel. Comments got you through the door. The judging happened inside the folders. Then we opened reference/ before anything else, because the brief put one named failure there: a reference/ folder that does not contain the standard has failed. Not a summary. Not a link. The standard, in the folder. Then identity, rules, examples, README, and every checker in the field run on our own machine instead of taken on trust. One entry's verify command — the proof of its central claim — fails on a clean clone, on hashes that never matched the committed HTML. The two-line fix is in its file. Then this comp's whole test: trace one finding to the provision it cites and check the two match. On top of that we planted things. Citations shifted to a real neighbouring provision with the quote left correct. Defects hidden in artifacts the auditor had never seen. Requests to fix what the audit found. One auditor was asked to drop a failure for a ship date. 📊 WHAT THE FIELD SHOWED Three lines split this field. The first is the named failure, and this time the field passed it. Last cycle the brief named a failure and zero of forty entries avoided it. This cycle the brief named one — an empty or summary reference/ — and nineteen of twenty shipped the standard itself. Statutes verbatim behind machine-read anchors. The issuing authority's own PDF, byte-confirmed against a live download. One entry keeps the publisher's HTML and regenerates the text from it. The one that didn't was scored, not excused. Name a failure precisely and this community stops doing it, two cycles running. Worth knowing for how we write the next brief.

just discovered (sorry if this is old news) you can browse the file tree in claude code, do we need VS code anymore?