User
Write something
Afternoon Tea is happening in 5 days
Pinned
I'm flattered! And it's a great breakdown!!
Someone shared that a person a reaction video was made about my method and at first I was nervous but immediately it was amazing praise. I have never met with this person one-on-one and I haven't paid them or done anything other than post my own videos ! I think they do a great job at breaking some of the concepts down. It does an amazing job of breaking down some of the logic especially some parts where I go ranting in my video he slows it down a bunch ! Much needed
Pinned
Welcome to Clief Notes. Here's where to start.
1. Watch the intro video and introduce yourself in the intro post here 2. Start with The Foundation (free course). Concepts, folder architecture, prompting framework. Everything else builds on this. 3. Check in at the bottom of each lesson. Polls, discussion posts, other members working through the same stuff. Use them. 4. When you're ready to build real things, move to Implementation Playbooks (Level 2). When you're ready to build your own tools, Building Your Stack (Level 3). 5. Post your work. Ask questions. Help others when you can. What are you here to build?
Poll
6701 members have voted
Pinned
Where've we been? Plus a quick ask
Hey all. You've probably noticed it's been quiet in here the last couple weeks, wanted to explain. We've been building something for the community, and travelling at the same time to meet with investors and a few clients. We've also been busy getting the Lyceum ready. So less posting than usual, but for a good reason!! We're announcing the thing this week, and there'll be more info on the Lyceum coming out this week too. I think a lot of you are going to be happy. We've been grinding nonstop to get this ready. Before we do, we want to hear from you. If you're Premium or VIP, what's missing for you right now and what would you want us to add? If you're not Premium or VIP yet, what would actually make you want to upgrade? Form's here, takes about two minutes: https://forms.gle/MM8PLn2f6An1dfEUA It's open until Sunday June 21. Looking forward to reading everyones answers! Back soon with the news :)
I'm giving away my OS map. The map was never the moat.
You built an agentic OS. So did the person three seats over. And when you put your architecture next to theirs, the shapes rhyme. Folders for clients. A governing layer up top. Named agents doing scoped work. An orchestrator routing it all. That's not a coincidence and it's not theft. It's convergence. Builders with no access to my internal architecture keep arriving at doctrine I already wrote down. One builder reasons their way to belief over prompting. Another builder names an agent and discovers that's the hook for giving it a soul. And another builds a routing gate to protect the signal. Different vantages, same destination. None of them copied me. They solved the same problem in their own org and ended up in the same place. I used to find that mildly surprising. Not anymore. Because if a stranger reinvents the doctrine without ever seeing it, the doctrine isn't clever positioning I invented. It's just how this actually works. Convergence is the proof that it's true. Which tells me the map was never the moat. If people can rebuild a system from a screenshot of a folder tree, then handing over the clean version costs me nothing and proves the point. So here it is. An outline of the AgencyOS map is attached to this post. Layers, agent roster, sample folder structure, and tool integrations. Take the shape. Start at Layer 1, not Layer 3. The agents are the fun part, so that's where everyone wants to start. The leverage is upstream. The belief layer governs everything the agents produce. Mine didn't come from a build sprint. It started forming in late 2023, with these ideas spoken aloud on a podcast, before any AI was in the picture. Then I spent over a year encoding that conviction into a system. Then I found ICM and ported it over. I'm still refining it. An agent I can spin up in 15 minutes. The belief layer took years because it had to exist before the machine did. Build the workforce on top of nothing and you get a fast machine with no conviction. And the belief layer is the one thing on that map you can't take from me. I can't take yours from you. You can copy the folders. You can copy the agent names. But you cannot copy what I believe into your system. I can go into my AI and ask it "what do I believe?" and it returns my truth. If you load my doctrine and ask the same question, you get what I believe. Not what YOU believe.
The Fable of Fable
A week and a half. 540 commits. I wrote almost none. The week, by the numbers: 6 tasks built overnight, every one audited by a second model, zero input from me. A knowledge graph that went 54% to 84% precise after one model swap. Then 9.5x faster in a day. A signed macOS app, 165 tests green. 600 green on the memory engine. One loop ran away. £2. The system capped it before I woke up. So I stopped checking the work. A second model marks the homework now. I wake up to finished builds I never touched. I watched my own system misbehave, and trusted the rail instead of jumping in. Five models, each on the job it does best. Fable holds the seat. The rest execute. The intelligence is the routing, not any single model. Next ARI-OS update. Full write-up: aris-space.com/documents/workflows/540-commits-one-human //A<3
The Fable of Fable
1-30 of 1,825
Clief Notes
skool.com/cliefnotes
What we give away free beats most paid courses. Build durable AI systems with a Marine vet and Edinburgh researcher. 40+ lessons, growing.
Leaderboard (30-day)
Powered by