hey everyone, I'm turning 40 this months and are having a bit of a mid-life crisis 😁 which is good because I start thinking about what I have achieved and what is yet to come. also about family, health and everything really... the big thing for me is also AI and especially what we are learning here in this community. honestly, it still blows my mind what I have seen, witnessed and develop here since I joined the community in March this year, is, truly incredible. my own journey with AI through this space and engagements here have also exceeded my own expectations. since I'm relatively new to AI, although my first machine learning project was back in 2015 teaching a software the Ge'ez (old Ethiopian language) alphabet und how to read ancient manuscripts, I work as AI Officer at NPO and humanitarian aid organisation. this is wild to me, because 2,5 year ago I was unemployed (almost 2 years in total). so not sure where all of this heading and what's possible. turning 40 years yet make an important impact for me. not sure if most people in here are above or below 40...? but for those who turned 40, how was it for you?

Hey Clief Notes fam! 👋 I'm Victor and I'm stoked to be here. 🙋 A little about me: Just someone looking to learn more. 🎯 My current goal: Setting up some automation tools to help me achieve my goals while keeping myself free for creative work. 💪 What I'm currently building/working on: Setting up a local LLM and workflow on my MacBook. 🤔 My biggest struggle or question right now: What to eventually do in this space. I am not sure I have a solution or service to offer. Let's get it! 🚀

I have further experimented with animations and storytelling and got draft that I really like. the audio is my cloned German voice (english planned). really amazing what is happening and how AI revoked my old filmmaker/storytelling interests - and of course it is all done with ICM method and the remotion.dev set up.

🎁 $1,000 IN EDUBAWARE CREDITS 🎁 One winner takes it. 📋THE CHALLENGE Build a folder. Then prove it earns its place. Every comp so far has assumed the folder helps. Nobody has had to show it. This week you run a control: same model, same questions, no folder. Then the same questions with the folder. You commit both runs, raw, and you report what actually changed. This week's deliverable is a folder plus the evidence that it beats no folder. 🎯PICK YOUR FOLDER Any specialist you want. Coach, researcher, editor, auditor, translator, something new. The folder is not the test. The test is the test. Pick a domain where you can write five to ten questions a stranger could grade. Questions with checkable answers. If the only way to judge the answer is taste, the control will not tell you anything. A few sparks: - A folder that answers questions about one codebase you can pin in the repo - A folder that answers policy questions against one document you ship in reference/ - A folder that handles one support category against a shipped FAQ - A folder that answers questions about one dataset you include - A folder that converts one input shape, graded against a spec in reference/ The pattern is the same every time. The answers have to live somewhere a mod can check. 🔥 THE ANGLE THIS WEEK Last comp was The Translator. The test was three runs on the same input to see if the shape held. The Control points that same test at the folder itself. In the Cartographer round, Marcelo ran a control before he changed a single card. Same model, same four questions, no map. It got the answers right, slower and with more reading, and it found two things his cards understated. He fixed both. Then after he rebuilt the map, the model read six files instead of ten and quoted the README's own rule as its reason for skipping the code. That is the only comp result all year that told us something we did not already believe. This week everyone runs one. Three things separate a real control from a demo:

📦 EVERY ENTRANT GETS A FEEDBACK FILE 📦 🔍 HOW WE READ THESE We cloned every repo and pinned it to its last commit before the deadline. Seventeen of eighteen had nothing after it. Then we did what the rubric asked, for every entry. We read the schema in reference/ first. We found the rule for a field with no source. We ran your folder three times: on the input you shipped, on that input with something the schema needs cut out, and on that input with irrelevant material stapled on. Then we picked five claims from your own output and found where each one came from in the input. That trace table is in your file. Five claims, five locations. You can see exactly where we looked and what we found. Every entrant shipped an input. That alone made this the most checkable field we have judged. 📚 WHAT THE FIELD TAUGHT Three lines split eighteen builds: ✅ The degraded test broke almost nobody. The rubric expected most entries to fail here, handing back a shorter document when the input ran short. Seventeen of eighteen kept the full shape and marked the gap. Name the hard case precisely and this community builds for it. ✅ The one way to lose held for seventeen of eighteen. The brief named it: put something in the output that was not in the input. We traced five claims in every entrant's own committed output. One entry had it. The near misses all had the same shape. The quote was real, and the value, the link or the sentence written next to it was not checked. Sixteen entries ship a checker, and we planted a fault in every one. Fourteen caught it by name. The two that missed had that same blind spot. ✅ Drop nothing turned into keep everything. Seven builds have a contract that cannot ignore anything, so a stapled email became a compliance row, a speaker, or an allergen. Every leaked line was quoted and cited, so nothing was invented. It was still noise on the page. Coverage and noise rejection pull in opposite directions, and only a few builds wrote down which one wins.