Activity
Mon
Wed
Fri
Sun
Aug
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
What is this?
Less
More
Owned by Jayden
Where entrepreneurs learn business structure — the real fundamentals behind every successful company.
Memberships
AI Automation Society
425.5k members • Free
Clief Notes
42.1k members • Free
17 contributions to Clief Notes
👑
⭐
2h •
🏆 COMP #8 RESULTS: THE WILDCARD 🏆
📦 AND SOMETHING NEW: EVERY ENTRANT GETS A FEEDBACK FILE 📦 🔍 WHAT WE DID DIFFERENTLY THIS TIME Every submission was cloned at the exact commit that was public when we read it, and read file by file. The brief. The identity. The rules. The reference layer. The code. Where a repo made a claim we could check, we checked it. Arithmetic recomputed by hand. Sample photos opened and compared against the outputs that cited them. Files diffed. Self-tests traced. Thirty-two repos, read at the code/word level. And one lens over everything, because it's the lens this whole community is built on: does the build keep the human's judgment where it pays and put the deterministic work in code, where it can't hallucinate? 📦 THE FEEDBACK PACKAGE This is the new thing, and it's for everyone not just the podium. 📦 COMP #8: THE WILDCARD - The Vault Every entrant gets a markdown file. Three parts: 1️⃣ The read. What your build actually is, and the strongest thing in it cited to your own files. Rule numbers. Function names. Your own examples. 2️⃣ One push. The single change that most improves your build. Not a list. One. 3️⃣ An idea worth naming something original in YOUR build, credited to you, that the rest of the community is told to take from. Plus links to the builds your feedback points at. Nobody walks out of this comp empty-handed. Thirty-two builds, thirty-two named ideas. The roster alone is worth the download. 📍 The package + the full write-up (what held up, what was missed) live in the new Feedback module: 📦 COMP #8: THE WILDCARD - The Vault 📚 WHAT THE FIELD TAUGHT Three lines split thirty-two repos: ✅ Enforcement. A must in a markdown file is a request. A must in code is a constraint. (That line is from one of your repos. It's in the package. Go find whose.) ✅ Evidence. The builds that shipped receipts of a REAL run transcripts, dated logs, before-and-after fixes read differently every single time.
1 like • 2h
Congrats everyone who placed
1 like • 1h
@Jake Van Clief amazing. I don’t feel bad just more work to do. My goal is to be in your cohort.
👑
⭐
7d •
Connection Hub: 📣 Marketing & Agencies
Intros for The Connection Hub - The Vault 👤 Who I am: (name + where you're based) 🛠️ What I actually do: (the specific work — not "I'm in real estate" but "I run a 3-agent team doing residential resale in Austin") 🤖 What I'm building with AI right now: (your current project, workflow, or the thing you're stuck on) 🎯 What I'm looking for connection-wise: (pick one or two) 💡 Someone who's solved [X] 🤝 A collaborator / accountability partner 👀 Just here to learn from people in my field 🧰 Trading workflows & systems 📬 Best way to reach me: (DM here / comment / link)
0 likes • 6d
@Danny Garcia hey Danny. I texted you
0 likes • 6d
@Kevin Williams hey I actually have had Claude running my ads for a while, if you would like some help would love to connect +17207128689
12d •
Need Help Guys! Thanks in Advance
Hey everyone! I’m going on vacation soon but still need to keep working while I’m away. What’s the best way to move everything from my desktop to the cloud so I can access all of my client projects, files, and development environment from my laptop? I’m using Claude Code and Cloud Code Dispatch, so I’d love to hear how others have set up a cloud-based workflow that’s reliable and easy to use while traveling. Any recommendations or tips would be greatly appreciated!
2 likes • 12d
@Bas Rosario Can you point me to any instructions or tutorials
2 likes • 11d
@Alex Brown much love. I knew this group had me covered
23d •
🏆 WEEKLY COMP #8: THE WILDCARD 🏆
🎟️ PRIZE: FREE SEAT IN THE LYCEUM 🎟️ Pick your cohort. Technical, Business, or Creator. Your call. ---- 📋 THE CHALLENGE You are the client this week. No fictional Marcus. No fictional Sarah. No fictional Devon. Pick a real problem in your own life or work. Build the folder-based specialist you wish you had. This is the capstone of Month 2. The challenge flips. Instead of building for someone else, you write your own brief and solve it for yourself. ---- 🎯 THE TWIST The hard part isn't building. The hard part is scoping. Picking the right problem is harder than solving the wrong one. Most people pick problems that are too small or too vague. The skill this week is treating yourself like a real client. Be specific about what's broken. Be specific about what you need. Don't pick "I want to be more productive." Pick "I waste two hours every Sunday night writing the same kind of LinkedIn carousel posts and I need a folder that handles 80% of the draft work so I can focus on the hook and the visuals." That's a real brief. Specific problem. Specific scope. Specific desired output. ---- 🗂️ TWO DELIVERABLES THIS WEEK This is the only week with two pieces: 1️⃣ Your own client brief. 250 words or less. Describe the problem you're solving for yourself. Treat yourself like a real client. What's broken? What have you already tried? What do you need? 2️⃣ The folder system that solves it. Same structure as every week: - 📄 identity.md - 📐 rules.md - 💬 examples.md - 📚 reference/ - 📖 README.md Your brief lives at the top of the repo as brief.md so judges can read it before they look at the folder. ---- 🔥 THE ANGLE THIS WEEK Anyone can follow a brief. Writing your own, then solving it, then shipping it as a usable folder is a portfolio piece that demonstrates judgment, not just execution. This is the skill that separates "AI hobbyist" from "AI builder." Anyone can prompt their way through a problem someone else handed them. Scoping a problem, designing the solution, and shipping it as a system is what real work looks like. 💪
7 likes • 15d
Oh my gosh, I got things mixed up. I thought it was two weeks to build now because we're now doing it biweekly. Man, I need to actually read the dates now. I had a lot of confidence in myself this week. It kind of really messed up my mood, but here we go. I really want to get connected with Jake. That's my goal here, and if Jake at least notices my work, that's a win for me. Relay is a folder-based studio operator. Clients ask in plain language, a 2-person team runs every account from one board, and an AI wired to the same files clears the routine work and escalates what needs a human. The agent is an ICM folder — and the studio it runs is a folder too. ▶ Live demo (no signup): https://relay-playroom.vercel.app 📁 Repo (brief.md at the top): https://github.com/griffainai/relay It opens with a 60-second pitch, walks the whole thing, then shows real Claude running the folder on your own key—not a mockup. The brief was treated honestly. I'm my own client. Relay is an IP-safe slice of the real "command center" my co-founder and I built to run 8 companies out of markdown. Work was scattered across Slack, docs, and eight folders; we tried the enterprise-platform trap and scrapped it. The real problem was never features — it was operating discipline. So we built the opposite of a platform: a folder. The ICM part I'm proud of — it's folder-as-agent, twice: - The agent is a folder—a Map (CLAUDE.md) routes to Rooms (CONTEXT.md, per stage) and Skills (loaded only when a task needs one). - The studio it runs is also a folder—one directory per client; every request, deliverable, and decision is a markdown file. - - The path through the folders is the logic rules. md (the Lane Protocol — 🟢 clear / 🟡 hold / 🔴 escalate) literally runs it. The thesis. The platform is the structure—that's the easy part, and I gave it away. The quality of what the AI produces tracks the depth of the folder you build: the context, the standards, the taste, the examples of "good." Claude is only ever as good as the folder you hand it. That craft is the methodology—it's what this community teaches.
👑
⭐
27d •
WEEK 7 COMP⚙️ THE OPERATOR — RESULTS
(and a small change to how we run these) Hello everyone!! 👋 First, the honest bit. This one is landing later than Monday, and on purpose. Two things got us here. One, a lot more of you are submitting now. If I am going to really sit with every entry and give it a proper look, a weekend is not enough. This round I went through all of them, watched the videos, opened the repos, the full pass. That takes time and I would rather do it right than rush it. Two, I could feel a few of you running hot. Weekly is a sprint, and burnout was starting to creep in for some. So we are moving to bi-weekly. More room to build, more room to breathe, and the time for me to actually review the work the way it deserves. 🎥 Quick word on the videos. They were a step up this round. Some of the animated walkthroughs and live demos were a genuine pleasure to watch, and yes, I weigh them. A clean demo that shows the thing actually working makes a real difference. However I don't want that to ALWAYS be a requirement. Also you will notice the Heavy hitters that you usually see up here are not currently, some posted late and I decided to let the new entries and first timers also have a chance as well! But certainly, check the original post as every submission has something for you to learn from : 💰 Competition 7 ➖➖➖ 🛠️ A FEW THAT STOOD OUT (in no order, and if you didn't make it, it doesn't mean yours wasn't great) The Pipeline Operator — @Jayden Forshee Runs a whole sales pipeline. Paste a lead and it grades it, writes the outreach, and moves the card itself. The live board where you watch cards move on their own, sat right next to a normal chatbot, was one of the clearest ways anyone has shown what an operator actually is. https://github.com/griffainai/studio-pipeline-operator Board: https://pipeline-operator.vercel.app/board
6 likes • 27d
Congrats @Gabriel very useful product. I’m coming for number 1 next time ! 😉❤️
1-10 of 17
@jayden-forshee-3287
Substrate — ontological audits + AI operating architecture for founder-led businesses · Built on ICM
Active 1h ago
Joined May 6, 2026
Dallas
Powered by