Hand a cheap model a task and it re-reads everything, or confabulates the one ID that actually mattered. So I pack it instead. A Context Pack is one file: exact needles (ids, paths, values) kept verbatim, the bulk gisted, sized to half the model's window. Workers read what matters and re-fetch the rest. A manager routes each task to the cheapest Claude tier that can do it, on your subscription, never metered. Small jobs go direct. Big ones fan out under a cheap large-context model that reassembles the result. I shipped this repo by pointing the tool at itself. It said "12 ok". I believed it only after diffing every file, because a workflow once told me "ok" for work it never ran. Verify the behaviour, not the tally. Repo, MIT, built with Claude: github.com/PUSHINGSQUARES/Build Deep-dive + a fidget to try: aris-space.com/documents/dispatch/context-pack-dispatch //A<3

I've been enjoying my ICM builds and systems. They are living and breathing and battle-tested. Now I've hit the point where I want to scale and expand them more than I practically can. The limiting factor? Me and my taste. My taste... well there's plenty of posts in here that will give you a pretty good indication of it. Human in the loop. Augment that human at every turn rather than cutting them out. My judgement where it matters. Guardrails and governance and stakes considered from the outset - as @Gabriel Azoulay put it, build the refusal and verification first and the rest will follow. (Yes, I've mangled it, it's not a quote, but the sentiment is there nonetheless). And in the middle of all of this, I've had a few ideas that have come in together. @Curtis Hays has agents in his system who sort requirements and building within his system. @Ari Evergreen has been inspiring me to think about where model vs model loops could play a piece in this picture to actually move things further along with my taste still driving all of the outcomes. And somehow this mashed up together into the following. @Bas Rosario taught us about how ICM was like baking a cake. And that moving from a workflow to a workspace was going from having a system that baked a cake to building a bakery. I can bake cakes. I have not one but two working bakeries. Now I need a construction crew. Not any construction crew - ones who know my bakeries and my taste and follow those to the letter. They don't suggest things that aren't compatible with my industrial grade ovens. They know what to do with my delicate equipment - nothing that is hand wash only is being shoved in the dishwasher by this crew! They understand that in my bakeries, my rules govern; and they honour and enforce that. Enter a new workspace where tools are made and bakeries are built. If you want to see them, glimpses of what these look like are already present in the week 8 competition builds - Chalky PRD (now 01 Chalky) and Architectural Thinking Partner (now 02 ATP).

This is a follow up on this post: https://www.skool.com/cliefnotes/building-the-construction-crew-who-build-bakeries?p=020aae63 The work order stage is built. Total spend: 5% of my weekly Fable usage. I had budgeted 10-15%. This means that we’re straight on to building the next stage in the chain - the dispatch and oversight. And, just like each stage, it’s running through the construction crew that have been built. The build trend is already speaking for itself. More updates to come - Fable has me on a clock. 🕰️