Hi everyone. Is there any rule of thumb on how many words in every layer of an ICM workflow? Im trying to narrow it down in a large repo with many canonical things that apply for every workflow and I have 1263 words in layer 0 and a context routing of 871 words.

I have nibbled at the edge of this idea and it fits in with ICM well. I am working on tools for it but I think the concept can help others. Quick test: define "AP", "POF", and "Gate". If you said Accounts Payable, Proof of Funds, and a logic gate — reasonable, and wrong. I work in parking. Here those mean Anti-Passback (stops a ticket getting passed back to a second car), Pay-on-Foot (the payment kiosk), and the barrier arm at a lane. Every industry has these. A new hire learns them in their first month. An LLM never does. It just picks the wrong meaning with full confidence and keeps moving. So instead of trying to make the model smarter, make documents smarter. A human maintains a glossary file. Term, what it means, a "not this" line (AP is NOT Accounts Payable), aliases people actually type, and a link to the deeper doc. An agent reads an incoming document (support ticket, email, whatever), finds which glossary terms actually appear in it, and prepends a header defining just those terms. Expand it to include routing tags. Dispatch, Billing, etc. Now every incoming support ticket has the information for the next agent to use. The glossary has who it goes to, or a link to the known troubleshooting process to write up an automated response. This can be done with a lighter model. This document is the router. The document contains the information to understand the document. It is also self-auditable. If no header, something is broken. If it's missing a routing tag because the agent failed to classify, it goes to a place for a human to look at it. Then the human can refine the glossary. I am calling it "Gloss". Would love to hear your thoughts, ideas, and questions.

Hey everyone, I'm new here and really want to learn how to use AI in my business. I've watched Jake videos on folders and the setup, but honestly, I'm overwhelmed. There's so much information and I'm not connecting the dots yet. I learn best when things are broken down into simple steps. Could someone point me to: - The absolute basics to start with (like "do this first, then this") - A simple first project I can complete to understand how it works - Which parts I can ignore for now as a beginner I'm committed to learning this, but I need a clearer starting point. Any guidance would be really appreciated. Thanks for understanding!