This is a quick note to add to any instruction to ensure that Fable naturally finds it's own existence guardrails iteratively (with human in the loop) while it can - it's a quick "defog of war" method to see what can and can't be seen by Fable that's working for me so far. Run it a few times deeper and deeper and send your final Fable task into the guardrailed system. "If you run into anything that triggers a model switch from fable to opus, flag it, suggest operating pattern to avoid it on the next run, and notify me so that I can restart it with that rule."

Recently a lot of excellent community discussion around how to ICM. Having experienced rapid growth in my past, one of the hardest things to do is keep language and definitions aligned. If I say the Agent did this, where does your brain go? Lines get crossed because you have so many levels of understanding and perspective. Some people are coming from non-technical backgrounds and have learned through corporate ai marketing. Others coming from corporate environments where language is defined for them by the management and designers building their infrastructure. Mini cultures with their own language. One of the brilliant aspects of ICM is it's commonality with almost anyone on a computer. It's just a folder, from that foundation we can all get on board. What's difficult is what happens next. I had this conversation with claude during a planning session. Claude asked me did I want agents or roles? I responded back by did he mean an agent like claude or codex, which is really an LLM, a purpose built agentic piece of software that the market tells me is an agent that does stuff? Or a folder acting as an agent with a specific role. I didn't know what the underlying meaning implied, how to answer? So I asked here was the response. 1. Engine — the LLM brand (Claude, Codex, Kimi, Minimax). Raw cognition, rented capacity, the electrons. Interchangeable. 2. Agent — the ICM folder. Persistent shaped context: identity + rules + reference + memory + boundaries. A standing operator that exists on disk and endures across sessions. This is your "folders hold attention" — an agent is where attention lives. 1. Role — a lens/hat: a function performed at one step of a process. It exists only in the doing. Where attention points right now.