🎁 $1,000 IN EDUBAWARE CREDITS 🎁 One winner takes it. 📋 THE CHALLENGE Build a folder-based AI translator that takes one kind of work and turns it into another kind of work. Same shape in, same shape out, every time. Not a summarizer. Not a writer. A converter with a contract. This week's deliverable is one translator folder that someone could drop into a Claude project, feed it the input it expects, and get back the output it promises. Every time. Without surprises. 🎯 PICK YOUR CONVERSION The conversion is yours. Pick one you do by hand right now and hate. A few sparks to get you thinking: - 📞 Sales call transcript → CRM notes in your team's exact fields - 📝 Long-form essay → LinkedIn carousel, slide by slide - 🎙️ Meeting recording → product requirements doc - 🔬 Research paper → investor one-pager - 🐛 Bug report thread → Jira ticket with repro steps - 📧 Customer email → support ticket with severity and category - 📊 Spreadsheet export → weekly status update - 📖 Interview transcript → case study draft - 🧾 Receipt photos described in text → expense report line items - 📋 Discovery call notes → SOW first draft The more locked-down the output, the better. "Turns notes into a doc" is not a contract. "Turns discovery call notes into a five-section SOW where section 3 is always scope exclusions" is. 🔥 THE ANGLE THIS WEEK Last comp was The Auditor. Every finding cited a provision so a reader could open the standard and check. The comp before that was The Cartographer. Every card cited a file and a line so a reader could open the source and check. The Translator is the same discipline, one more time. Every line in the output traces to a line in the input. ↔️ A translator has three properties that a summarizer does not: 1. The output has a fixed shape. Same fields, same order, same format, regardless of what the input looked like. If the input was messy, the output is still clean. If the input was short, the output still has every field, marked empty where there was nothing to fill it.

Congrats to Clief Notes and everyone who showed up for this Week 12 Auditor Comp. This was the first peer-to-peer reviewed competition, and it set a real standard. The work was judged by people who actually know the space, and that made the whole thing feel earned, not performative. It was a genuine pleasure working with @Don Roy and @Bas Rosario . They are true leaders in this community — sharp, fair, and deeply respected. Judging alongside them was an honor, and their care for the process showed in every decision. To the competitors: thank you for putting your work in front of peers and trusting the process. That takes guts. To Clief Notes @Jake Van Clief : thank you for building something new instead of copying what already exists. This is how a community levels up. Proud to have been part of the first one. Here’s to many more.

$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.

A few people here have said the hard part is turning what they know about AI into work somebody will pay for. I can only help with half of that. I run an IT services business, so when a client shows an interest I already have the relationship and the trust. I can't tell you how to get the first conversation. I can tell you what I do once I'm in it. This is what happened this morning. All my clients are small businesses. Before we talk about any project, I tell them where I stand on AI. The wording below is close to what I actually said. 1️⃣ AI as it exists right now has been incredibly overhyped, particularly for small businesses. At least half the time, and probably a lot more, AI is not the solution you're looking for. 2️⃣ At the same time it has been undersold. The mad proposals for second brains and vibe-coded replacements for SAP have hidden the really easy wins that are available right now with off-the-shelf LLMs. 3️⃣ An "agent", or a swarm of them, is probably not what you want or need. 4️⃣ It is not a pool to dive into. It's a potentially scalding bath. Dip your toes in, adjust the temperature, and go in a bit further each time. That is the safe, low-cost way to build experience and end up with AI-augmented systems that actually work. 5️⃣ Doing number 4 puts you well ahead of your competitors. While they spend money on big AI projects and get burned, you build solid systems that move the business forward. Nobody has ever pushed back on this. If anything it relaxes the room, because most small business owners have already been pitched the opposite and didn't believe it. 🚨What we did next🚨 We spent about an hour going through one particularly painful, mostly manual process they run approximately ten times every day. I recorded the whole meeting. Afterwards I fed the transcript into Claude and asked it for a process map. The first draft was almost right. 🪙The link below is an anonymised version of a later draft. Company, people and email addresses are made up; the process is real.

💰 $500 CASH 💰 One winner takes it. 📋 THE CHALLENGE Build a folder-based AI auditor that checks something against a specific standard and reports where it falls short. Not your opinion of what's good. An actual standard that exists in the world. This week's deliverable is one auditor folder that someone could drop into a Claude project and use to check their work against the rules of their industry. 🎯 PICK YOUR STANDARD The standard is yours. Pick one that actually exists. Pick one you could point someone to. A few sparks to get you thinking: - ♿ WCAG 2.1 AA accessibility audit of a web page - 🔒 GDPR audit of a privacy policy or data flow - 📋 SOC 2 readiness audit of a security policy doc - 📄 Contract audit against standard SaaS data-handling clauses - 🏗️ Code audit against a specific style guide (PEP 8, Airbnb JS, Google Java) - 🏥 HIPAA audit of a patient intake process - ♻️ Brand compliance audit against a published brand guideline - 📊 Financial model audit against FAST modeling standards - 🎓 Grant proposal audit against a specific foundation's published criteria - 📱 App Store submission audit against Apple's review guidelines - 🧾 Invoice audit against a client's stated payment terms The more specific the standard, the better. "Audits for quality" is not a standard. "Audits a React component against the WCAG 2.1 AA success criteria" is. 🔥 THE ANGLE THIS WEEK Last comp was The Cartographer. Forty of you built maps where every card cited a file and a line, and we cloned the territory to check the cards against source. The ones that held up were the ones a stranger could verify. The Auditor is that same discipline pointed at a rulebook instead of a codebase. ⚖️ Every finding cites a provision the way every card cited a line. The standard is the territory. The audit is the map of where the artifact sits against it. Three things separate a real audit from an opinion: 1. The standard is external and citable. Your auditor should be able to say "this fails WCAG 2.1 success criterion 1.4.3" not "this contrast looks low to me."