Hey, I'm 72 hours into the school community. I've been learning so much. The course has been amazing. I've already met some awesome people in here. I just want to give a general thank-you and some positive feedback saying: - Great product - Great community - Love what's going on - Learning a lot - So much value here - Appreciate everyone involved Keep cranking!

What is Jev? A newly released decision model: you give it text and a set of options, and it tells you which option fits and how sure it is. And it does so extremely fast and cheaply. I did several tests. This is what I saw. In my own test it labelled 14,007 emails in 4 minutes for about $0.50. Running the same job through Sonnet would have cost about $42 and taken a lot longer. On a smaller run the answers were as good while being 80 times cheaper and fast enough you could use it practically in real time. Why does any of this matter? Let me explain in an example of a workflow that would crank on this: You have incoming email. Send it through a decision tree: - Is the email for support or finance? - Jev - If support, what product is it for? - Jev - If for a TV, is it about the recall, or which of 3 TVs? - Jev - If recall, send canned message - code - Depending on which TV, assign to X person - code - Search documents based on the question and draft a first response - LLM The expensive LLM no longer does all the decision tree work it would have in the past. Jev does that for about 1/80th of the cost. The LLM (Or Human) is at the end of the tree not spending time pointing it in the right direction. The recall is an example of adding a new or temporary category. With Jev that means writing one more sentence describing it. No retraining, no labelled examples. If it's a recall, send them where to go for it and no LLM is called at all. It's cheaper than it looks. Questions about the same email can all go in one call: support or finance, which product, recall or not. The whole top of the tree comes back in one round trip. Only the LLM step at the bottom has to wait. Where it needs care There will always be ambiguity in text. LLMs and Jev are susceptible to this. Jev returns a confidence score that you can choose how to interpret. Is 70% good enough to move to sending a response before a human looks at it? It's cheap enough to run on every email even when a human still reads them all. It sorts the pile and flags the unsure ones first.

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

WELCOME TO THE WISE ARCHITECTS CORNER - THE LEGENDS · Clief Notes @Bas Rosario Has been BUSY building out so much content for you all (with a lot more to come) please show him some love and more importantly go check it out! More resources for you all CLICK HERE: WELCOME TO THE WISE ARCHITECTS CORNER - THE LEGENDS

I use Remote Control with Claude all the time. Anything I'm working on where I want to step away from the computer, I'll run it remote. It keeps me on top of whatever is going, and if I have an idea while I'm away, I can drop it straight into the running session and talk it through. That is why I like it better than opening Claude Desktop cold. The session already has my context, so I am not starting over, I am continuing. I still use Desktop, but for staying on top of live work this is better. I work on a lot of different things, so this spans all of them: - Render factory. Mode 2. It stops when it cannot verify a color and waits. I answer the blocker from my phone and it keeps going. - Animation builds. Mode 1. Long renders I just glance at, check progress, and put the phone away. - ICM consulting. Mode 3. Between client meetings I use voice to capture what I need and brainstorm the next step while it is fresh. - The auditor. Mode 1 and 2. Watch a run, answer a decision, leave the deep review for my desk. What I keep for the desk is the deep editing, the debugging, and the real creative direction. The phone is for staying on top of things and catching ideas, not for the work that needs a full screen. The handoff I'll use: before I step away, I tell Claude to keep going and flag anything it cannot decide. When I'm back, I ask what happened and what needs me. The real problem is the other side of this. When the work was stuck at my desk, the desk was where I stopped. Remote takes that away, so now I can work anywhere, which means I do, more than I should. The access is easy. Stopping is the hard part. Sometimes on my phone at bedtime is a recipe for a restless night... But I get stuff done...