Let's fix it. Look, sales isn't something you can perfect without doing it and it's definitely not a "script". It's a framework. Just like the things you build...there are steps to follow. ICM is a framework. There are a few moments that really matter in your framework in sales. 1) The trust frame is a sentence (and the story of a lady patching in her son from jail during a sales call) 2) The only time "no" means "yes" 3) The presentation is a map + calculator not the whizbang 4) Temperature testing = the truth 5) The moment you shut up buttercup 6) The 3 ways to handle any and all objections I think @Darren Soares is the only one who's went through the free sales training in the classroom. Maybe since it's on the Tubez, you will too? Always got your back, RyMac P.S. The same training broken down into micro lessons is here in the classroom. P.P.S BMC' App is getting really close to launching. Premium, VIP, and people on the waiting list get the beta deal I talk about on the page. There's an example of me live sparring there, too. P.P.P.S Fred Built The Perfect ICM Builder just in case you haven't seent' it.

Getting a little closer... Feeling a little dangerousy' right around the corner.

You can have no coding knowledge or you could be the best programmer in the world. You will learn a lot from this video. 4R Audit Video Great work Ry. Truly appreciate you!

Tough exam, lot's of reparation to get it ... Proud of myself, wanted to share it with the group. If someone is studying for this, and needs help, I'm glad to give you advice. Also happy to help if you're stuck with implementation.. just reach out. @Ry Mac .. I did it!!

Strands Harness does not help "ATSW_OS" because the system's architecture explicitly rejects the use of traditional multi-agent orchestration frameworks. Instead of relying on an external framework to manage agents, "ATSW_OS" uses the Interpretable Context Methodology (ICM). This method completely replaces framework-level orchestration with a standard filesystem structure. - Filesystem as Orchestrator: In "ATSW_OS", there is no orchestration framework installed; the folder structure itself is the program. Numbered folders dictate the execution order, and plain markdown files carry the prompts and instructions for each stage. - Handoffs and Context: Rather than relying on a framework for memory and context passing, intermediate work is handed off between stages using output/ directories. The output of one folder simply becomes the input for the next. - Avoiding Engineering Overhead: For sequential workflows that require a human to review the output at each step, agentic frameworks introduce unnecessary engineering complexity. By using a filesystem, every intermediate output is a plain text file that a human can easily read, edit, and save without needing to edit code or redeploy a framework. Because the folders handle stage sequencing and local Python scripts handle the mechanical tasks, an external agent framework like Strands Harness is entirely unnecessary for the stack.