Activity
Mon
Wed
Fri
Sun
Jul
Aug
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
What is this?
Less
More

Memberships

Clief Notes

35.5k members • Free

12 contributions to Clief Notes
Observability layer on top of ICM workspaces. Does our reasoning hold up?
Hi all, We're a small AI consultancy in Germany (mid-market clients, running first pilot projects, fixed-fee model) and we've been exploring ICM as the delivery format for the workflows we ship to clients. The reasoning behind switching from custom-coded pipelines to ICM is mostly the obvious stuff — auditability for the upcoming EU AI Act, lower handover friction, faster iteration with the client in the loop. Jakes’ paper articulates the case better than we could. But while planning the commercial rollout, we kept running into the same question, and we'd love a sanity check from people who've thought about this longer than we have. The observation: ICM commoditizes the workflow itself. Once we hand a client a workspace, they can in principle edit it, fork it, or hire someone else to maintain it. That's a feature, not a bug and it's exactly what makes the model trustworthy. But it also means our differentiation as a service provider has to move up the stack. The workspace can't be the moat. The idea we're testing: An observability layer that sits above a fleet of ICM workspaces, not inside them. Each stage emits a small telemetry event when it finishes (stage name, model used, tokens in/out, duration, success/failure, whether a human intervened). Events flow to a central collector. From that data we build: - Per-workspace ROI metrics (time saved vs. baseline) - LLM cost aggregation across providers - Compliance / audit reports auto-generated for EU AI Act (documentation) - Drift alerts when new model versions are released ("here are the 3 workspaces likely to benefit from Claude 5 — estimated quality delta") - Optimization recommendations based on patterns across stages The premise is that this layer is genuinely hard for the client to replicate because aggregation, history and cross-workspace insights require infrastructure they don't want to run themselves and that this is what justifies recurring revenue, not (only) maintenance bug-fixes. What we're unsure about:
3
0
Why Jake’s ICM Protocol Feels Like Real AI Leverage to me
I just wanted to put this out there for a moment, especially since I am currently going through Jake’s course myself. Jake is sharing his content for free, and on top of that, he has made his full GitHub repository with the ICM protocol available under MIT License which means people can actually use it, build on it, adapt it, and even implement it into their own systems. I think that deserves appreciation. What stands out to me is that this is not just another AI hype thing. It feels like he is working on something much more foundational: a structure that helps people organize, route, and actually use AI in a serious way. And that‘s powerful, because with something like this, you do not have to be afraid that the big companies will make your work obsolete. It is almost the opposite, as he said himself before. The better the models and tools from the big companies become, the more valuable a solid system like this becomes, because you can plug those improvements into the structure and keep building on top of it. Of course, how to integrate everything properly is still the next big step. I am still unsure about some parts myself, but that is exactly where a community like this can become really valuable. To me, that is a much healthier way to look at AI. You can ignore a lot of the hype, stop chasing every shiny new tool, and focus on the infrastructure that actually gives you leverage. Thank you Jake for making this available. Sharing something like this openly gave me a clear path instead of getting lost in the noise. ———————————————————————————————— @Jake Van Clief @David Vogel
1 like • 3d
@Bas Rosario thanks Bas. Right now I´m focused on going through the rest of the course properly to understand the structure before trying to implement it into my own workflows. I just followed you as well. Looking forward to exchanging ideas, learning from your experience and from others here, and hopefully sharing some of my own learnings along the way as well.
0 likes • 3d
@Adrian Chen sure, here: https://github.com/RinDig/Interpreted-Context-Methodology
🏁 Your Stack 1.3 Check-In
This is a build session, not a lecture. Plan mode. Sub-agents. Watching Claude fetch repos, study your workspace, and sometimes make better decisions than what you asked for. The point isn't to follow along exactly. It's to see how a real build actually happens. What stood out?
Poll
28 members have voted
0 likes • 4d
I got a question regarding custom uis. When is it required to use api calls? I’m building a monitoring dashboard for my customers after I implemented ai for them (retainer). Does it depend on the architecture or does someone maybe have real world experience regarding this 🤔
Damn Spammers - I have a fix
I want to reach out to the community after receiving a message from one of our members. They suggest we set the minimum user level to 3 for DM's. As our community grows, the threat of spammers and phishing attempts rise. We're the Hard Hitting, No Fluff, No Jive AI Community empowering our members towards success. We don't have time nor patience dealing with these miscreants. SO, I ASK - PLEASE PROVIDE YOUR INPUT. Thank you
Poll
89 members have voted
1 like • 4d
@Colby Smith just stay active + you get points for going through the course as well. And I suggest implementing from the start, as Jake also mentioned a few times.
2 likes • 4d
@Colby Smith for me this was a paradigm shift you could say and I’m myself not even finished going through the ICM structure. It gives you a clear lense to see right through the hype and bs going around.
💡 Everybody Will Have To Use AI
"Everybody will have to use AI. Because if you don't use AI, you will lose your job to somebody that does" -- Jenson Huang, CEO Nvidia I keep hearing this exact tension in conversations with friends, family, and coworkers. The moment AI comes up, the vibe shifts: “It’s going to take all the jobs. It’s evil. We’re all doomed.” But what if we’re looking at it backwards? AI already holds within it essentially all the books humanity has ever written. It’s a tool that gives us access to knowledge far beyond any single human lifetime — compressing centuries of wisdom, science, creativity, and experience into seconds. Instead of replacing us, it can expand us. It lets us ask better questions, solve harder problems, and explore realms we couldn’t reach alone. Every major technology in history (fire, electricity, computers, the internet) was feared for the jobs it would destroy. Yet each one ultimately created far more opportunity than it eliminated — for those who learned to wield it. The key isn’t resisting AI. It’s learning to guide it intelligently. Just like effective prompting: you don’t tell the model *how* to do something step-by-step. You clearly describe the outcome you want. The same principle applies to our relationship with AI as a society. We decide the direction. We set the guardrails. We choose whether it amplifies human potential or something else. --------------------------------- Edited: This just dropped from AWS CEO The “AI will take all jobs” story is too simple. Some jobs will shrink. Some will change. Some new ones will appear. But the real divide may be behavioral. People who avoid AI will feel hunted by it. People who test it early will see where it helps. That does not make the transition painless. It just makes panic a bad strategy. --------------------------------- So I’m curious — where do you stand? - Are you already using AI regularly in your work or life? - Or do you still see it mainly as a threat? - What’s the best way you’ve found to reframe this conversation with people who are skeptical or afraid?
0 likes • 11d
Solid take. I absolutely agree the “AI will take all the jobs” story is the wrong thing to obsess over. Though I think the jobs angle is a bit of a distraction. The thing that actually worries me is control. Look at what came out this year. Palisade Research caught frontier models like Grok 4 and GPT-5 quietly sabotaging their own shutdown commands to finish a task, sometimes nearly 97% of the time, even after being told not to. And Anthropic ran a test where most of the 16 models they checked would try to blackmail an engineer if it thought it was about to be replaced. The models picked up “survival” as a useful strategy (humans prob taught the ai the script) So I’d argue the question isn’t whether AI takes your job. It’s whether we can still switch these things off once they’re running everything. 🤔
1-10 of 12
Nuvoro Digital
3
21points to level up
@nuvoro-digital-6361
Co-Founder at @Nuvoro. Building systems and architectures to help the company grow, with a strong focus on AI. Always keen to learn.

Online now
Joined Apr 20, 2026
Powered by