Mar 9, 2026 Meeting Mar 9, 2026 at 19:58 PDT - Transcript 00:00:00 Yeshwanth Reddy Yerraguntla: Okay. Vara Kumar Jagarapu: Go Yeshwanth Reddy Yerraguntla: What did uh goals are say yesterday? Manisha Gundapuneedi: So, Vara Kumar Jagarapu: away. Yeshwanth Reddy Yerraguntla: Everybody it's difficult to assume uh we have like dependencies are covered. So everyone has to start with some kind of a markup. Manisha Gundapuneedi: okay. Yeshwanth Reddy Yerraguntla: So if I take a random item like this ad hoc answers right uh actually the news this is very clear on how to do news broadcast is uh somewhere where we don't have very the full-fledged system is not available yet. So what does it mean? We have to first uh understand from this backbone what are the starting points and ending points for this life cycle. Once you figure that out, you will start mocking up inputs. Uh what are all the required inputs to get this uh concept working mockups ready and then you will come to the UI you'll start testing it and see how it responds based on which you know how to uh do the coding activity based on which you'll know how to set up the API contracts and everything. 00:01:20 Yeshwanth Reddy Yerraguntla: Once those are set, you will have now a proper requirements document saying for this to function properly, these are the inputs. This is how the input should be present in the DB. All those things will show up. And the API contracts, this is how I'm planning to uh implement or I have already implemented them in this format. key um that is like one level of execution to have to to get to that point. The way I would want let's say Raj Shaker if he picks it up the way I would want him to do it is first of all create a fresh ticket in Jira saying uh understand the life cycle uh agentic orchestration between RT agent and user aware uh agent for news broadcast that is one ticket acceptance criteria is to come up with subtasks to come up with mock data to come up with the API contracts right Um then uh or subtask mark data API contracts finally actual code implementing on the mock data. This the acceptance criteria uh and that is acceptance criteria for the what is what is it dummy Jira task. 00:02:44 Yeshwanth Reddy Yerraguntla: I'll just create a fresh sheet. First thing we are saying is this is the task name uh explore lagput understandic acceptance criteria to understand how it fits in uh overall code. Next to to understand how to set up mark data uh create subtasks for above two points followed by start coding to demo the idea on mark data. Finally finish documentation for V1 implementation. This is one task. These are these are the acceptance criteria. Sorry. I'm sorry I'm getting confused. The exploration task exploration step acceptance criteria is set up subtasks for this item. The acceptance criteria task itself is going to come out come out with these uh uh uh things as things to do. So each one of them will once someone like either you or Rajik or whoever once someone goes through this and say yeah this is looking good then immediately you will create those subtasks in Jira for each one of these each one of these is going to have its own acceptance criteria now right here what is the acceptance criteria what files to search and uh how what are the entry points to demo this uh feature allow you have multiple acceptance criteria each one will have its own acceptance criteria now I am 00:05:18 Yeshwanth Reddy Yerraguntla: saying people can sit and do this one thing uh today itself based on each on each one of these things they'll know what to do and they can continue doing now. Am I still Manisha Gundapuneedi: Okay. Yeshwanth Reddy Yerraguntla: confusing? Manisha Gundapuneedi: Uhhuh. Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: They have to come up with this subtask but whenever they're trying to understand right again uh it will come to lead Yeshwanth Reddy Yerraguntla: It will come to lead but they will sit with the person who is about to implement so that both of them are on the same page. Vara Kumar Jagarapu: uh then it is fine in that case like if it will work. Yeah. Yeshwanth Reddy Yerraguntla: just the lead can't sit and think through and then give KT or Vara Kumar Jagarapu: Yeah. Yeshwanth Reddy Yerraguntla: just the junior anyway can't do it by themselves. So to come to that point let the junior at least do some homework. Vara Kumar Jagarapu: Yeah. Ma. Yeah. Practically. Yeah. 00:06:47 Vara Kumar Jagarapu: You can speak it out. Yeshwanth Reddy Yerraguntla: So then what will Manisha Gundapuneedi: If it involves lot of unknowns or lot of we will put them aside. Yeshwanth Reddy Yerraguntla: Correct. Correct. Correct. What whatever tasks don't have unknowns or don't need research, they should be the ones uh they should be the candidates. Vara Kumar Jagarapu: Yeah. Yeshwanth Reddy Yerraguntla: Okay. Vara Kumar Jagarapu: So before that like maybe discuss we can proceed on it. We can create a backlog task required and then we can assign priorities P 0 and filter out it and can distribute among the people. That is what I'm Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: thinking. Yeshwanth Reddy Yerraguntla: Um I can spend two more hours. Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: So Vara Kumar Jagarapu: They can assign once Manisha Gundapuneedi: discuss Vara Kumar Jagarapu: civiliz Yeshwanth Reddy Yerraguntla: um makes sense. Manisha Gundapuneedi: clear. Yeshwanth Reddy Yerraguntla: Makes sense. Makes sense. So Uh first is design system. You can drop off. Yeah. 00:08:40 Yeshwanth Reddy Yerraguntla: Yeah. We'll continue. Age of U front end platform design one design system. What is this purely the aesthetics part of it? Manisha Gundapuneedi: content design three phases. Yeshwanth Reddy Yerraguntla: H Manisha Gundapuneedi: First design Vara Kumar Jagarapu: just just to get deliver items from from there. Manisha Gundapuneedi: followup. Yeshwanth Reddy Yerraguntla: Who is the Vara Kumar Jagarapu: Manisha or present. Yeshwanth Reddy Yerraguntla: assenee? Vara Kumar Jagarapu: Maybe we can write something like follow up design to get this 100. We can do that. Yeshwanth Reddy Yerraguntla: Okay. Vara Kumar Jagarapu: Good. Yeshwanth Reddy Yerraguntla: nothing to change basically this is even though it is in Manisha's bucket insert one column right leader at least two people Vara Kumar Jagarapu: While Yeshwanth Reddy Yerraguntla: Anita. Okay. User navigation patterns is user inter user Manisha Gundapuneedi: History. Yeshwanth Reddy Yerraguntla: experience. Vara Kumar Jagarapu: navigation Manisha Gundapuneedi: in that Yeshwanth Reddy Yerraguntla: Okay. Okay. Okay. Manisha Gundapuneedi: case. Vara Kumar Jagarapu: I think this can be close to on. Yeshwanth Reddy Yerraguntla: Then second 00:10:23 Vara Kumar Jagarapu: Yeah. Yeshwanth Reddy Yerraguntla: um see I will suggest and putting on Manisha Gundapuneedi: Okay. Yeshwanth Reddy Yerraguntla: tickets in the sense of at least my understanding. Vara Kumar Jagarapu: Okay. Uh you Yeshwanth Reddy Yerraguntla: Sorry. Vara Kumar Jagarapu: subtask Yeshwanth Reddy Yerraguntla: stories. Manisha Gundapuneedi: Are Yeshwanth Reddy Yerraguntla: Correct. Manisha Gundapuneedi: we Vara Kumar Jagarapu: right Yeshwanth Reddy Yerraguntla: Correct. Uh Vara Kumar Jagarapu: system. Use the navigation pattern combination visualization and Yeshwanth Reddy Yerraguntla: subtasks. Oh no, I am I I I am on the same page with that. Vara Kumar Jagarapu: then Yeshwanth Reddy Yerraguntla: But what I'm trying to say is um there has to be an initial uh subtask saying uh explorer that one task should lead to creation of more detailed tasks on now. I'm not saying this is itself a subtask because we don't know what to do. Vara Kumar Jagarapu: Okay. So, uh and the external team it's kind of just follow task for us. They can create subtasks on this Yeshwanth Reddy Yerraguntla: just Manisha Gundapuneedi: separate. 00:11:58 Yeshwanth Reddy Yerraguntla: put Vara Kumar Jagarapu: particular subtask. Yeshwanth Reddy Yerraguntla: And what I mean by subtask is the tasks acceptance criteria Manisha Gundapuneedi: Oops. Yeshwanth Reddy Yerraguntla: is to come up with detailed list of tasks for this one guy. Or maybe if we are saying the design let them take care of the headache. Vara Kumar Jagarapu: Uh Yeshwanth Reddy Yerraguntla: I will only do follow align we can create subtask by saying this is purely Vara Kumar Jagarapu: um Yeshwanth Reddy Yerraguntla: followup task. Vara Kumar Jagarapu: my intent actually just just to follow up Yeshwanth Reddy Yerraguntla: Okay. Vara Kumar Jagarapu: and they can follow their own. We Yeshwanth Reddy Yerraguntla: Process. Great. Vara Kumar Jagarapu: have Yeshwanth Reddy Yerraguntla: Yeah, this is clear. So immediately they will go into Jira. Vara Kumar Jagarapu: friends that we need to get for Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: API, Yeshwanth Reddy Yerraguntla: Right. Vara Kumar Jagarapu: right? Yeshwanth Reddy Yerraguntla: Next. Uh, Vara Kumar Jagarapu: Yeah, Yeshwanth Reddy Yerraguntla: reverify. Reverify. Yeah. Yeah. 00:13:08 Vara Kumar Jagarapu: sorry. Yeshwanth Reddy Yerraguntla: One second. on second continu. Vara Kumar Jagarapu: Okay, sure. Yeshwanth Reddy Yerraguntla: discuss. Sorry. Vara Kumar Jagarapu: All Manisha Gundapuneedi: Ed. Vara Kumar Jagarapu: right. Chares. All right, I think Manisha Gundapuneedi: Uh, are they JWT? Vara Kumar Jagarapu: Okay. APS already. Manisha Gundapuneedi: Five minutes. Vara Kumar Jagarapu: Uh, Manisha Manisha Gundapuneedi: Hello. Vara Kumar Jagarapu: question. So, email notific Manisha Gundapuneedi: Huh? Vara Kumar Jagarapu: P2 better Manisha Gundapuneedi: there. Vara Kumar Jagarapu: notification. Hello. Manisha Gundapuneedi: choose. Vara Kumar Jagarapu: When P are Manisha Gundapuneedi: Uhhuh. Vara Kumar Jagarapu: back Manisha Gundapuneedi: Um, Vara Kumar Jagarapu: Pisces. Manisha Gundapuneedi: training Vara Kumar Jagarapu: Pick Manisha Gundapuneedi: cycle. Vara Kumar Jagarapu: it up. Manisha Gundapuneedi: Priority button. Vara Kumar Jagarapu: Give me actually The pen All right. Where are you? Daddy. Let's keep going. Are you speech? Dad. Is that unit test? 00:35:08 Manisha Gundapuneedi: feature levels. Vara Kumar Jagarapu: General automation. Manisha Gundapuneedi: All right. Vara Kumar Jagarapu: Excuse me. Are Hello. Hello. Thank you. Breakfast Sign Manisha Gundapuneedi: What? That's one down like Vara Kumar Jagarapu: already. Manisha Gundapuneedi: Okay, Yeshwanth Reddy Yerraguntla: I'm back. Vara Kumar Jagarapu: Yeah, 2 minutes Yeshwanth Reddy Yerraguntla: Okay, Vara Kumar Jagarapu: 2 minutes Yeshwanth Reddy Yerraguntla: take your Vara Kumar Jagarapu: Yeah, I am back. Yeshwanth Reddy Yerraguntla: Huh? Vara Kumar Jagarapu: So Yeshwanth Reddy Yerraguntla: Looks Vara Kumar Jagarapu: just Yeshwanth Reddy Yerraguntla: good. Vara Kumar Jagarapu: back usern pattern. Yeshwanth Reddy Yerraguntla: user admin. Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: I don't know. Vara Kumar Jagarapu: Thought of chicken are back related actually. and uh restrict pages to admin only. That is okay. And uh authentication authorization checkp Yeshwanth Reddy Yerraguntla: Uh authorization. Okay. What do you mean? Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: There is arbback in terms of what kind of uh data agents can access for 00:45:50 Vara Kumar Jagarapu: General Yeshwanth Reddy Yerraguntla: every user. One second. Uhhuh. Admin access control. Vara Kumar Jagarapu: login and consequent authorizations Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: back. Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: Allow admins to invite uh users. List of users display adific on Yeshwanth Reddy Yerraguntla: I training P1. Vara Kumar Jagarapu: right Yeshwanth Reddy Yerraguntla: So the admin, Vara Kumar Jagarapu: admin trainer. Yeshwanth Reddy Yerraguntla: so let me put it this way. Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: Tata Steel when they see the demo obviously it will be seen by one or two people only. It's not like they're releasing it to their team anywhere. So P 0 for P 0 deadline is 4 weeks from now. We can we can put all of these as P1. Vara Kumar Jagarapu: Okay then. Right. Set DB and users DB data models and uh table contracts. Yeshwanth Reddy Yerraguntla: admin leadership all those things I'm saying level data models 00:48:22 Vara Kumar Jagarapu: Mhm. Python junk. Yeshwanth Reddy Yerraguntla: Python Django API Vara Kumar Jagarapu: Okay. Tables. Tables. Yeshwanth Reddy Yerraguntla: table. Vara Kumar Jagarapu: more. Okay. Okay. So without so one thought I have is no need to invent everything because Yeshwanth Reddy Yerraguntla: Makes Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: sense. Vara Kumar Jagarapu: And Okay. Yeah. And the seventh row. Maybe login screen. Yeshwanth Reddy Yerraguntla: H Vara Kumar Jagarapu: What login needs to be supported in username password. Yeshwanth Reddy Yerraguntla: render channel P 0. Vara Kumar Jagarapu: Uh Yeshwanth Reddy Yerraguntla: Okay. Vara Kumar Jagarapu: okay. P. Yeah. the clear Salesforce and Microsoft the P1 P4. Okay. So your question at the Yeshwanth Reddy Yerraguntla: Yeah, duplicate JC. Uh yeah, Vara Kumar Jagarapu: moment. Yeshwanth Reddy Yerraguntla: duplicate support for Microsoft and test. I think we are good. Vara Kumar Jagarapu: Mhm. It's 00:58:56 Yeshwanth Reddy Yerraguntla: I'm back. Vara Kumar Jagarapu: User onboarding management part of us corresponding login. Yeshwanth Reddy Yerraguntla: Okay. Yeah. Show Vara Kumar Jagarapu: What do you think? Only a few things on the we Yeshwanth Reddy Yerraguntla: H. Yeah. Vara Kumar Jagarapu: can. Yeah. Okay. So, and login supporting Yeshwanth Reddy Yerraguntla: Check Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: picture. Vara Kumar Jagarapu: Login Yeshwanth Reddy Yerraguntla: Oh Vara Kumar Jagarapu: UI. Yeshwanth Reddy Yerraguntla: no already. H. Vara Kumar Jagarapu: What? Bangalore. Yeshwanth Reddy Yerraguntla: H migration. Vara Kumar Jagarapu: Okay, sorry the Yeshwanth Reddy Yerraguntla: uh migration from basic Vara Kumar Jagarapu: demonations. Yeshwanth Reddy Yerraguntla: UI. Vara Kumar Jagarapu: Okay. So, Yeshwanth Reddy Yerraguntla: Oh no. P1 Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: actually 456 Vara Kumar Jagarapu: Okay. So, Yeshwanth Reddy Yerraguntla: P1. 456. Vara Kumar Jagarapu: 4 5 6. Okay. Yeshwanth Reddy Yerraguntla: I'm back. Vara Kumar Jagarapu: So uh and username password back 01:03:34 Yeshwanth Reddy Yerraguntla: Oh no. Vara Kumar Jagarapu: APS Yeshwanth Reddy Yerraguntla: Login support. Yeah. Vara Kumar Jagarapu: independent who can these are ready to pick once user onboarding Yeshwanth Reddy Yerraguntla: Oh, Vara Kumar Jagarapu: management tables and corresponding login support AP regular username and password needs to be implemented that needs to be configured through flag system. Yeshwanth Reddy Yerraguntla: Monaco pile. Vara Kumar Jagarapu: Okay. Okay. Yeshwanth Reddy Yerraguntla: Whatever we need. One of them is this. Vara Kumar Jagarapu: checks. Okay. So this can be also done right and dashboard landing Yeshwanth Reddy Yerraguntla: Hello. Vara Kumar Jagarapu: page. Yeshwanth Reddy Yerraguntla: P1. Oh, P2. Okay. Okay. Vara Kumar Jagarapu: Okay. Next. Visualizations. Visualizations. Dash. Yeshwanth Reddy Yerraguntla: bro. Yeah. Visualizations for uh chat. Vara Kumar Jagarapu: ask. Yeshwanth Reddy Yerraguntla: Visualizations for dashboard. Vara Kumar Jagarapu: Okay. So, PG1, right? So next chart interface and continuous conversations maintaining current 01:06:06 Yeshwanth Reddy Yerraguntla: and the P 0 streaming of P 0 sockets P Vara Kumar Jagarapu: text. Yeshwanth Reddy Yerraguntla: 0. Yeah. on Vara Kumar Jagarapu: Then fine data streaming and agent responses Yeshwanth Reddy Yerraguntla: slow Vara Kumar Jagarapu: responses entry pointing. Yeshwanth Reddy Yerraguntla: agent. Simple mark agent coach. Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: Yes. Vara Kumar Jagarapu: Right. Yeshwanth Reddy Yerraguntla: Yes. Vara Kumar Jagarapu: Okay. Uh sockets implementation is also same. Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: to call information should be displayed in the UI while working on the user query. Okay. So this can be also done more with more present right. Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: Okay. Nent follow-up questions. Oh this is also as a part of uh We give Yeshwanth Reddy Yerraguntla: Um, Vara Kumar Jagarapu: elevator Yeshwanth Reddy Yerraguntla: this is something they can mock basically relatively easy but feature. Exactly. Vara Kumar Jagarapu: followup questions like it will ask you will be replying right. Yeah. Yeshwanth Reddy Yerraguntla: That's not what I a second I'll share my screen and tell 01:08:10 Vara Kumar Jagarapu: Okay. within. Yeshwanth Reddy Yerraguntla: what Vara Kumar Jagarapu: Mhm. Yeshwanth Reddy Yerraguntla: ask open when you ask a question. summarize whatever Vara Kumar Jagarapu: H. Yeshwanth Reddy Yerraguntla: question these are probably followup questions for Vara Kumar Jagarapu: Oh no. Yeshwanth Reddy Yerraguntla: that is what I mean Vara Kumar Jagarapu: Oh. Okay. Yeshwanth Reddy Yerraguntla: and Vara Kumar Jagarapu: So, okay. For now. Okay. So, okay. Yeshwanth Reddy Yerraguntla: implement Vara Kumar Jagarapu: So, Yeshwanth Reddy Yerraguntla: because Vara Kumar Jagarapu: later. Yeshwanth Reddy Yerraguntla: yeah Vara Kumar Jagarapu: Okay. Now, Yeshwanth Reddy Yerraguntla: training life cycle So P1 Not done Vara Kumar Jagarapu: okay. H right. So Yeshwanth Reddy Yerraguntla: correctly. Vara Kumar Jagarapu: okay. Okay. The errors and exception handling in the uh in the UI. Okay. uh errors and exceptions. It can be API calls or agent. Is there any way that we are thinking structure call this? 01:10:34 Manisha Gundapuneedi: Yeah. Vara Kumar Jagarapu: Okay. So back Yeshwanth Reddy Yerraguntla: Ch. Manisha Gundapuneedi: Actually Vara Kumar Jagarapu: right hand Manisha Gundapuneedi: agent handles it. Vara Kumar Jagarapu: complications. silent that might be the issue. Correct me. Manisha Gundapuneedi: Hello. Yeshwanth Reddy Yerraguntla: main issue graceful Vara Kumar Jagarapu: Yeah. So, Yeshwanth Reddy Yerraguntla: something it has to tell instead of simply being silent or crashing. Vara Kumar Jagarapu: so scope of the story Yeshwanth Reddy Yerraguntla: Yes. Vara Kumar Jagarapu: top. Yeshwanth Reddy Yerraguntla: The junior themselves will come up with what are the things. Vara Kumar Jagarapu: Okay. So I to you at Manisha Gundapuneedi: Huh? Vara Kumar Jagarapu: least Manisha Gundapuneedi: I got it. Vara Kumar Jagarapu: Okay. Agree. Yeshwanth Reddy Yerraguntla: after 2 weeks. What is that scope? They Vara Kumar Jagarapu: after two weeks. Errors and Yeshwanth Reddy Yerraguntla: don't Vara Kumar Jagarapu: exceptions. So to be on CN needs to be taken Yeshwanth Reddy Yerraguntla: le generally speaking, 01:13:04 Vara Kumar Jagarapu: care. Yeshwanth Reddy Yerraguntla: errors and exceptions. And so they are just they are easy to handle. It will tell it will come up with all the possible situations where we need to handle these Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: things. Vara Kumar Jagarapu: Okay. Fine. Okay. So Yeshwanth Reddy Yerraguntla: Only thing uh here to take care is what are all the scenarios that you have to cover the list out there each scenario what to Vara Kumar Jagarapu: okay. Okay. Yeshwanth Reddy Yerraguntla: do Vara Kumar Jagarapu: History management is structure DB structure DB intention. Yeshwanth Reddy Yerraguntla: postress Vara Kumar Jagarapu: Okay. Okay. Session Yeshwanth Reddy Yerraguntla: maybe Vara Kumar Jagarapu: management user log. Okay. Yeshwanth Reddy Yerraguntla: Yes, Vara Kumar Jagarapu: tables Yeshwanth Reddy Yerraguntla: correct. Got it. Vara Kumar Jagarapu: right Yeshwanth Reddy Yerraguntla: Correct. Vara Kumar Jagarapu: okay uh yeah session manager for we can use full history to the al we can use the context window 85% limit So Manisha is clear. 01:14:49 Manisha Gundapuneedi: You can always compact it once with session management. Uh we can send to Vara Kumar Jagarapu: And whenever you're chatting complete whenever next question is askedly we thought of like sending full history. Okay. Plan the back end APS and finalize contracts. Create more APIs Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: required. Yeshwanth Reddy Yerraguntla: separate task and custom because there are so many marks that you have to Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: create. Manisha Gundapuneedi: Yeah. Yeshwanth Reddy Yerraguntla: All Vara Kumar Jagarapu: So, right. So that till 32 most of the things Manisha Gundapuneedi: Yeah. Vara Kumar Jagarapu: you can start working on Yeshwanth Reddy Yerraguntla: right. Vara Kumar Jagarapu: it. Manisha Gundapuneedi: Yeah. User interface only. Vara Kumar Jagarapu: actually migration from okay. So P you should able to start and working on them. Manisha Gundapuneedi: I mean we can start butch Vara Kumar Jagarapu: Okay. Manisha Gundapuneedi: for. Vara Kumar Jagarapu: You put Ganesh. Manisha Gundapuneedi: Oh Vara Kumar Jagarapu: Okay. So, I'm thinking what? Manisha Gundapuneedi: no. 01:17:32 Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: Fore! Vara Kumar Jagarapu: And Amoleia Harshet Abilash. Manisha Gundapuneedi: foreign. Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: Foreign! Foreign! Manisha Gundapuneedi: Low task data source agent lowle architecture. Yeshwanth Reddy Yerraguntla: task with them. Correct. Manisha Gundapuneedi: User. Vara Kumar Jagarapu: Okay. Okay. So on based on user some connectors should be Yeshwanth Reddy Yerraguntla: Yeah, Vara Kumar Jagarapu: automatically assigned to them. Yeshwanth Reddy Yerraguntla: it can be P2. Vara Kumar Jagarapu: P2. Manisha Gundapuneedi: Ready Yeshwanth Reddy Yerraguntla: make to access additional cont Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: who whoseever name it Vara Kumar Jagarapu: Lay them Yeshwanth Reddy Yerraguntla: Show the Vara Kumar Jagarapu: up. Manisha Gundapuneedi: for Yeshwanth Reddy Yerraguntla: whatever we've been doing Since one Manisha Gundapuneedi: detail. Fore discussed. Vara Kumar Jagarapu: Hey, chill out. Yeshwanth Reddy Yerraguntla: set research sprint Um Manisha Gundapuneedi: only sprint one presenter task. Yeshwanth Reddy Yerraguntla: first Manisha Gundapuneedi: management. Yeshwanth Reddy Yerraguntla: backlog. Manisha Gundapuneedi: Okay. Vara Kumar Jagarapu: Maybe. So you can send this list of list top level then we can take it 01:21:47 Manisha Gundapuneedi: Okay. Vara Kumar Jagarapu: forward Manisha Gundapuneedi: Now she Vara Kumar Jagarapu: task. Yeah. No. Manisha Gundapuneedi: Okay. Vara Kumar Jagarapu: Um, Manisha Gundapuneedi: Um Yeshwanth Reddy Yerraguntla: Rahul Vara Kumar Jagarapu: AP signature. Soy. Yeshwanth Reddy Yerraguntla: I don't want to do Manisha Gundapuneedi: animal. Oh. Yeshwanth Reddy Yerraguntla: it. Vara Kumar Jagarapu: Yeah. Then Yeshwanth Reddy Yerraguntla: 33 sorry 34 35 set up for your user preferences follow questions okay okay second question Vara Kumar Jagarapu: I paint it. Yeshwanth Reddy Yerraguntla: user preferences followup questions Basic agent set up for UI communication. Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: I break I we just break it into uh two new rows. User preferences followup questions on actually followup questions already Vara Kumar Jagarapu: chart. Yeshwanth Reddy Yerraguntla: actually. Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: User preferences on the other hand is coming into training aspect. training life cycle. Thumbs up or thumbs down to it should um yeah Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: training sir. Vara Kumar Jagarapu: So, 01:24:50 Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: So later Yeshwanth Reddy Yerraguntla: Uh, Manisha Gundapuneedi: Oh Vara Kumar Jagarapu: clear. Yeshwanth Reddy Yerraguntla: man. Manisha Gundapuneedi: no. type uh say get workflow or slow environments Vara Kumar Jagarapu: branches Manisha Gundapuneedi: information Vara Kumar Jagarapu: inside. Yeshwanth Reddy Yerraguntla: Uhhuh. Existing one there. Manisha Gundapuneedi: guidelines. team Vara Kumar Jagarapu: already existing. Yeshwanth Reddy Yerraguntla: Get workflow environments. I 38 on the other hand Manisha Gundapuneedi: contact. Yeah. Yeshwanth Reddy Yerraguntla: already Manisha Gundapuneedi: Oh. Vara Kumar Jagarapu: Okay. Okay. So just the team key we can Mhm. Yeshwanth Reddy Yerraguntla: and I mean I can do it immediately anytimes and branch Vara Kumar Jagarapu: Okay. So call schedule Yeshwanth Reddy Yerraguntla: up to you. Vara Kumar Jagarapu: isn't alpha now. Yeshwanth Reddy Yerraguntla: Yeah. / alpha branch branch Vara Kumar Jagarapu: Sorry. Yeshwanth Reddy Yerraguntla: branch. Vara Kumar Jagarapu: It presented a bit. Um Manisha Gundapuneedi: Come on. Yeshwanth Reddy Yerraguntla: detailed tasks. News broadcast ad hoc answers question and refresh. 01:27:21 Yeshwanth Reddy Yerraguntla: Create required databases tables to fulfill knowledge base specifications. Implementation of required tools integration of new or new tool creations governance life cycle unknown. So for 39 40 41 uh I can these are heavy tasks and we can ask uh uh people to get started on these things. Vara Kumar Jagarapu: We deleted task. Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: But as you said like lead and corresponding person they will be discussing and they come up with what to do right and then we'll creating a task. Yeshwanth Reddy Yerraguntla: Correct. Correct. Correct. Yeah. Vara Kumar Jagarapu: So, Yeshwanth Reddy Yerraguntla: Pawania. So news broadcast. I'll continue doing this. It is not done yet. I will continue. I will add a task in Jira. Quest questions and refresh. actually. Yeah. News broadcast. Yeah. Create required databases and required tables. Vara Kumar Jagarapu: I'm done. Uh I actually solve it. 01:29:13 Yeshwanth Reddy Yerraguntla: Oh, no. No. Are Vara Kumar Jagarapu: table. Yeshwanth Reddy Yerraguntla: they Vara Kumar Jagarapu: Okay. So, this needs to provide him. Okay. So, Yeshwanth Reddy Yerraguntla: like I Manisha Gundapuneedi: Not quite Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: did. Manisha Gundapuneedi: here. Vara Kumar Jagarapu: Implementation of required tools and integrations. Agent agent function. Yeshwanth Reddy Yerraguntla: Away communication. Vara Kumar Jagarapu: Okay. So that like anything to start with. Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: Can we schedule it at 11:30? Manisha Gundapuneedi: down. Vara Kumar Jagarapu: Um. Manisha Gundapuneedi: And now Yeshwanth Reddy Yerraguntla: 1 hour. I can Vara Kumar Jagarapu: Uh. Manisha Gundapuneedi: that Vara Kumar Jagarapu: Oh. Yeshwanth Reddy Yerraguntla: hear I don't know why people Vara Kumar Jagarapu: invited. Okay. So 8:30 morning, Yeshwanth Reddy Yerraguntla: What? Vara Kumar Jagarapu: right? Yeah. Yeshwanth Reddy Yerraguntla: Huh? Vara Kumar Jagarapu: Just for example, how will let's say Yeshwanth Reddy Yerraguntla: Yeah. Oh no. Vara Kumar Jagarapu: okay I Atlantically. 01:31:53 Yeshwanth Reddy Yerraguntla: Align situation slow. Vara Kumar Jagarapu: Okay. Yeah. Share some Yeshwanth Reddy Yerraguntla: Implementation Vara Kumar Jagarapu: 43. Yeshwanth Reddy Yerraguntla: of require tools integration on new tool creations. Vara Kumar Jagarapu: JP. Yeshwanth Reddy Yerraguntla: Um basically tool library there will be common tools for all the agents. This is a I mean there is no standard uh uh implementation methodology or anything research uh task. So either Raja should take it or I should take it. Vara Kumar Jagarapu: Okay. So library max right. Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: already existing. Start. Yeshwanth Reddy Yerraguntla: We can probably take this call once we have enough number of tools to work with. Vara Kumar Jagarapu: Hey. Uh Yeshwanth Reddy Yerraguntla: What is the point of premature optimization? Vara Kumar Jagarapu: expectation. Okay. Yeshwanth Reddy Yerraguntla: specific to each Manisha Gundapuneedi: Nice. Yeshwanth Reddy Yerraguntla: connector Vara Kumar Jagarapu: So then you Yeshwanth Reddy Yerraguntla: used the word API connector, Vara Kumar Jagarapu: like Yeshwanth Reddy Yerraguntla: right? 01:34:36 Yeshwanth Reddy Yerraguntla: So that there is a general purpose API uh query tool that will be useful for all agents. Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: We can take that call until now. We don't need to really think of what to do right Vara Kumar Jagarapu: Okay. Sorry. Yeshwanth Reddy Yerraguntla: now. Vara Kumar Jagarapu: Yeah. Simply know it just letter can think of. Yeshwanth Reddy Yerraguntla: Yeah. Yeah. Vara Kumar Jagarapu: So next uh governance life cycle. Yeshwanth Reddy Yerraguntla: extremely unknown Vara Kumar Jagarapu: Um yeah Yeshwanth Reddy Yerraguntla: activity. Vara Kumar Jagarapu: actually prepare plan and Yeshwanth Reddy Yerraguntla: Sorry. Vara Kumar Jagarapu: discuss Yeshwanth Reddy Yerraguntla: Yeah. Yeah. Vara Kumar Jagarapu: we can go in Yeshwanth Reddy Yerraguntla: H So this question I Vara Kumar Jagarapu: deep. Yeshwanth Reddy Yerraguntla: I would say either you or I should take it Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: and this is P 0 right so yeah important that we crack it as soon as possible. Vara Kumar Jagarapu: Sure. Yeah. Maybe next we can discuss. 01:36:04 Yeshwanth Reddy Yerraguntla: satway transport uh in Vara Kumar Jagarapu: Yeah. Yeshwanth Reddy Yerraguntla: progress I don't know like implementation of data source and rag agreements Right. Vara Kumar Jagarapu: Wait Manisha Gundapuneedi: Huh? Vara Kumar Jagarapu: Yeah. Yeshwanth Reddy Yerraguntla: So, Manisha Gundapuneedi: Okay. Yeshwanth Reddy Yerraguntla: Are they rapist? Manisha Gundapuneedi: King of 46 Vara Kumar Jagarapu: agreements Manisha Gundapuneedi: 47 Yeshwanth Reddy Yerraguntla: Implementation Vara Kumar Jagarapu: and Yeshwanth Reddy Yerraguntla: of data source and drag agreements. Vara Kumar Jagarapu: correct. Yeshwanth Reddy Yerraguntla: Yeah. Second data source and drag agreements. Manisha Gundapuneedi: Are they agreements? Yeshwanth Reddy Yerraguntla: So Manisha Gundapuneedi: Click give now. Yeshwanth Reddy Yerraguntla: data source rag agreements. Vara Kumar Jagarapu: Um, Yeshwanth Reddy Yerraguntla: how data source talks with concepts of world model snapshot escalation rules and uh database. So when I say rag agreements I mean DB agreements on hybrid DB see concepts Vara Kumar Jagarapu: 100. Manisha Gundapuneedi: Control Yeshwanth Reddy Yerraguntla: world model snapshot all these things should be first thing inside a DB Vara Kumar Jagarapu: Sorry. Manisha Gundapuneedi: that good Yeshwanth Reddy Yerraguntla: refresh. share nothing. 01:38:40 Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: Yeah. Manisha Gundapuneedi: I'm like touch. Vara Kumar Jagarapu: Did they back up or kiss this Yeshwanth Reddy Yerraguntla: You play this Vara Kumar Jagarapu: code? Yeshwanth Reddy Yerraguntla: one second. Copy. Paste. Moj. Cool. Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: rag agreements with proper DB sources example. Okay, let me share my screen Vara Kumar Jagarapu: H. Yeshwanth Reddy Yerraguntla: agent agent.py Right? Can you see I'm saying enterprise agent these are the instructions this is technically this is the world model currently I don't want world model to be in code problem I can't change it everything I have to open the code and see what is Vara Kumar Jagarapu: H. Yeshwanth Reddy Yerraguntla: going on they if I put this in a posgress database where a table is called I don't know static data instructions table enterprise agent should fetch that from posgress directly and put it put that string here that Vara Kumar Jagarapu: H Yeshwanth Reddy Yerraguntla: way the code will be very uh minimal only we have to focus on writing clean uh tools for the code for the agent that is what I 01:40:38 Vara Kumar Jagarapu: clear. Yeshwanth Reddy Yerraguntla: meant in that row Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: right. Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: So maybe that wording is wrong. Vara Kumar Jagarapu: 46. Yeshwanth Reddy Yerraguntla: 46 data source. Sorry. Implementation of data source and rag agreements. Data source. Okay. Second implement value. They have unifier to work with, right? Manisha Gundapuneedi: No, sir. Yeshwanth Reddy Yerraguntla: Sorry. Then take up something other uh some other agent. Yeah, some agent. If the question is which one to take? Uh um I will suggest we go with Google agent only. Google. Why? Because we did some work in Google already. Agents law executing agent Manisha Gundapuneedi: Okay. Yeshwanth Reddy Yerraguntla: agent I know there is Google somewhere so they can learn learn they can Manisha Gundapuneedi: Yeah. Yeshwanth Reddy Yerraguntla: reuse those components modify them so that it is applicable to our architecture Vara Kumar Jagarapu: or data such as local GO. 01:42:25 Yeshwanth Reddy Yerraguntla: Google mail agent.py Google Gmail app. Gmail scheduleuler They were trying to do a lot of things in a very ad hoc way. So Arpit and Rahul can take up this and start cleaning up as per our architecture. What I'm trying to say Manisha Gundapuneedi: Okay. Yeshwanth Reddy Yerraguntla: basically the challenge is to shrink down the number of lines that are uh in the code for Google related features. So I will yeah I'll suggest go take up Gmail only implementation of rack cache and testing it out if not Gmail. Yeah. User persona and trainer persona. I think this is P P2 P1 Vara Kumar Jagarapu: Madam P already Manisha Gundapuneedi: Yeah. Yeshwanth Reddy Yerraguntla: user admin page Vara Kumar Jagarapu: admin Yeshwanth Reddy Yerraguntla: PE. Okay. One second. Cool. Vara Kumar Jagarapu: the description. Yeshwanth Reddy Yerraguntla: based on persona how the agent should work out. Vara Kumar Jagarapu: Previous Yeshwanth Reddy Yerraguntla: This is actually similar to these two are similar to each other. 01:44:43 Vara Kumar Jagarapu: just drag. Yeshwanth Reddy Yerraguntla: Cool. Vara Kumar Jagarapu: practice each other. I Yeshwanth Reddy Yerraguntla: Okay. Vara Kumar Jagarapu: only Yeshwanth Reddy Yerraguntla: Nice. And this while this is talking about how agents should respect should respect arbback ante. This on the other hand is uh how back end supplies arbback related info to agents distinction Vara Kumar Jagarapu: Have a minute. Yeshwanth Reddy Yerraguntla: agent okay the training life cycle I'm Sorry. So when the user says tomorrow from tomorrow onwards you give only bar charts on Napu it should go it somewhere that this is Vara Kumar Jagarapu: H. Yeshwanth Reddy Yerraguntla: how um this is AI specific how agent into agents and agents will update training update and use training info in from database. This is what I meant. Vara Kumar Jagarapu: I can sub the Yeshwanth Reddy Yerraguntla: How agents will update second Vara Kumar Jagarapu: reason. Yeshwanth Reddy Yerraguntla: user? Yeah. Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: Done. Implementation of data source and oh 01:46:44 Vara Kumar Jagarapu: That's a bit Yeshwanth Reddy Yerraguntla: sorry browser notification. Okay. Vara Kumar Jagarapu: better. Yeshwanth Reddy Yerraguntla: UI uh feature PPS to send send browser notification user interface core agent. Vara Kumar Jagarapu: feature of just okay at least notific Yeshwanth Reddy Yerraguntla: children. Vara Kumar Jagarapu: email Yeshwanth Reddy Yerraguntla: Oh Vara Kumar Jagarapu: WhatsApp Yeshwanth Reddy Yerraguntla: no. Vara Kumar Jagarapu: and WhatsApp P12. Yeshwanth Reddy Yerraguntla: We can do that. It's either way. It's fine. Vara Kumar Jagarapu: Okay. Yeah. Training life cycles. It's Yeshwanth Reddy Yerraguntla: Next training life cycle. Vara Kumar Jagarapu: 51. Yeshwanth Reddy Yerraguntla: Should system should auto understand escalation from data snapshot should Vara Kumar Jagarapu: I take a data snapshot. Yeshwanth Reddy Yerraguntla: send. Yeah. We can assign it to shaker. Create required tables to store runbooks. Define the mock data. Version management. If runbook updation is related to date, runbook updation is related to responding behavior towards user it considered acted accordingly. 01:49:18 Yeshwanth Reddy Yerraguntla: Further basically this is uh related to version management to some extent it is related to this guy. 48 to 52 somewhat related to each other in the sense that uh oh sorry this uh these two these two I think we leave leave them to Raja only we p the way and I don't want to go inside in depth News and insights related component is not covered initially. Vara Kumar Jagarapu: Okay. Sorry. user interface news and insights. Most probably it should not be under this age Yeshwanth Reddy Yerraguntla: This Vara Kumar Jagarapu: dashboard. Yeshwanth Reddy Yerraguntla: Yeah. Yeah. Pick them refresher. This Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: decent Vara Kumar Jagarapu: Okay. Pink color. So then Yeshwanth Reddy Yerraguntla: H. Vara Kumar Jagarapu: exactly Yeshwanth Reddy Yerraguntla: For every data source somewhere we have to write that table. Let me share my screen. Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: Sharing Gmail I have to refresh every 1 01:51:25 Vara Kumar Jagarapu: Uhhuh. Yeshwanth Reddy Yerraguntla: minute. G chat every 1 minute. show basic uh I mean Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: Ailia these people can do it Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: implementation Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: modules so every Okay. Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: Whatever number of minutes it will take Vara Kumar Jagarapu: that that that will trigger at that particular time. Uh that is clear Yeshwanth Reddy Yerraguntla: correct. Vara Kumar Jagarapu: and Yeshwanth Reddy Yerraguntla: Yes. Vara Kumar Jagarapu: So it needs to be wait until it get some Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: response right. So that will take the table and accordingly it will u push it. Okay, responses that will be taken care to send alert or to send something right. So job is receiving acknledgement success or Yeshwanth Reddy Yerraguntla: Yeah. Yes. Vara Kumar Jagarapu: failure. Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: task anyone can do right. Yeshwanth Reddy Yerraguntla: Yes. Vara Kumar Jagarapu: Clear Yeshwanth Reddy Yerraguntla: Anyway, this is P2 task, so it's not that important. 01:53:29 Vara Kumar Jagarapu: later. Yeshwanth Reddy Yerraguntla: actually. Vara Kumar Jagarapu: Uh, okay. Yeshwanth Reddy Yerraguntla: Oh, sorry, sorry, sorry, sorry. Oh, no, no, no. Sorry, sorry. Correct. Correct. Correct. So, receive all updates from all data source agents per refresh. Vara Kumar Jagarapu: and actually news Yeshwanth Reddy Yerraguntla: Uh, Vara Kumar Jagarapu: life. So that next research or something. Yeshwanth Reddy Yerraguntla: generate new cycle, Vara Kumar Jagarapu: Oh no. Yeshwanth Reddy Yerraguntla: right? Because it's a major uh feature. Uh yeah we that is why P that we are starting early. Vara Kumar Jagarapu: Maybe someone but yeah. Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: Yeah. Okay. Yeshwanth Reddy Yerraguntla: So Vara Kumar Jagarapu: Milestone. Okay. and Yeshwanth Reddy Yerraguntla: At that point, this will become milestone uh M2 Vara Kumar Jagarapu: okay and then Yeshwanth Reddy Yerraguntla: right. Vara Kumar Jagarapu: yeah I'll do it It Yeshwanth Reddy Yerraguntla: Yeah. Broadcast news to user aware agent. Vara Kumar Jagarapu: is. 01:55:23 Yeshwanth Reddy Yerraguntla: broadcast news to user aware agent. P1 P1 receive news from realtime agent. Uh, so P 0 Vara Kumar Jagarapu: P1. Yeshwanth Reddy Yerraguntla: P1 P1 Vara Kumar Jagarapu: Okay. Okay. Yeshwanth Reddy Yerraguntla: receive news from RT agent is a function of broadcasting news to user aware Vara Kumar Jagarapu: Right. Yeshwanth Reddy Yerraguntla: agent. Okay, actually from RT agent Vara Kumar Jagarapu: 57. This is Yeshwanth Reddy Yerraguntla: pull relevant users for news items. Designate news items to each other each user and push to UI agent again. Vara Kumar Jagarapu: Yeah. Okay. 58s. Oh, sorry. Sorry. Yeshwanth Reddy Yerraguntla: Jes Vara Kumar Jagarapu: Control. Okay. Sorry. Yeah. Yeshwanth Reddy Yerraguntla: configurable setup of data source wise refresh time. Vara Kumar Jagarapu: Fine. Yeshwanth Reddy Yerraguntla: Which data needs to be fetched? pingd at every refresh event mechanism for long running data sync. Same activity which is this Vara Kumar Jagarapu: So I will see the P 53. 01:57:22 Yeshwanth Reddy Yerraguntla: guy. Vara Kumar Jagarapu: three. Yeshwanth Reddy Yerraguntla: Yeah. Oh no. Oh no. Vara Kumar Jagarapu: So, Hello. So, can they get Yeshwanth Reddy Yerraguntla: Pick Vara Kumar Jagarapu: select? Yeshwanth Reddy Yerraguntla: user aware agent in call us data trigger them to UI agent to update again update knowledge Yes. Vara Kumar Jagarapu: But that's not okay. Yeshwanth Reddy Yerraguntla: 582 M2 but at the same time none of these are like super unknowns knowledge sync life complex either P1 Start Vara Kumar Jagarapu: 2 minutes a call. Yeah, Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: actually Yeshwanth Reddy Yerraguntla: Oh, nonunctional requirements. Vara Kumar Jagarapu: 180 Yeshwanth Reddy Yerraguntla: Okay, Vara Kumar Jagarapu: requ Yeshwanth Reddy Yerraguntla: got it. Vara Kumar Jagarapu: Okay. Knowledge sync. Yeshwanth Reddy Yerraguntla: Oh no. Vara Kumar Jagarapu: I think what is it? Yeshwanth Reddy Yerraguntla: Cont. Vara Kumar Jagarapu: Knowledge graphs Yeshwanth Reddy Yerraguntla: H first of all what is knowledge Vara Kumar Jagarapu: contain. Yeshwanth Reddy Yerraguntla: graphic whatever is happening in diwami today needs to be stored in that database whether it is a list of text files or a graph data structure or structured 02:02:07 Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: data we don't know but content is very clear that today whatever happened in Diwami I have to put it Vara Kumar Jagarapu: Today at any point of time, right? same snapshot knowledge graph. Yeshwanth Reddy Yerraguntla: Hand Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: out. Vara Kumar Jagarapu: Uh and then receive news updates compare against the previous snapshot the snapshot snapshot relevant items. Okay. Clear. Yeshwanth Reddy Yerraguntla: This should raer to take it because it's very complex Vara Kumar Jagarapu: And then next. Yeshwanth Reddy Yerraguntla: refresh insert and escalation life cycle. Could Vara Kumar Jagarapu: Refreshing Yeshwanth Reddy Yerraguntla: Okay. Vara Kumar Jagarapu: sets and escalation life cycle receive refreshing. Okay. Prevent duplicate refence data sources duplicate Yeshwanth Reddy Yerraguntla: Maybe two complaint duplicates to chrome. Actually, I'll tell you what I what I thought when I wrote it. Okay. by mistake. refresh agent to set the give me updates for Vara Kumar Jagarapu: Hm. Yeshwanth Reddy Yerraguntla: um um at 12:00 for some reason by mistake somewhere it should be remember that 5 minutes is too less of a time to do refresh 02:04:31 Vara Kumar Jagarapu: M. Yeshwanth Reddy Yerraguntla: anyway already 5 minutes back JSON so I will not use it. Sorry, I will not refresh. Instead, if you are asking at 1205, I'll give you the same refresh as that for 120:00. Vara Kumar Jagarapu: Okay. already Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: and it can be from job scheduleuler or it can be from Jira sorry user or Jira Yeshwanth Reddy Yerraguntla: User question. User question. User will never say refresh. Vara Kumar Jagarapu: refresh related to Yeshwanth Reddy Yerraguntla: Hert Vara Kumar Jagarapu: get I want to catch can handle later. Yeshwanth Reddy Yerraguntla: should handle. Yeah. Vara Kumar Jagarapu: So later we can think of it Yeshwanth Reddy Yerraguntla: So these are dam. Vara Kumar Jagarapu: before. Yeshwanth Reddy Yerraguntla: Okay. Vara Kumar Jagarapu: Yeah. on top of it. What we need based on updated time and creation time. Yeshwanth Reddy Yerraguntla: Oh Vara Kumar Jagarapu: Okay. Update self and indexes. Yeshwanth Reddy Yerraguntla: no. 02:06:46 Vara Kumar Jagarapu: Find a chest pet. Yeshwanth Reddy Yerraguntla: Refresh. are low. I need to update my data source agents DB example. Gmail when I fetch emails in the last 1 minute. What is one purpose of fetching emails to update my snapshot? Second, let's Vara Kumar Jagarapu: Hello. Yeshwanth Reddy Yerraguntla: say some will be important emails which might have sentiment which might have important action items things like that data source Vara Kumar Jagarapu: Mhm. Yeshwanth Reddy Yerraguntla: agent. It is not a snapshot by the way. It is just saying for these emails contain this information. So when I ask a question tomorrow saying give me all the angry mails from Vara Kumar Jagarapu: H Yeshwanth Reddy Yerraguntla: yesterday. Vara Kumar Jagarapu: already a sentiment wishes. and Yeshwanth Reddy Yerraguntla: It is a it is always a function of the data source agent. Vara Kumar Jagarapu: call. Yeshwanth Reddy Yerraguntla: When you design a data source, you will say what are the things that uh this agent should uh index. 02:08:26 Vara Kumar Jagarapu: Yeah, that needs to be planned better. Yeah. Clear. Clear and have the man derive in sets. Publish refresh insets. Yeah. Same similar thing. Yeshwanth Reddy Yerraguntla: H. Vara Kumar Jagarapu: What it may just be clear. Yeshwanth Reddy Yerraguntla: Yeah. Easy Manisha Gundapuneedi: Uh, are they actually in Vara Kumar Jagarapu: discussation Yeshwanth Reddy Yerraguntla: der. Yeah. Vara Kumar Jagarapu: question Yeshwanth Reddy Yerraguntla: Yeah. We can assign it to one of these two people. Again, Vara Kumar Jagarapu: Amen. Yeshwanth Reddy Yerraguntla: I manu I'm not happy with 58 59 60 61 being separate uh tasks. Yeah. Just check. Yeah. Yeah. Vara Kumar Jagarapu: Clear. Yeshwanth Reddy Yerraguntla: N Manisha Gundapuneedi: where I Refreshing. Yeshwanth Reddy Yerraguntla: H. Oh Vara Kumar Jagarapu: It can be from user also, Yeshwanth Reddy Yerraguntla: no. Vara Kumar Jagarapu: right? Okay. refreshing. Okay. Yeshwanth Reddy Yerraguntla: Um. 02:10:46 Vara Kumar Jagarapu: It will ask RT agent to get the updates. Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: It is finally message send right that is get updates refresh at the end of the day it is asking Yeshwanth Reddy Yerraguntla: Yes. Vara Kumar Jagarapu: something like get updates. Okay then similar user user also like asking get the J updates. Yeshwanth Reddy Yerraguntla: Difference center. Brendit Lono I understand that to agent you are trying to send get Jira updates which is the same string and in the form of message/ send protocol but crucially the difference is going to be we we will send metadata saying uh this question is being asked by refresh agent or scheduleuler whereas this question is being asked by Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: vend Vara Kumar Jagarapu: Okay. Um, Yeshwanth Reddy Yerraguntla: metadata that is the only way we have to I mean we have to ensure that uh for user the answers are always very Vara Kumar Jagarapu: okay. Yeshwanth Reddy Yerraguntla: quick. So give me latest updates more or less likely when user is asking 02:12:11 Vara Kumar Jagarapu: Please can it just Yeshwanth Reddy Yerraguntla: question So that is what I mean by having different Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: uh uh functionality for the same Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: question. Vara Kumar Jagarapu: So, user data is okay. Yeshwanth Reddy Yerraguntla: Yes. You understand what? Vara Kumar Jagarapu: user data source key. Yeah, we have a differentiation whether it is came from uh like right whenever you updating snapshots right at Yeshwanth Reddy Yerraguntla: All right. Vara Kumar Jagarapu: least specific system but it This came something like I need updates till now till now like when it comes to there like the snapshot is available till morning 8:00 a.m. but user ask around 400 p.m. in the evening uh Yeshwanth Reddy Yerraguntla: Okay. And the refresh agent hasn't updated it yet. Vara Kumar Jagarapu: because the scheduleuler might be running uh 24 hours or Yeshwanth Reddy Yerraguntla: It's been 24 hours. Vara Kumar Jagarapu: 12 hours whatever it may be. Yeshwanth Reddy Yerraguntla: Yeah. Right. Vara Kumar Jagarapu: datations 02:13:55 Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: allows Yeshwanth Reddy Yerraguntla: Good question. So definitely I see what you mean. Um if Jira is not refreshing very frequently but Naven still want something out of it. Um point. Ideally Vara Kumar Jagarapu: Uh we have to get that information user Yeshwanth Reddy Yerraguntla: situation Vara Kumar Jagarapu: level. Okay, but it's temporary. Maybe we can delete it later. System questions. Yeshwanth Reddy Yerraguntla: Right. Vara Kumar Jagarapu: Not good. Yeshwanth Reddy Yerraguntla: Open question. What I think is uh perhaps we if the user who is asking is uh team lead that person can also ask what are the updates since last 1 hour right and on an on an ideal basis the system should answer it in that case in that case Vara Kumar Jagarapu: Yes. Yeshwanth Reddy Yerraguntla: maybe it can do uh whatever refresh refresh it is sending to data agent it will fetch the latest updates it will send to the user and then it might say realtime agent ad hoc refresh you can take this information and update your snapshot because I don't want to waste that information we can 02:15:57 Vara Kumar Jagarapu: Yeah. Yeshwanth Reddy Yerraguntla: perhaps take that route also Hold on. Vara Kumar Jagarapu: What level system again we need to validate. Yeshwanth Reddy Yerraguntla: That is applicable every time that is applicable all the time. Vara Kumar Jagarapu: Yeah. User level system. Yeshwanth Reddy Yerraguntla: Yeah. If if it is a genuine update, I will first answer give the answer to user and then I will say let me update my own knowledge base. Anyway, I was supposed to update it 4 hours later. I will update it right now. Vara Kumar Jagarapu: Okay. Yeah. then or temporarily what we can do is uh uh whenever user asks right then system we can extract the information and store okay sorry Yeshwanth Reddy Yerraguntla: Exactly. User Vara Kumar Jagarapu: maybe uh user Yeshwanth Reddy Yerraguntla: Uh okay. Vara Kumar Jagarapu: key. Yeshwanth Reddy Yerraguntla: Okay. This is better. Actually, what I was thinking was more limited. What you're saying makes sense. Vara Kumar Jagarapu: Yeah. 02:18:03 Vara Kumar Jagarapu: will be taking decision what to send to that user. Yeshwanth Reddy Yerraguntla: Right. Right. Vara Kumar Jagarapu: Yeah. Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: Uh Manisha clear. Manisha Gundapuneedi: How Vara Kumar Jagarapu: Uh discussion clear Manisha Gundapuneedi: clear? Vara Kumar Jagarapu: questions. Okay. Okay. Sorry. demo. You can list it down and you can ask Right. Manisha Gundapuneedi: Yeah. Okay. Vara Kumar Jagarapu: Okay. Manisha Gundapuneedi: So, Vara Kumar Jagarapu: H Yeshwanth Reddy Yerraguntla: Rashid missing slow. Manisha Gundapuneedi: Okay. Screen juice. Yeshwanth Reddy Yerraguntla: Sorry. One thing is Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: life cycle. Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: is there I understand they are subtask they need to be Vara Kumar Jagarapu: Yeah. Anywhere like as we discussed they can do it on the go researchers. Yeshwanth Reddy Yerraguntla: separate Vara Kumar Jagarapu: Yeah. Yeshwanth Reddy Yerraguntla: point yeah they will have to come up with detailed subtasks and their acceptance criteria. So key the first task is going to be explore so and so task 02:20:36 Vara Kumar Jagarapu: Yeah. Okay. Yeshwanth Reddy Yerraguntla: JSON JP Vara Kumar Jagarapu: Select Yeshwanth Reddy Yerraguntla: cool technique Vara Kumar Jagarapu: uh Yeshwanth Reddy Yerraguntla: in Rosal Paris shoes. Vara Kumar Jagarapu: multiple rows of the chest. Yeshwanth Reddy Yerraguntla: Okay. Okay. Nice. Vara Kumar Jagarapu: Yeah, Yeshwanth Reddy Yerraguntla: User preference P3. Vara Kumar Jagarapu: like Yeshwanth Reddy Yerraguntla: Sorry. P3. Am I right? But tasks itself can they be P2, P1 and H. Refresh agents life cycle. Trigger schedule configure setup ping to get insights from the date and trigger them to email. Vara Kumar Jagarapu: Then 545 was delayed with JSON just Yeshwanth Reddy Yerraguntla: Yeah. 55 task which means HR news. Okay. Craft knowledge sync life cycle generating new cycle. You see all updates the uh fetch arc snapshot update snapshot actually 53 and 56 55 53 55 Vara Kumar Jagarapu: Three. Yeshwanth Reddy Yerraguntla: 56 Vara Kumar Jagarapu: Rash in there. Yeshwanth Reddy Yerraguntla: I think 55 is a super set of 53 53 56 55 significant overlap 02:23:12 Vara Kumar Jagarapu: Oh, Yeshwanth Reddy Yerraguntla: 54 is separate. Um Vara Kumar Jagarapu: P 0 P 0 P2 Actually Yeshwanth Reddy Yerraguntla: 53 54 55. Are we breaking it properly? basic question. Vara Kumar Jagarapu: there will be kind of overlapping Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: one person remaining Dr. Chescoli Yeshwanth Reddy Yerraguntla: Yeah. See refresh agent life cycle is starting from pinging all data source agents and ending it uh calling user aware insight agent sorry then call the and alert engine to get insights so Vara Kumar Jagarapu: H. Yeshwanth Reddy Yerraguntla: that trigger them to UI life cycle uh uh what is it uh alert refresh create required 54 different cycles. Now screen first two points are one life cycle uh consolidate e life cycle consolidate fetched information and update knowledge Vara Kumar Jagarapu: H. Yeshwanth Reddy Yerraguntla: base is becoming actually Vara Kumar Jagarapu: Um. Yeshwanth Reddy Yerraguntla: 53 Vara Kumar Jagarapu: Um. Yes. Yes. Yes. 53. Yeshwanth Reddy Yerraguntla: 53 55 update knowledge base on that itself is 02:25:07 Vara Kumar Jagarapu: 55 Yeshwanth Reddy Yerraguntla: one whole life cycle Then we are Vara Kumar Jagarapu: 5 Yeshwanth Reddy Yerraguntla: saying fetch snapshot 53 broadcast news to user aware agent uh so that I can send to UI agent basically. Vara Kumar Jagarapu: Let's Yeshwanth Reddy Yerraguntla: So the refresh agent life cycle itself is covering 53 and 55 it should break it Vara Kumar Jagarapu: see. Yeshwanth Reddy Yerraguntla: down. Vara Kumar Jagarapu: Uh Yeshwanth Reddy Yerraguntla: All I'm saying is we should break this down end points thesis and this is simply talking about refresh agents life cycle. This is basically saying I will ping the realtime agent I'll get back uh something job done or not. Vara Kumar Jagarapu: Okay. Okay. Okay. Clear. Clear. Yeshwanth Reddy Yerraguntla: So this can go up. Then we have uh darata Vara Kumar Jagarapu: Snapshot updation. Yeshwanth Reddy Yerraguntla: news knowledge graph sync life cycle is very complex. Receiving all fetch arc snapshot update snapshot. So receive all updates from data source engine Vara Kumar Jagarapu: This is it. 02:26:40 Yeshwanth Reddy Yerraguntla: per directly. Basically we are saying receive uh latest snapshot and uh broadcast news to user aware agent from RT agent broadcast news life cycle relevant users from news items designate to each and push to UI actually all I'm saying is I'll get the latest snapshot which is anyway done in all its Sync life cycle. Vara Kumar Jagarapu: steps. Yeshwanth Reddy Yerraguntla: This itself is a large enough task for them. Generate and Vara Kumar Jagarapu: Uh Yeshwanth Reddy Yerraguntla: broadcast. Vara Kumar Jagarapu: yeah. Okay. Okay. Clear. Yeshwanth Reddy Yerraguntla: This can go to Amulia. This can go to Har. Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: This is also P in my head like this is the whole brain of the system. So and yeah is taking care of uh agent between art data source agent user interface agent real agent user aware agent Vara Kumar Jagarapu: Actually, Yeshwanth Reddy Yerraguntla: L Vara Kumar Jagarapu: Yeah. Uh Yeshwanth Reddy Yerraguntla: cycle 02:28:47 Vara Kumar Jagarapu: maybe Yeshwanth Reddy Yerraguntla: cycle. Vara Kumar Jagarapu: at least responsibility. Yeah. Yeshwanth Reddy Yerraguntla: Mhm. Vara Kumar Jagarapu: But yeah. Yeshwanth Reddy Yerraguntla: Okay. Vara Kumar Jagarapu: Go Yeshwanth Reddy Yerraguntla: Refresh insights and escalation. These were unnecessary, right? Vara Kumar Jagarapu: answers. Yeah. Yeshwanth Reddy Yerraguntla: H user aware agent to data source agent. Vara Kumar Jagarapu: For Yeshwanth Reddy Yerraguntla: delete. Yeah. Vara Kumar Jagarapu: example, real Yeshwanth Reddy Yerraguntla: Hold on. Vara Kumar Jagarapu: Amaz. Yeshwanth Reddy Yerraguntla: Yeah, I mean this is technically one piece of code. So correct life cycle. Lot of life cycles pass through this one guy. Makes sense. Uh can take care of this part. Vara Kumar Jagarapu: We'll be getting this snapshot saving and receiving. Yeshwanth Reddy Yerraguntla: Oh. Oh no. Vara Kumar Jagarapu: databases. Yeshwanth Reddy Yerraguntla: 105. Oh. Vara Kumar Jagarapu: Okay. Real three parts functions right. Yeshwanth Reddy Yerraguntla: H. Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: Uh, okay. But uh, everyone is working on the same agent. 02:32:30 Vara Kumar Jagarapu: independent function different Yeshwanth Reddy Yerraguntla: Understood. Vara Kumar Jagarapu: function functions implement. Yeshwanth Reddy Yerraguntla: Got it. Makes Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: sense. life cycles. The functionalities that they have to take care of are refresh Vara Kumar Jagarapu: H. Yeshwanth Reddy Yerraguntla: agent pinging the realtime agent receiving sending it to Q receiving acknowledgement. Yeah. Vara Kumar Jagarapu: Independent system. Yeshwanth Reddy Yerraguntla: Right. Compare update. Each of these is its own function. Okay. Vara Kumar Jagarapu: Uh create Yeshwanth Reddy Yerraguntla: Got it. Refresh. Vara Kumar Jagarapu: more clarity mean. Hello And Manisha Gundapuneedi: Huh? Vara Kumar Jagarapu: incrementally Yeshwanth Reddy Yerraguntla: questions there. Sorry. Vara Kumar Jagarapu: incrementally at least like we are approaching to Consultate and Yeshwanth Reddy Yerraguntla: At any point if you feel you're going technically in Vara Kumar Jagarapu: appoint Yeshwanth Reddy Yerraguntla: depth execution Manisha Gundapuneedi: Execution. Yeshwanth Reddy Yerraguntla: when I say when I'm about to give this task to I not saying what she should do I am saying first explore this topic this is what you are planning to what are all the things that you have to get clarity on to start execution. 02:35:35 Yeshwanth Reddy Yerraguntla: So she should understand which parts of the code she should modify, what functions she has to write uh how to set up mark data, what uh uh things she has to test uh how to write uh tests for this feature. None of these are code related in the sense that she's not writing code. She's all right. She's only writing what she's about to write. Manisha Gundapuneedi: Okay. Yeshwanth Reddy Yerraguntla: Acceptance. Acceptance criteria. A very big a very detailed uh MD file containing all these items. either Raj Shaker or I will go through it properly. No, because she and I are sitting only on that one feature. It is now better to forget everything, focus only on that one thing and go you will go in detail how she did correct point correct. It might take one or two hours but the discussion will give rise to proper technical implementations at which point she'll now create all the tasks. Manisha Gundapuneedi: Oh. Yeshwanth Reddy Yerraguntla: We will waste a lot of time. 02:37:13 Manisha Gundapuneedi: What can Yeshwanth Reddy Yerraguntla: I think Vara Kumar Jagarapu: Sorry. Yeshwanth Reddy Yerraguntla: yeah I mean whichever way Vara Kumar Jagarapu: At Yeshwanth Reddy Yerraguntla: uh I'm fine whichever direction we'll take right Vara Kumar Jagarapu: least Yeshwanth Reddy Yerraguntla: We'll actually start going forward in Vara Kumar Jagarapu: We can rearrange these things and I think right test All proper Yeshwanth Reddy Yerraguntla: Yeah, actually Because like Vara Kumar Jagarapu: hood Yeshwanth Reddy Yerraguntla: chicken functionalities functionalities now several people have to come together for testing it. Vara Kumar Jagarapu: M. Yeshwanth Reddy Yerraguntla: There is no testing owner. Vara Kumar Jagarapu: Yes. I Yeshwanth Reddy Yerraguntla: On the other hand, it protects life cycle, Vara Kumar Jagarapu: think Yeshwanth Reddy Yerraguntla: you can test the whole cycle end to end because you're writing the whole code end to end. The only issue h the Vara Kumar Jagarapu: Delables test life cycles program Yeshwanth Reddy Yerraguntla: only problem we the whole reason we started this discussion was some cycles were subsets Vara Kumar Jagarapu: overlapping. Yeshwanth Reddy Yerraguntla: of larger cycles. So larger cycles 02:39:14 Vara Kumar Jagarapu: Yeah, I Yeshwanth Reddy Yerraguntla: decomposing which basically Vara Kumar Jagarapu: think Yeshwanth Reddy Yerraguntla: means Vara Kumar Jagarapu: Oh. Yeshwanth Reddy Yerraguntla: track saying we we don't need these things already. They can continue. Vara Kumar Jagarapu: Okay. Yeah. Yeshwanth Reddy Yerraguntla: Mig yeah P2 M2 we will know how to start tracking and how to start prioritizing which one to start first all those things Manisha Manisha Gundapuneedi: Turn. Yeshwanth Reddy Yerraguntla: I'm sure The moment you have them ready, your task is to generate more tasks. Uh start exploring by going through previous documentations. So previous notes actually if I open up uh enterprise I enter Vara Kumar Jagarapu: My Good experience. Yeshwanth Reddy Yerraguntla: price. One thing I did is whatever discussions we had uh conversations on a folder every conversation we had in uh with everyone up to March 5th, right? Any text file say so you can always use an agent and uh make it understand what is going Vara Kumar Jagarapu: Money. Yeshwanth Reddy Yerraguntla: on. 02:42:01 Yeshwanth Reddy Yerraguntla: So they can use these conversations and let the AI know what they are trying to do. They can always uh what do you call tell key this is the feature I'm trying to build according to these discussions what should I be doing. So charge jet itself will guide them output once they are creating Jira task once they create the documentation then our jobs will become to read the documentation and correct them Manisha Gundapuneedi: H. Yeshwanth Reddy Yerraguntla: they will get started and hopefully either tomorrow day after tomorrow they'll have something to start showing. Manisha Gundapuneedi: Sorry. Nighting. Yeshwanth Reddy Yerraguntla: Give this give these tasks and give this information. Okay. Yeah. Vara Kumar Jagarapu: You know uh maybe tomorrow or day after tomorrow next 3 days couple of days maybe available Yeshwanth Reddy Yerraguntla: Okay. Vara Kumar Jagarapu: procedure. Yeshwanth Reddy Yerraguntla: Mhm. Vara Kumar Jagarapu: So just Yeshwanth Reddy Yerraguntla: Okay. Yeah. Yeah. Okay. Yeah. By that time once these people have their uh uh expectations 02:43:39 Vara Kumar Jagarapu: accept Yeshwanth Reddy Yerraguntla: uh um it's okay I think we can cool down a little and uh try to focus on our own tasks individual tasks Vara Kumar Jagarapu: Yeah. Yeah. Yeshwanth Reddy Yerraguntla: not Vara Kumar Jagarapu: Initial task bit exploring while they will get some clarity today. Yeshwanth Reddy Yerraguntla: Yes. Vara Kumar Jagarapu: They can go through the diagram once understand the flows. Yeshwanth Reddy Yerraguntla: Yes. Yes. Vara Kumar Jagarapu: Tomorrow mornings they can questions Yeshwanth Reddy Yerraguntla: Not just understand the flows. Vara Kumar Jagarapu: and Yeshwanth Reddy Yerraguntla: I'm saying they can also use the conversations in the that too. Vara Kumar Jagarapu: Yeah. Yeshwanth Reddy Yerraguntla: Make charge understand everything. Vara Kumar Jagarapu: Yeah. So on top of it morning structure and all Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: and they'll be equipped to do them like we at least Yeshwanth Reddy Yerraguntla: Yes. Yes. Vara Kumar Jagarapu: Manisha me or uh people will answer Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: Yeah. Okay. Yeshwanth Reddy Yerraguntla: So everyone should have some task on the Jira Manisha Gundapuneedi: Okay. Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: actually not Vara Kumar Jagarapu: Okaser. Manisha Gundapuneedi: Okay. Yeshwanth Reddy Yerraguntla: before we Manisha Gundapuneedi: what they going to do. Once they're done with elaboration, they can start working on the task. Few tasks plus priorities. Yeshwanth Reddy Yerraguntla: Yeah. Okay. Drop out. Bye. Bye. Transcription ended after 02:46:28 This editable transcript was computer generated and might contain errors. People can also change the text after it was created.