Apparently “I’ll get those videos out soon” needed a clearer deadline. Preferably one I actually followed. 😂 Sorry these took longer than planned, everyone. The new videos for Foundation lessons 4.1–4.4 are now live! These look quite different from most of my videos. I’m trying a mix of animation, actual app screenshots, highlighted instructions, and worked examples to make the ideas easier to follow—and easier to try yourself. Here’s where to jump in: 👉 4.1: Install and First Use — 5:37 Start here if you’re still getting comfortable working with AI and local files. Grab the Foundation Practice download in Resources so you have something concrete to work with. 👉 4.2: Working With Files — 7:45 Take a few meeting notes and turn them into a decision list you can actually check. Who agreed to what? Where did that deadline come from? What’s still unanswered? 👉 4.3: Think, Then Build — 8:24 For those times when you ask AI for a whole plan before you’ve quite decided what you want. Compare your options, choose an approach, and turn it into a short brief before building. 👉 4.4: Project Instructions — 7:09 Give your AI a useful onboarding note: where to find the context, where the draft should go, and what needs checking. Includes the AGENTS.md / CLAUDE.md connection for people using Codex, Claude Code, or both. You can also follow the exercises with a regular chat tool and save the files yourself. I would love some honest feedback on this style. Does the animation help things click? Are the app screenshots useful? Is anything moving too quickly—or taking too long?

I was creating a second version of a pricing engine I built. Claude decided to deploy onto my live site, and then overwrote the local file where the latest updates for that code lived, apparently. The last commit to git was two weeks ago. So, I think I just lost 2 weeks of de-bugging code cause I didn't commit the latest version to git. Is this real? Did I just skip the most important step -- saving my work? This is a real thing, right?

I'm currently in the process of taking a lot of my data logbooks, chat exports, and reasoning traces and creating my own brain, which I'm then gonna root AI through. Essentially my own completely custom bespoke brain, which works in the same way a human brain does in regards to memory and promotion of thoughts and storage, etc. Been doing some early work on this and seen some good outputs so far. Just wanted to come on the community to see whether anyone has done similar and would kindly offer advice/be okay with me throwing questions at them in Dms ;]

Four groups working the whole weekend to create Comic Books featuring current world problems: circular economy, climate change, digital knowledge and the impact of AI in the workplace. I’m mentoring the brazilian group dealing with AI in the workplace. All four groups are live streaming to each other. Working with youth is one of the most important and fulfilling experiences.

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?