Activity
Mon
Wed
Fri
Sun
Jun
Jul
Aug
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
What is this?
Less
More

Memberships

Clief Notes

29k members • Free

23 contributions to Clief Notes
🏁 Foundations 2.6 Check-In
You just saw how video production turns into code. Vote below, then tell us in the comments: what is one repetitive creative task in your work that could become a pipeline?
Poll
415 members have voted
0 likes • 8h
@Beatrice Olsson I welcome the conversation! 😊 My clients are currently in the service industry, I work with them to organize their businesses. Building CRMs, CMS, Agentic and non Agentic workflows which in turn helps them to organize, categorize, cleanup and manage their data and daily business tasks. (Sorry if that sounded like a pitch!) The software, systems, and solutions I design are done so with humans in mind, I am neurodivergent and I am an advocate for universal design and accessibility. I tinker a lot, I built my own version of a second brain. I called it DREAMS - Deep Retention Encoding Ai Memory System, along side a Dashboard called DeJaVu which allows you to view the data/memories within the system. - DREAMS = Deep Retention & Encoding Al Memory System — an AI-collaborator memory substrate modeled on hippocampal-style consolidation, designed for cross-session continuity (and eventually cross-agent shared brain via MCP per Plan 6.2), Architecture, based on what I've seen this session: - Hippocampal-style two-tier. short-term buffer → consolidation→ long-term memory (LTM). Buffer items expire if not consolidated; consolidation promotes by score gate (memories below threshold silently SKIP — Bas hit this Session 40 attempt-1 at score 0.44, attempt-2 at 0.56 promoted). - Episodic + semantic hybrid: each memory carries content + vector embedding (HuggingFace MiniLM, eager-warmup at FastAP! startup) + emotional weight + created at + type. - Associative graph: memories link to each other via cosine similarity over time, building an association layer (3471 associations as of Session 41 baseline). Recall traverses the graph, not just nearest-neighbor. - Pinned anchors: high-importance memories stay in LTM - regardless of decay (23 pinned currently — identity, cultural rules, substrate findings, people, validation moments). - Encrypted at rest: envelope encryption (AES-256|GCM with AAD = tenant_id: memory_1d) + per-memory wrapped DEK + 32-byte master KEK at -/dreams-keys/local-kek - that's Plan 6.1, shipped Sessions 37-40, all 315+ memories now envelope-encrypted, - Decay + reinforcement: reinforce endpoint exists to bump weight on recall; pinned items skip decay. - MCP-accessible: served as MCP tool so Claude (any instance) can store_memory / recall / etc. directly.
0 likes • 4m
I love this perspective, innovation in AI is about people learning about, adapting to, and adopting Artificial Intelligence into their daily lives to empower and unlock their own human potential. Joining communities like this one help people see that! I’m glad you are in the community! If you ever want to chat about AI shoot me a message!
Unable to Purchase VIP Subscription
Hey has anyone else had trouble purchasing the subscription? I tried both google pay and the card option. Both were blocked on my end. Any help would be much appreciated. Thanks!
0 likes • 2h
I’m always happy to help out here as well! I have been building alone for awhile and I have been looking for a community. This community definitely has a great culture and I am grateful to be a part of it 😊
1 like • 1h
@Kevin Carrasco thank you 🙏 I know the site needs a face lift but it serves its purpose. A lot of good information on there. My hope it to get it to a place that makes it a true community resource, free, relevant and genuinely a stepping stone to better understanding!
The Blueprint for a Global AI Finance Hub: My "North Star" Structure
Even before the meetings happen, preparation is everything. I’ve been brainstorming how to take the principles we learn here and scale them for a global corporation (14,000 employees, 72 countries). This is the "North Star" for my journey toward becoming an AI Finance Manager. It’s a technical skeleton that ensures security, scalability, and—most importantly—the K.I.S.S. (Keep It Simple Stupid) model for the end-user. The Infrastructure (The Engine Room) Using the folder structure we’ve mastered, I’ve mapped out how a global hub would actually look "under the hood":Plaintext/ ├── CLAUDE.md # The Master Router (Direct OData Logic) ├── /identity # ACCESS CONTROL GATE │ ├── global_admins.md # Full access (Admin level) │ ├── DK.md # Validated users for Denmark │ └── [70+ countries].md # Global validation files ├── /library # THE COMMAND CATALOG │ ├── /global # Standard tools (e.g., /extract_ledger) │ └── /local # Country-specific tools (e.g., /dk_vat_report) ├── /core-logic # THE ENGINE ROOM │ ├── date_parser.md # Translates "MMYY" into OData parameters │ └── odata_templates.md # Master OData entity mapping ├── /countries # LOCAL CONTEXT & AUDIT │ └── /DK │ ├── audit-log.md # Record: Date | User | Command | Status │ └── local_settings.md # Local Legal Entity IDs / Currencies ├── /technical # SYSTEM RELIABILITY │ ├── mcp_config.md # OData read-only parameters │ └── health_check.md # System status triggers └── /schemas # EXCEL TEMPLATES └── ledger_standard.xlsx # Raw data structure The User Journey: From Teams to "Done" I want a user (let’s call him Lars) to get what he needs in under 60 seconds without ever touching a complex ERP menu. 1. The Request: Lars types /dk_vat_report 0126 in Microsoft Teams. 2. The Gatekeeper: The system checks /identity/DK.md. Lars is validated. 3. The Health Check: The system pings the MCP (Model Context Protocol). Connection is green. 4. The Data Pull: The AI uses the date_parser to see that 0126 means January 2026. It reaches directly into D365 via OData. 5. Delivery: The AI maps the data into a clean Excel template and uploads it to the chat. 6. Audit: The system silently logs the action for compliance.
0 likes • 1h
Incredible @Allan Durhuus 🔥 this is very well put together. You are doing amazing things! 👏
The Asgardian Council
🔥 16 saves. 1 day. 3 AI voices cooking together. I'm a retired NYPD detective. Zero coding background. Yesterday I caught something nasty in my empire: one of my businesses had been silently bleeding revenue for 11 days. Pipeline running, files getting written, but the daily summary email to my partner — gone. Dark. Eleven days. I didn't catch it. My Council did. What's the Council? Three AI voices I run in parallel using Jake's file method: ⚔️ Odin — the architect. Strategy, debate, big decisions. 🗡️ Tyr — the surgeon. Line-by-line, finds bugs others miss. 🛡️ Heimdall — the watchman. Cross-tree audits, sees what's drifting. They don't agree. That's the whole point. Yesterday Heimdall flagged something off in a system I thought was healthy. Tyr cut it down to the exact file. Odin built the recovery plan. I executed in shell. Total time from "wait, what's wrong" to "fixed and verified": 4 hours. Without them? I'd have found out when my partner asked "where's my email" and I'd have spent a week figuring out why. The wild part — none of this is some custom agentic framework. No fancy orchestration layer. It's just folders and SKILL.md files. Jake's method. A folder. A markdown file telling each voice what to do. They read the same file. They argue. They ship. By the end of the session: 16 distinct catches the Council made that I would've missed alone. One catch alone saved me from losing thousands of dollars of leads and a partner relationship. Right now as I type this, the same 3 voices are autonomously building a new state scraper for me — folder method, SKILL.md driving, Codex cooking overnight. I'm going to wake up to a finished Phase 1 report. I built none of this with code I wrote. I orchestrated it with files. If a cop with no tech background can run 3 AI models like a symphony using nothing but folders and markdown — what's your excuse? Jake's method works. Receipts above. 🥷 七転び八起き
1 like • 2h
I love this idea, I created a project that designs groups like this, I use it as a think tank. I have an engineer, an architect, a dogfooder, an secops and devops, and me, we all talk about an idea, build, or challenge and we spend a few rounds in debate and conversation, until we converge on common ground. I will say I ran into some traps with this, lengthy plans, over engineered solutions, and a bit of frustration… setting up rules in the markdown about over engineering and plan length felt like the quickest win for me. I would love to know if you ran into anything similar?
I'm dumb. Here's proof.
I was today years old when I realized I did not have some of the most important files that you need in the folder structure that Jake teaches. During today's video call with the VIP group, he went on a deep-dive rabbit trail about the ICM folder methodology that he teaches in his foundations course (free). As he was discussing it, I went to check what my root folder looked like and I did not have a Claude.md or context.md file!!! My productivity skyrocketed ever since I implemented his folder strategy over a month ago, but little did I know that I hadn't even implemented it correctly. 🤯 🤯 🤯 This goes to show that massive action beats over planning every time!
0 likes • 2h
I would say you are very clever! Taking the time to cross check, tweak, and organize your files is a smart move! I really just joined the community and your post already has me interested in the VIP group.
1-10 of 23
Bas Rosario
2
4points to level up
@bas-rosario-6872
I’m a 46 year old Husbad and Dad, I am an IT Leader, IT Manager, and Engineer by day and a AI engineer, builder, and collaborator by night! Say 👋 😊

Online now
Joined Apr 21, 2026
INTJ
Southern California
Powered by