Hermes can run a cron job without ICM. It can wake up on schedule, read a source, write a report, send a message, and save the run output. It also has its own durable storage: - session history, - persistent memory, - cron definitions and run logs, - skills, - and whatever files it creates in the workspace. That is useful. But it can still leave you with a familiar mess: > a chat somewhere > a cron log somewhere else > a report with no obvious home > and an agent that needs you to explain the project again next week That is where ICM comes in. I use ICM around my Build Market Close signal cron so the **job is not the whole system**. The cron is just the heartbeat. The structure holds the memory: ```text pinned-post-curriculum-signal/ ├── CONTEXT.md ├── signal-register.md ├── reply-drafts.md ├── curriculum-outline.md └── runs/ └── YYYY-MM-DD/ └── signal-review.md ``` Here is what each part does: - **`CONTEXT.md`** tells a fresh agent what source it may read, what counts as meaningful signal, what it may write, and where it must stop for me. - **`runs/YYYY-MM-DD/`** keeps a dated receipt of every review: what the job saw, what changed, and what it deliberately did not do. - **`signal-register.md`** is the one place for real questions, objections, implementation friction, and learner needs. - **`reply-drafts.md`** holds proposed answers for review. Nothing gets posted automatically. - **`curriculum-outline.md`** turns repeated questions into a better lesson sequence instead of letting them disappear into comments. So the cron does the recurring check. But ICM makes the check **usable**. A fresh agent can open the folder and answer: 1. What is this job for? 2. What source is it allowed to use?

Hey Clief Notes fam! 👋 I'm Edgar and I'm stoked to be here. 🙋 A little about me: I'm a paediatric intensive care consultant in Glasgow. Alongside that I run a small family travel business and do Maltese consular work. 🎯 My current goal: I've used ChatGPT for over three years and got comfortable with it — but that's level one, level two. I want level three: answers that are actually personal to me, not generic. 💪 What I'm currently building/working on: Working through this keeps bombarding me with ideas — for the hospital, for work, for everyday tasks — way bigger than what I came here for. The core of it is building my second brain, to automate things I do regularly, like post creation for the travel business and other areas. I've started venturing into Hermes, set up on an old computer, and Cogni on another, connecting them through Tailscale. Structurally I started trying to build one big folder for everything; I've since moved away from that to a separate folder for each element, with a plan to integrate them later — it keeps me more focused when I'm working on one piece at a time. 🤔 My biggest struggle or question right now: Time. I wish I had more of it to really invest in this. How do I split my time between learning this properly and actually living my free time, rather than spending it sitting down reading? Let's get it! 🚀 Would love to get to know as many of you.

This podcast says yes. I can say I disagree…

#TOKEN-MAXXED

What amazes me about ICM is how different it is from traditional software. Normal software is built by a team around a fixed set of features. You get what they built, and if you need something else, you buy another tool or wait for an update. With ICM, I can build as many personal tools as I want. A workflow I repeat becomes a small system of folders and files that my AI can run. If it isn't right, I change it. If a better idea comes along, I scrap it and build a better version, all without waiting on a vendor or paying a developer. It's living software. It changes when I change, it grows as my work grows, and it's mine. An idea in my head can become a working system the same day. In ICM, your workflow is your software.