I ran Opus 4.8 at max thinking effort this week. The finding isn't "it's smarter." The finding is where that thinking goes, and what it needs before it pays off. Here's what nobody tells you about high-effort reasoning. It only thrives when there's something to reason over. Drop a max-thinking model into an empty context and you get a slow, confident guess. Drop it into a workspace you've actually built, the briefs, the memory, the prior decisions, the evidence, and it does something different. It digs. Three things I noticed. 1. Context is the unlock, not the model. The jump from 4.7 to 4.8 wasn't really "smarter weights." It was better use of the room you give it. The intelligence isn't in the model. It's in the environment you set up before you ask the question. 2. The slow part is the feature. Thinking times went up a lot. That felt like a cost until I read what it was doing. It wasn't stalling. It was hunting through the context for evidence before answering. Judge the reasoning, not the clock. The pause is the work. 3. It reasons evidence-first. This is the real shift. 4.8 goes looking for proof in your context before it commits to an answer. 4.7 tended to answer first, then justify. Working backwards from evidence instead of forwards from a guess changes the quality of everything downstream. It's the best reasoning I've seen from any model, and it only shows up when the evidence is there to find. So the lesson isn't "turn thinking up." Effort and context are a pair. Max effort on a thin context is an expensive guess. Max effort on a built-out workspace is a researcher. Build the room before you ask the question. Full deep-dive available at: https://www.aris-space.com/documents/workspaces/max-thinking-empty-room ASIDE —> After @Ruben Aguirre 's great post earlier today. If you highlight over any AI terminology, it will give you a plain English explanation of what that is. And there's also a glossary at the bottom to help. <3

You've built the system. Prompts are dialed. Agents have context. Files are clean. Output is fast. But something is still off. The system is capable. It just doesn't always know what it should be doing. That's not a prompting problem. That's a governance problem. SOPs are essential. I'm not arguing against them. But SOPs teach how. How to write. How to analyze. How to research, package, and present work. They are instructions about execution. What SOPs cannot tell you is whether. Whether this deliverable should exist at all. Whether this approach fits the client's actual position. Whether the work is technically correct and strategically wrong. That's the gap. A skilled agent can still make the wrong move beautifully. Governance is the "whether" function. The layer that says no. Not "no, that's technically incorrect." The SOP catches that. "No, that follows the brief, but the brief is the problem." "No, that's on-brand and it'll cause drift six weeks from now." "No, we don't ship that until someone's asked whether this should exist." SOPs taught the system how to write, analyze, research, summarize, and package work. SOPs could not tell the system whether the work should exist in the first place. That's not an execution problem. No amount of better prompts closes it. Governance is a different layer with a different job. I didn't figure this out in advance. The same client calls kept surfacing the same rule. Coherence before creativity. Diagnosis before deployment. Meaning before media. Revenue before reach. I made those calls so many times that I stopped deciding and started following an order. That's the line where instinct quietly becomes doctrine. These themes kept showing up in my podcast, on team calls, and on client calls. I started documenting them. Then I built a layer to enforce them. I called it the Governor. It was running in ChatGPT before I had anything I'd call an OS. When I later imported everything into ICM's file and folder system, the architecture finally gave it a proper home. But the judgment came first.