User
Write something
Afternoon Tea is happening in 7 days
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
6621 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 :)
Pinned
The Folder System Became My Agency
Twenty-four days ago I posted about Jake's folder system video. This is what happened next. Same foundation — markdown files, orchestration prompts, clear roles. I just kept building. Fifteen named specialists. Each one with a soul file, guardrails, and a playbook. Duke orchestrates. Cash writes. Trace pulls the data. Hank runs the financials. Clint handles the MCP integrations. Behind each one is either a human counterpart doing the real work alongside them — or a role I can't afford to hire yet. Katie who's been with me for 18 years, now has her own orchestrator running the same system. Twenty-seven client folders. Twelve live MCP integrations. One shared repo. The folder system isn't replacing my agency. It becoming my agency. Jake gave me the unlock. This is how it's going.
The Folder System Became My Agency
Hmmmm this sounds very familiar…
Google’s version if ICM? The **Open Knowledge Format (OKF)** is an open, vendor-neutral specification designed to standardize how context, metadata, and curated knowledge are stored and shared between humans and AI agents. Introduced by the Google Cloud Data Cloud team in June 2026, OKF formalizes the emerging **"LLM-wiki" pattern** (popularized by AI researcher Andrej Karpathy) into a portable, interoperable format. Instead of forcing AI agents to repeatedly search massive, disconnected text files or query proprietary vendor catalogs, OKF provides a shared standard for a living knowledge base. ### Core Technical Structure The technical shape of an OKF "bundle" is intentionally minimal and lightweight. If you have ever used tools like Obsidian, Notion, or static site generators like Hugo, the structure will look highly familiar: * **File System as Identity:** An OKF bundle is simply a directory tree of standard Markdown (.md) files. Each file represents a single unit of knowledge—called a **Concept**—which can be a physical asset (like a database table or API endpoint) or an abstract idea (like a business metric or an incident playbook). * **YAML Frontmatter:** Every Markdown file begins with a snippet of YAML configuration metadata. * **Minimal Schema Constraints:** To maintain ultimate flexibility, the specification enforces only **one** required field in the frontmatter: type. Other highly recommended (but optional) fields include title, description, resource (a unique URI pointing to the underlying asset), tags, and timestamp (ISO 8601). * **Graph via Hyperlinks:** Concepts are linked together using standard Markdown links ([Link Text](path/to/file.md)). This effectively turns a flat folder structure into a rich graph of untyped, directed relationships (e.g., *parent/child*, *depends-on*, *joins-with*). Broken links are explicitly permitted to represent knowledge gaps that haven't been written yet. ### The 3 Core Design Principles
🏁 The Archive 1.2 Check-In
After reading the full history of thinking machines: Vote below, then tell us in the comments: which part of the timeline surprised you the most?
Poll
154 members have voted
1-30 of 1,755
Clief Notes
skool.com/cliefnotes
Jake Van Clief, giving you the Cliff notes on the new AI age.
Leaderboard (30-day)
Powered by