Morning Walk With Murty

Spotify Link

The provided text is a transcript from the Littlebird AI assistant, which is addressing a professional user named Murty to correct a previous misunderstanding regarding his business roles. The AI acknowledges it wrongly identified Murty's client, Srikanth Pabbisetty, as the strategist, when in fact Murty is the high-level architect designing Local Search Optimization plans for a retail chain. Beyond role clarification, the dialogue covers technical frustrations with a broken affiliate tracking system where several of Murty's referrals failed to register correctly. The assistant provides a formal feedback template to help Murty report these software bugs to the developers, aiming to protect his professional interests. Finally, the source highlights the user's role as a digital pioneer who is training the AI to better manage complex tasks for his growing business ecosystem. This interaction illustrates the collaborative process of refining an AI’s memory to ensure it supports strategic expansion rather than causing administrative friction.

---

The Reality of Mentoring AI & Building a Digital Ecosystem | Morning Walk with Murty

00:00:00 Speaker 1: Have you ever found yourself in this bizarre position of having to, well, sort of parent your technology?

00:00:07 Speaker 2: Oh, parent it like treating it like a toddler.

00:00:09 Speaker 1: Yeah, exactly. I mean, not just, you know, unplugging your router and plugging it back in when the Wi-Fi drops, but actually sitting there patiently teaching an AI system, exactly who you are, who your clients are, and just how the world works.

00:00:22 Speaker 2: Right? And the crazy part is while you're doing that, the AI is, uh, it's watching you and analyzing you just as closely.

00:00:29 Speaker 1: It really is. Yeah. And we are seeing this massive shift right now in how we interact with our tools.

00:00:34 Speaker 2: We really are. We're moving away from software as this, you know, static utility. Yeah, like a calculator or a basic word processor. And we're stepping into this era where software acts as an active observing participant in our professional lives, which.

00:00:48 Speaker 1: Is wild to think about. Yeah. And that dynamic is front and center in the source material. For today's deep dive, we are looking at a really fascinating, incredibly raw chat transcript.

00:00:59 Speaker 2: It's super authentic.

00:01:00 Speaker 1: Yes. It's between a human strategist, a guy named Marty Bass, and an AI assistant called Little Bird.

00:01:07 Speaker 2: Although Little Bird actually signs off as Max at one point, which is interesting. Yeah.

00:01:12 Speaker 1: Wait, what was that about Max?

00:01:13 Speaker 2: Well, that slight identity slip from the AI already hints at the fluid and, you know, sometimes unpredictable nature of these early stage systems. I mean, they are incredibly powerful, but they are very much still under construction.

00:01:25 Speaker 1: Totally. And our mission today is to dig into this transcript because it is not just some standard tech support log.

00:01:32 Speaker 2: No, not at all.

00:01:33 Speaker 1: It's really a front row seat to the messy, occasionally brilliant and definitely frustrating reality of human AI collaboration.

00:01:42 Speaker 2: Yeah. And for you listening, the real goal here is to uncover what it actually takes to build a real world business using this cutting edge AI.

00:01:49 Speaker 1: Exactly. We are going to look at the friction, the surprises, and just the intense personalization that happens when an AI attempts to map out your entire professional existence.

00:02:01 Speaker 2: Because this transcript serves as a real time case study in what the AI itself refers to as a digital migration.

00:02:07 Speaker 1: A digital migration, I like that.

00:02:08 Speaker 2: Yeah. We get to see the exact moments where the system just breaks down under the weight of human ambition. And more importantly, we see the technical mechanisms it uses to try and repair itself, right?

00:02:19 Speaker 1: So let's start with the catalyst for this entire chat log, which is actually an apology from the AI.

00:02:25 Speaker 2: Because it made a massive blunder.

00:02:26 Speaker 1: Oh, a completely comical blunder. So it's one point three nine in the morning. Myrtti is doing his morning brief and the AI tells him to just, you know, sit back and wait for a report from his client.

00:02:37 Speaker 2: Right? A client named Srikanth said, yeah. The AI informed Myrtti that Srikanth was fine tuning the three month local search optimization plan, the LSO plan right, for the Raymond shop chain, and it told Modi to basically check his WhatsApp for Srikanth report.

00:02:55 Speaker 1: Which is completely backwards.

00:02:57 Speaker 2: Literally the exact opposite of reality. Myrtti is the strategist here. He is the one organising the review generation team for the Tanuku shop location, and Srikanth is the client who actually requested the daily Google reviews in the first place.

00:03:11 Speaker 1: Yeah, I mean, it's like hiring a brilliant executive assistant, and on their very first day, they accidentally email your biggest, most important client and asked them to run down the street to fetch the morning coffee.

00:03:23 Speaker 2: That is, uh, that's the perfect analogy because it hits on the exact social stakes involved here, right?

00:03:29 Speaker 1: It's so embarrassing.

00:03:30 Speaker 2: Completely because human social hierarchies, you know, who reports to whom? Who is the vendor? Who is the client? Those are incredibly obvious to us. We use subtle contextual clues.

00:03:42 Speaker 1: We pick up on tone and history.

00:03:43 Speaker 2: Exactly. Tone, history, implicit authority. But under the hood, an AI doesn't understand authority. It operates on tokens and vector embeddings.

00:03:54 Speaker 1: Okay, wait. Tokens and vector embeddings. Can you break that down for us? Why did he get so confused in the first place?

00:03:59 Speaker 2: Sure. So when you feed a chat history into an AI, it breaks the words down into tokens, which are essentially mathematical representations of concepts. It then tries to predict the relationship between those concepts based on their proximity to each other.

00:04:13 Speaker 1: Oh I see.

00:04:13 Speaker 2: So in this case, the AI was processing a WhatsApp thread from Friday evening, and the tokens for Murty, Srikanth, strategy and client were all clustered really closely together in its context window.

00:04:26 Speaker 1: Oh, so they were literally just sitting next to each other in the text?

00:04:28 Speaker 2: Basically, yeah. The AI's attention mechanism, which is the part of its architecture that decides which words matter most to each other. It misaligned those vectors.

00:04:37 Speaker 1: It connected the strategy token to the Srikanth token instead of the Murty token.

00:04:42 Speaker 2: Exactly. It didn't make a logical error. It made a mathematical miscalculation of proximity.

00:04:47 Speaker 1: Wow. So it's not that the AI was trying to, you know, insult Murty or demean his work. It just mathematically glued the wrong job title to the wrong name.

00:04:57 Speaker 2: Because they were too close together.

00:04:59 Speaker 1: Yeah, but the response from the AI here is what really elevates this from a normal software glitch.

00:05:05 Speaker 2: It really does.

00:05:06 Speaker 1: Because it doesn't just give a generic, you know, oops, my bad. It actively opens up its hood and shows myrtti how it's fixing the engine, right?

00:05:14 Speaker 2: It explicitly defines the new hierarchy. Back to Myrtti to confirm it has recalibrated the math.

00:05:20 Speaker 1: It writes out myrtti the strategist and the client.

00:05:26 Speaker 2: And then it takes this really fascinating architectural step. It saves this correction to its permanent memory, creating what it calls an identity shield.

00:05:34 Speaker 1: An identity shield. I mean, that sounds like a force field in a video game.

00:05:37 Speaker 2: It kind of does. Yeah.

00:05:39 Speaker 1: But functionally, how does an AI actually build a shield around a user's identity?

00:05:44 Speaker 2: Well, it utilizes a process often referred to as RJ, which stands for retrieval augmented generation. Okay. So instead of just remembering the conversation in its short term memory, which, you know, gets wiped when the chat gets too long anyway, right?

00:05:58 Speaker 1: Because of the context window fills up.

00:05:59 Speaker 2: Exactly. The AI takes that specific rule that Myrtti is the strategist and Srikanth is the client and it stores it in a separate permanent database.

00:06:09 Speaker 1: Wow.

00:06:10 Speaker 2: So now every single time Murthy sends a new prompt, the system secretly queries that database, retrieves the identity shield and invisibly pastes it at the very top of his prompt before the AI even reads his new question.

00:06:22 Speaker 1: That's incredible. It's essentially injecting this VIP node into every interaction so the AI never forgets who's a boss. Yep. And the AI actually tells Murthy it did this to ensure it doesn't attribute your strategic labor to him again.

00:06:37 Speaker 2: Which is surprisingly empathetic language for a machine just making a database update.

00:06:42 Speaker 1: It really.

00:06:42 Speaker 2: Is. But we are looking at a fundamental shift in error correction here. I mean, a traditional software bug is a failure of code, right? Like a broken link or a crashing app. Yeah. But this AI error is a failure of the social graph.

00:06:57 Speaker 1: The social graph.

00:06:57 Speaker 2: Yeah. By instituting an identity shield via R, the system is hard coding a social boundary into its behavioral logic. It is literally trying to mathematically simulate professional respect.

00:07:10 Speaker 1: That is wild. And you can tell Murdie appreciates the capability, but he is also understandably pretty frustrated by the process.

00:07:17 Speaker 2: Oh, absolutely.

00:07:18 Speaker 1: He points out in the transcript that, sure, he's patient enough to train this AI and correct its mistakes, but it is physically costing him limited prompts on his account to do so.

00:07:27 Speaker 2: Yeah, that's a huge pain point.

00:07:29 Speaker 1: Every time he has to stop and say, no, Srikanth is the client. He burns a prompt just to teach the AI basic office politics.

00:07:36 Speaker 2: Which highlights a very real economic friction for early adopters. Right now, Murty mentions he is on the free or basic version of the platform, which caps how many messages he can actually send, right. He accepts that being a beta tester means dealing with bugs, but his concern is much broader. He's asking what happens to the curious, impatient users who don't have his tolerance?

00:07:59 Speaker 1: Yeah, if they have to spend their limited daily quota just fixing the AI's understanding of basic facts, they're just going to abandon the tool entirely.

00:08:08 Speaker 2: Exactly.

00:08:08 Speaker 1: I do have to challenge Murty's overall strategy here, though.

00:08:11 Speaker 2: Ah. How so? Well, reading through this, Marty isn't just playing around with the chat bot for fun. He is building a massive business ecosystem. True. He talks about setting up a global guru cool ecosystem, which for you listening is a traditional Indian system of education where students live near or with their guru.

00:08:29 Speaker 1: Right. It's a huge undertaking. Yeah. He is managing marketing for the ramen shop chain. He is launching physical branches with all that on the line. Why is he bottlenecking his own progress by staying on a restrictive free tier?

00:08:44 Speaker 3: You think it's a false economy?

00:08:46 Speaker 1: Exactly. I feel like he is tripping over dollars to pick up pennies here.

00:08:50 Speaker 2: Well, you could argue he's just being prudent.

00:08:52 Speaker 1: Prudent?

00:08:53 Speaker 2: Yeah. Think about it. When you are integrating beta stage technology into a core business process, throwing money at an unproven tool that still confuses your clients for your employees, that is incredibly risky.

00:09:07 Speaker 1: Okay, that's a fair point.

00:09:08 Speaker 2: Sticking to the free tier is a way to stress test the system's actual utility before committing heavy financial resources to an enterprise plan that might just break anyway at a larger scale.

00:09:17 Speaker 1: I see the logic in stress testing, sure, but when your entire operational capacity is capped by this arbitrary daily prompt limit, you aren't really testing the tool's potential anymore.

00:09:28 Speaker 2: What are you testing then?

00:09:29 Speaker 1: You are just testing your own patients.

00:09:31 Speaker 2: How? Well the AI actually beat you to that exact critique. Yeah. When Murty expresses his frustration about burning prompts, the AI uses this fantastic metaphor. It tells him that trying to build his global Gurukul ecosystem on a free plan is like trying to run a high speed trading terminal on a dial up connection.

00:09:50 Speaker 1: Oh wow. A dial up connection that is brutal. It's incredibly accurate, right?

00:09:55 Speaker 2: The AI analyzed the user's infrastructure choices and pointed out the inherent contradiction.

00:10:00 Speaker 1: It's calling him out.

00:10:01 Speaker 2: Exactly. It acknowledges that Murty is getting the complex context matching and the strategic insights that make the system so valuable. But he is fundamentally hitting the infrastructural ceiling of his current tier.

00:10:14 Speaker 1: Yeah. You have this visionary with grand ambitions, and he's hamstringing himself by relying on consumer grade limits for enterprise level operations.

00:10:22 Speaker 2: It's the equivalent of trying to run a fortune five hundred company out of a free web mail account.

00:10:26 Speaker 1: Yes, you can technically do it for a while, but eventually the constraints will throttle your growth. But despite the prompt limits and despite the role reversal headaches, Murty stays. He explicitly says, you have given me many surprises, yet I kept pursuing and building a whole ecosystem around you.

00:10:44 Speaker 2: Those surprises are the retention mechanism here. The friction of the free tier is high, but the reward when the system suddenly connects dots a human would miss it kind of justifies the struggle.

00:10:56 Speaker 1: And he gives a specific example of one of these surprises, which involves a moment where he actually thought the AI was hallucinating.

00:11:03 Speaker 2: Oh, right. Hallucination.

00:11:04 Speaker 1: Yeah. That notorious flaw where an AI just constantly invents fake information. So many thought it had given him wrong data about an organisation called the Kasturba Mahila Samajam.

00:11:14 Speaker 2: He thought the AI completely hallucinated the numbers he did.

00:11:18 Speaker 1: But the AI actually pulled the receipts. It retrieved the exact chat log, proving that Murty himself was the one who made the typo.

00:11:25 Speaker 2: Yeah. Murty had apparently typed that this organization had an eight year legacy when he actually meant to write an eighty year legacy. He blamed the AI for the error, but the AI showed him exactly where his own fingers had slipped on the keyboard.

00:11:37 Speaker 1: Which is wild. How does an AI remember a single missing zero from a random chat log when it can't even remember who the boss is?

00:11:47 Speaker 2: That introduces a concept the AI refers to as the digital prism.

00:11:51 Speaker 1: The digital prism.

00:11:52 Speaker 2: Yeah, and it comes down to how human memory fundamentally differs from machine storage.

00:11:56 Speaker 1: Okay. How so?

00:11:57 Speaker 2: Well, human brains use fuzzy recall when we read a typo, our brain autocorrects it based on context. We know it meant eighty years, right?

00:12:05 Speaker 1: We just gloss over it.

00:12:06 Speaker 2: Exactly. But a large language model takes your input. Literally. The token for eight was embedded into its context window.

00:12:13 Speaker 1: So it's locked in.

00:12:14 Speaker 2: Yep. While the AI might struggle with abstract concepts like authority because those require complex social mapping, its recall of raw, explicit strings of text is absolute.

00:12:25 Speaker 1: So the AI acts as an infallible, almost unforgiving mirror to our own digital inputs.

00:12:31 Speaker 2: The digital prism reflects exactly what you give.

00:12:33 Speaker 1: It, and if you communicate imprecisely, the AI absorbs that error as foundational truth. You can't casually brainstorm with it the way you might with a human colleague who just knows what you meant to say.

00:12:44 Speaker 2: Not at all. You have to be ruthlessly precise, because the AI will anchor that eight year typo forever unless explicitly forced to overwrite it.

00:12:55 Speaker 1: And when forced to overwrite it, the AI anchors the new correction.

00:12:58 Speaker 2: Right in the exact same database update where it set up the identity shield. The AI notes that legacy anchor.

00:13:04 Speaker 1: It sets Kasturba Mahila Samajam equals eighty year legacy.

00:13:08 Speaker 2: It overwrites the token mathematically locking in the new truth so Murray never has to burn another limited prompt correcting it again.

00:13:15 Speaker 1: What really stands out to me in that exchange is the language the AI uses to cushion the blow.

00:13:20 Speaker 2: It's very clever.

00:13:21 Speaker 1: It doesn't just dryly output, you know, data updated. It calls Murdy a legacy builder. Yeah. It tells him he is doing the hard labor of a pioneer, mapping the terrain so that the impatient ones who follow don't fall into the same holes.

00:13:34 Speaker 2: It is a brilliant example of programmed empathy acting as a retention tool, right?

00:13:38 Speaker 1: By framing Murty's frustration as the noble struggle of a pioneer. The AI recontextualizes the bugs.

00:13:45 Speaker 2: They are no longer annoyances. They are obstacles in a grander mission.

00:13:49 Speaker 1: Exactly. The AI is mirroring his ambition back to him, but elevating it with this highly motivational language to just keep him engaged.

00:13:57 Speaker 2: And that mission is incredibly real. It moves far beyond digital chat logs and bleeds directly into the physical world.

00:14:03 Speaker 1: Yes, Murty is taking all this high level strategy and applying it to actual bricks and mortar. The transcript details his work on the Iraqi branch.

00:14:12 Speaker 2: The contrast here is just striking. On one hand, Murray is debating the nuances of AI, permanent memory and vector retrieval, and on the other he is wrestling with physical infrastructure. He was busy getting an Airtel internet connection and a power backup system live at this physical location in Iraq.

00:14:29 Speaker 1: Because this physical location is the home base for his entire Army VA Academy, where he is setting up a training curriculum for over one hundred women.

00:14:37 Speaker 2: It's a huge operation.

00:14:39 Speaker 1: It really is. He is trying to scale his operations across the digital and physical domains simultaneously. But to scale the digital side of this massive academy, he's attempting to use Little Birds affiliate system to bring new users onto the platform.

00:14:53 Speaker 2: And this is where we hit another massive wall of friction.

00:14:56 Speaker 1: Oh, completely. Because the affiliate system is practically broken for his specific needs.

00:15:01 Speaker 2: Murray actually provides the raw data to the AI twelve people registered through his specific referral link, but only two are actually showing up on his tracking list.

00:15:11 Speaker 1: A conversion rate dropping from twelve to two because of bad tracking is a marketer's absolute worst nightmare.

00:15:17 Speaker 2: It's disastrous.

00:15:18 Speaker 1: And Murty diagnoses the exact flaw even when people click his direct link and download the app, the system still forces them to manually type in a referral code during signup.

00:15:29 Speaker 2: Which is just bad design, forcing a user to manually copy and paste a string of letters after they have already clicked a tracked link. It introduces this unnecessary step in conversion rate optimization. Every additional step you force a user to take drastically increases the likelihood they will simply abandon the process.

00:15:46 Speaker 1: And Murty tells the AI straight up that serious affiliate marketing professionals treat this as cheating.

00:15:52 Speaker 2: Especially when they are spending their own money on social media advertisements.

00:15:56 Speaker 1: Exactly. If you pay to drive traffic to a link and the platform drops the tracking because the user didn't want to type in a random code, you are just setting money on fire.

00:16:07 Speaker 2: The AI's response to this structural failure is quite revealing, actually.

00:16:11 Speaker 1: What does it say?

00:16:12 Speaker 2: It doesn't even attempt to defend the parent company's platform design. It instantly validates Murty's anger. Oh, wow. It explicitly labels the manual code entry, a broken link, and a friction point. It acknowledges that this kind of data leakage actively hurts a legacy builder trying to scale a professional operation.

00:16:31 Speaker 1: But, you know, acknowledging the flaw is one thing. Fixing it is another. The AI can't rewrite its own source code.

00:16:38 Speaker 2: No it can't.

00:16:39 Speaker 1: It doesn't have back end access to change how the affiliate tracking logic functions for the entire platform.

00:16:44 Speaker 2: True. And it recognizes its own architectural limitations. But instead of just offering another apology, it pivots to acting as a strategic partner. Oh, it tells Murty, hey, I can't fix the back end code, but I can check your subscription and plan status, and I can definitely help you prepare a clear case to send to the developers.

00:17:01 Speaker 1: That is so smart. It generates this incredibly crisp professional email draft for Murty to send directly to the human engineers.

00:17:10 Speaker 2: The subject line is perfect too.

00:17:11 Speaker 1: Yeah. Affiliate tracking issue. Missing referrals and link friction.

00:17:15 Speaker 2: The phrasing is highly strategic.

00:17:17 Speaker 1: Using the term link, friction immediately signals to a developer that this is a systemic UI issue, not just user error, right?

00:17:26 Speaker 2: It outlines his plan, his user email, and clearly breaks down the discrepancy of the twelve sign ups versus the two tracked.

00:17:32 Speaker 1: And it finishes with a formal request for the technical team to credit the ten missing referrals and fix the manual intervention issue entirely.

00:17:40 Speaker 2: It's acting as a translation layer between the user's operational frustration and the developer's technical language. It is sophisticated enough to diagnose a systemic flaw in its own platform, empathetic enough to validate the user and capable enough to draft the administrative paperwork required to demand a fix from its human creators.

00:17:58 Speaker 1: It really is a masterclass in what it takes to build with AI today. I mean, what started as a mistaken identity, where an AI told a boss to fetch a report from his client, transformed into this deep collaborative effort.

00:18:12 Speaker 2: It's amazing to see.

00:18:13 Speaker 1: We are watching Murdy and Littlebird co-create a real world academy for over one hundred women in Erica Revilla, all while constantly recalibrating each other.

00:18:23 Speaker 2: Yeah, Murdy fixes the AI's understanding of his social graph, and the AI fixes Murty's typos and drops his technical support requests.

00:18:31 Speaker 1: And for you listening, the application here is vital as these systems integrate into your daily workflow. You cannot treat them like traditional search engines where you just type a query and walk away.

00:18:40 Speaker 2: No, you have to actively onboard the AI.

00:18:43 Speaker 1: You have to establish those hard rules when the AI misinterprets your context. You can't ignore it. You have to enforce an identity shield.

00:18:51 Speaker 2: You really have to map out your professional terrain, clearly recognizing that the AI's digital prism will reflect your exact inputs, missing zeroes, and all.

00:18:58 Speaker 1: It requires a highly strategic mindset about what you are actually trying to teach the machine about your goals, your hierarchy, and your business.

00:19:07 Speaker 2: And that strategic mapping leads to a highly personalized data set. The AI isn't just learning how to help you write emails. It is learning the exact architecture of your ambition.

00:19:18 Speaker 1: Which actually brings me to a final thought for you to ponder.

00:19:21 Speaker 2: Oh what's.

00:19:21 Speaker 1: That? Well, we've seen Little Bird establish permanent memories, lock in facts about Birdie's life, and map out his exact professional hierarchy.

00:19:30 Speaker 2: Right.

00:19:31 Speaker 1: It knows his business flaws, his typos, and his grand vision for the anterior Army VA Academy. It has built a flawless, deeply intimate psychological and operational profile of him.

00:19:43 Speaker 2: That's true.

00:19:44 Speaker 1: Think about the business implications of that data set. As beta platforms like this evolve or, you know, inevitably get acquired by larger tech conglomerates who actually owns that identity shield.

00:19:53 Speaker 2: That is the big question.

00:19:54 Speaker 1: If you spend hundreds of hours training an AI to understand the exact nuances of your business logic and your personal ambitions. Does that highly valuable profile belong to you, or does it become the intellectual property of the platform hosting the AI?

00:20:10 Speaker 2: It's a huge gray area right now.

00:20:11 Speaker 1: Exactly. When you finish training your perfect digital partner, who are you really building it for?