Mar 4, 2026 Enterprise Brain - V2 - Arch - Transcript 00:00:00 Yeshwanth Reddy Yerraguntla: Hi bro. Rajashekar G: Hi now. Vara Kumar Jagarapu: Hey, Yeshwanth Reddy Yerraguntla: Hi in Rajashekar G: Hi bro. Vara Kumar Jagarapu: she Yeshwanth Reddy Yerraguntla: um Excel to I have it Rajashekar G: We'll call Manisha. Yeshwanth Reddy Yerraguntla: back. Rajashekar G: Manisha calls us. Yeshwanth Reddy Yerraguntla: Sure. Vara Kumar Jagarapu: Maybe iteration discussions. Maybe we can start. What is clear? Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: Naku and system. Yeshwanth Reddy Yerraguntla: Mhm. Are you definitely please uh tell us? Vara Kumar Jagarapu: knowledge. Yeshwanth Reddy Yerraguntla: No definitely if something is not uh um striking well either there is a gap in your knowledge or it's Vara Kumar Jagarapu: Uh Yeshwanth Reddy Yerraguntla: genuinely wrong. Both ways it's important to address. Vara Kumar Jagarapu: We need to make Yeshwanth Reddy Yerraguntla: Mhm. Vara Kumar Jagarapu: it gateway. So there should be some gateway that we need to keep it there to route it. Yeshwanth Reddy Yerraguntla: Do you want to discuss it on the canvas? What that? Vara Kumar Jagarapu: But yeah, 00:07:54 Yeshwanth Reddy Yerraguntla: Yeah. Yeah. No. No. Let's discuss. Shall I share my screen? Yeah. Yeah. One second. Vara Kumar Jagarapu: back microserite Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: Yeah. Yeshwanth Reddy Yerraguntla: Which one are you talking about? Vara Kumar Jagarapu: The core. Yeshwanth Reddy Yerraguntla: Uh go. Vara Kumar Jagarapu: The core. Middle. Yeah. Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: So, alert insights excl something whatever it may be. Uh we different different Yeshwanth Reddy Yerraguntla: Is it to coordinate or tomorrow? Vara Kumar Jagarapu: but thought. Yeah. Maybe discuss points clarity on top of Yeshwanth Reddy Yerraguntla: Okay. Vara Kumar Jagarapu: it. Yeshwanth Reddy Yerraguntla: Manisha answer. Vara Kumar Jagarapu: Huh? Rajashekar G: I'm Manisha Gundapuneedi: Wonderful. Vara Kumar Jagarapu: Already joined. She good Yeshwanth Reddy Yerraguntla: Oh no. Okay. Rajashekar G: nice. Vara Kumar Jagarapu: morning. Yeshwanth Reddy Yerraguntla: Manisha. Okay. Manisha Gundapuneedi: He's okay with it. 00:10:52 Yeshwanth Reddy Yerraguntla: Hold Manisha Gundapuneedi: Um, Yeshwanth Reddy Yerraguntla: on. Manisha Gundapuneedi: he's happy. Uh he Yeshwanth Reddy Yerraguntla: H Manisha Gundapuneedi: said he was asking questions on data engineering. Sorry. data engine classification regression related question and Yeshwanth Reddy Yerraguntla: or Manisha Gundapuneedi: uh and Yeshwanth Reddy Yerraguntla: Okay. Manisha Gundapuneedi: last update on Yeshwanth Reddy Yerraguntla: Okay. Manisha Gundapuneedi: Rahul Yeshwanth Reddy Yerraguntla: Wow. Vara Kumar Jagarapu: Okay. Manisha Gundapuneedi: Ganesha. Vara Kumar Jagarapu: Pricing. Manisha Gundapuneedi: UI actually Yeshwanth Reddy Yerraguntla: Okay. Recording. Manisha Gundapuneedi: meeting recording. Huh? Yeshwanth Reddy Yerraguntla: Oh. Mhm. Manisha Gundapuneedi: So Yeshwanth Reddy Yerraguntla: Okay. Vara Kumar Jagarapu: Turn window. Manisha Gundapuneedi: local model Rajashekar G: Okay. Okay. Manisha Gundapuneedi: Gemini Rajashekar G: Only P 0. Yeshwanth Reddy Yerraguntla: Yeah. Yeah. Rajashekar G: Sure. Yeshwanth Reddy Yerraguntla: Sure. Um owners see there are so many Manisha Gundapuneedi: in a hospital acceptance criteria and features Rajashekar G: streams of Yeshwanth Reddy Yerraguntla: perspect Manisha Gundapuneedi: expansion. Foreign speech. Foreign speech. Foreign speech. 00:14:09 Yeshwanth Reddy Yerraguntla: Exploration discussion verify. Vara Kumar Jagarapu: Like we already written some acceptance that can be well written Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: like if you have some decisions that you need to change acceptance accordingly and related Yeshwanth Reddy Yerraguntla: Yeah. Okay. Vara Kumar Jagarapu: Yeah. People might not be satisfied. So four at Yeshwanth Reddy Yerraguntla: Yes. Vara Kumar Jagarapu: least and okayify already Yeshwanth Reddy Yerraguntla: There is no list of visualizations that we prepared. Okay. Vara Kumar Jagarapu: of the features which you Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: Okay. Vara Kumar Jagarapu: Okay. Uh so best practices Yeshwanth Reddy Yerraguntla: Okay. Sorry. Sorry. Vara Kumar Jagarapu: management and history management. management for example. Yeshwanth Reddy Yerraguntla: Mhm. Vara Kumar Jagarapu: So what are we following for example? So next we have to come to an alignment session and history. Yeshwanth Reddy Yerraguntla: Okay. Session straight forward. Basically you have a DB of uh the structured DB 00:16:42 Vara Kumar Jagarapu: H Yeshwanth Reddy Yerraguntla: post you have user Vara Kumar Jagarapu: okay Yeshwanth Reddy Yerraguntla: um chat uh id chat messages JSON Vara Kumar Jagarapu: session Yeshwanth Reddy Yerraguntla: back end. Vara Kumar Jagarapu: back front end academic Yeshwanth Reddy Yerraguntla: Yeah. Front end code. Vara Kumar Jagarapu: Okay. Okay. Yeah. Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: Okay. Let it be. That's fine. Now we can send Yeshwanth Reddy Yerraguntla: For now. We can send full history to a We can always Vara Kumar Jagarapu: present. Okay. Yeshwanth Reddy Yerraguntla: compact it Vara Kumar Jagarapu: There Yeshwanth Reddy Yerraguntla: later. Rajashekar G: History is different and this is different history management. Vara Kumar Jagarapu: is Yeshwanth Reddy Yerraguntla: Uh history. Okay. Okay. Uh Rajashekar G: While charting the previous context Yeshwanth Reddy Yerraguntla: exact swap JSON. Rajashekar G: took Yeshwanth Reddy Yerraguntla: Okay, Vara Kumar Jagarapu: Yeah. Yeshwanth Reddy Yerraguntla: we can always compact it uh to write last 10 Rajashekar G: All right. 00:18:17 Yeshwanth Reddy Yerraguntla: messages. Vara Kumar Jagarapu: Okay. Rajashekar G: Okay. Vara Kumar Jagarapu: Right. Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: Best practice compact it once uh Vara Kumar Jagarapu: Oh, no. Yeshwanth Reddy Yerraguntla: token context window hits uh 85%. Vara Kumar Jagarapu: Yeah. Rajashekar G: cont. Sorry. Context window. Okay. Got it. Yeshwanth Reddy Yerraguntla: Jim has a larger window. Open has a smaller Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: window. Vara Kumar Jagarapu: fixtures Yeshwanth Reddy Yerraguntla: agent. Vara Kumar Jagarapu: limit. Yeshwanth Reddy Yerraguntla: This is a common behavior. Vara Kumar Jagarapu: already. Yeshwanth Reddy Yerraguntla: Correct. Vara Kumar Jagarapu: Okay. Okay. Yeshwanth Reddy Yerraguntla: Got it. Vara Kumar Jagarapu: Right. Yeshwanth Reddy Yerraguntla: Where will UI agent code be Vara Kumar Jagarapu: Uh Yeshwanth Reddy Yerraguntla: implemented? Vara Kumar Jagarapu: forward user interface. Very nice. Yeshwanth Reddy Yerraguntla: Yeah. Back front end. Vara Kumar Jagarapu: Okay. Yeah. Yeshwanth Reddy Yerraguntla: One sec. Vara Kumar Jagarapu: Yeah. Okay. Responsibilities nothing but notifications. 00:21:12 Vara Kumar Jagarapu: notifications Rajashekar G: only Vara Kumar Jagarapu: part. Rajashekar G: UI. Vara Kumar Jagarapu: Yeah, we'll go with the third Rajashekar G: Yeah. Vara Kumar Jagarapu: point. Yeah, third point. Acceptance. Rajashekar G: Here's Vara Kumar Jagarapu: There should be Rajashekar G: that Vara Kumar Jagarapu: person. Rajashekar G: multiple. How we going to handle that? Vara Kumar Jagarapu: for Yeshwanth Reddy Yerraguntla: H. Vara Kumar Jagarapu: example cascading effect. Yeshwanth Reddy Yerraguntla: Oh no, conflicting in my view there is no hierarchy trainer is one trainer. Vara Kumar Jagarapu: Okay. Single. Yeshwanth Reddy Yerraguntla: How many number of people are there? Vara Kumar Jagarapu: Okay. Yeah. Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: Then uh Yeshwanth Reddy Yerraguntla: Okay. alignment trainers. Vara Kumar Jagarapu: next Yeshwanth Reddy Yerraguntla: That's the only key concern that we have to address. Um because everyone is working for the same organization. Vara Kumar Jagarapu: All Yeshwanth Reddy Yerraguntla: Um the everyone should have a single Vara Kumar Jagarapu: right. Yeshwanth Reddy Yerraguntla: opinion. Yeah. 00:23:19 Yeshwanth Reddy Yerraguntla: The the places they will touch will change. Engineer best practices were on designer best practices where on so they will update different parts of the knowledge base that occurred Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: problem. Vara Kumar Jagarapu: So, Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: Then that is fine. Yeshwanth Reddy Yerraguntla: Oh, Vara Kumar Jagarapu: Uh Yeshwanth Reddy Yerraguntla: probably. Vara Kumar Jagarapu: just Rajashekar G: Every Yeshwanth Reddy Yerraguntla: Um, Rajashekar G: role will be user and ro will be admin. based on Vara Kumar Jagarapu: Okay. Rajashekar G: that Yeshwanth Reddy Yerraguntla: sorry. Rajashekar G: but one person can act as a trainer as well as user cover. Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: Oh, Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: there is no trainer mode user mode though if that's what you're asking. Vara Kumar Jagarapu: chart instruction that he wants to remember in a system. Yeshwanth Reddy Yerraguntla: Mhm. Vara Kumar Jagarapu: Okay. So that will be going to admin intention. Yeshwanth Reddy Yerraguntla: admin page. is low. Who is a trainer? 00:25:43 Yeshwanth Reddy Yerraguntla: Who is not a trainer? and it's search. Vara Kumar Jagarapu: Uh okay. It's a kind of configuration. Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: Uh okay. admin not related to anything about Yeshwanth Reddy Yerraguntla: Land Vara Kumar Jagarapu: kind of settings will be storing as a role rightific. Rajashekar G: Okay. Vara Kumar Jagarapu: Okay. Okay. Yeah. Rajashekar G: Oh no. Okay. Vara Kumar Jagarapu: Okay. Most probably seventh row. Seventh. Yeshwanth Reddy Yerraguntla: critical messages. Vara Kumar Jagarapu: to send. Yeshwanth Reddy Yerraguntla: Yeah. Yeah. Vara Kumar Jagarapu: Okay. List of alert received notification window or Yeshwanth Reddy Yerraguntla: Hunter Vara Kumar Jagarapu: something. List of alerts received in a Rajashekar G: UI side discussion Vara Kumar Jagarapu: notification. Rajashekar G: point. Vara Kumar Jagarapu: Okay. This measures can be Yeshwanth Reddy Yerraguntla: This uh front button. Vara Kumar Jagarapu: WhatsApp. Yeshwanth Reddy Yerraguntla: One thing we can probably do is show browser Vara Kumar Jagarapu: So we frozen. 00:28:42 Yeshwanth Reddy Yerraguntla: notification. Vara Kumar Jagarapu: Okay. Closer notific. if okay is not a part of Yeshwanth Reddy Yerraguntla: I mean, Vara Kumar Jagarapu: website. Yeshwanth Reddy Yerraguntla: yeah, it's still not a part of website. Vara Kumar Jagarapu: M Yeshwanth Reddy Yerraguntla: True. Vara Kumar Jagarapu: okay P to our next negative. Yeshwanth Reddy Yerraguntla: Yeah, Vara Kumar Jagarapu: Second last one. Okay. Next. Yeah. Yeshwanth Reddy Yerraguntla: Uh-huh. I mean just a Rajashekar G: I actually design. Vara Kumar Jagarapu: So, Rajashekar G: So this Yeshwanth Reddy Yerraguntla: design Rajashekar G: one Vara Kumar Jagarapu: What is it? H Rajashekar G: everyone will involve. Vara Kumar Jagarapu: okay. Okay. Which needs to be checked with different people. Rajashekar G: Okay. Vara Kumar Jagarapu: Okay. Next. Yeah. Core isn't related. Yeah. Yeshwanth Reddy Yerraguntla: Choose several orchestrations. Uh agent between RT agent and user interface agent. RT agent and user interface agent. 00:31:16 Yeshwanth Reddy Yerraguntla: Uh okay answers. Fair enough. News broadcast add answers data source key questions and uh refresh create required databases implementation of required tools. Okay. So question orchestration implementation plan knowledge based structures need to be managed. Database schemas need to be discussed and implemented. Confirmation of Postgress and um only Vara Kumar Jagarapu: Uhhuh. Yeshwanth Reddy Yerraguntla: Postgress. Vara Kumar Jagarapu: on top of it. Psychopg Yeshwanth Reddy Yerraguntla: Mhm. Oh, Vara Kumar Jagarapu: or Yeshwanth Reddy Yerraguntla: okay. Vara Kumar Jagarapu: something Yeshwanth Reddy Yerraguntla: Has easy, straightforward, reasonably. Vara Kumar Jagarapu: required, new tools or something else. Yeshwanth Reddy Yerraguntla: Okay. items. So I have to sit on these and figure out what needs to be Vara Kumar Jagarapu: Okay. Okay. So maybe Yeah. Yeshwanth Reddy Yerraguntla: done. Vara Kumar Jagarapu: Okay. Okay. Nice. Yeshwanth Reddy Yerraguntla: be finalized. What is data agent query tool on a Vara Kumar Jagarapu: already agent data source agent 00:33:10 Rajashekar G: Good Yeshwanth Reddy Yerraguntla: question? Rajashekar G: point. Vara Kumar Jagarapu: already. Yeshwanth Reddy Yerraguntla: Okay. Sorry. Sorry. Vara Kumar Jagarapu: Okay. Uh intention Okay. Yeshwanth Reddy Yerraguntla: Orchestration is what we will Vara Kumar Jagarapu: Yeah. Yeshwanth Reddy Yerraguntla: do. Vara Kumar Jagarapu: Okay. So that we can proceed on it. Right. Yeshwanth Reddy Yerraguntla: Okay. Vara Kumar Jagarapu: Yeah. Next. P. Okay. Next. Yeshwanth Reddy Yerraguntla: into the alert life cycle Rajashekar G: Right. Yeshwanth Reddy Yerraguntla: escalation engine knowledge update notification service. Okay. Alert is same notification cycle. Vara Kumar Jagarapu: Sending Yeshwanth Reddy Yerraguntla: But from the perspective of core agent Vara Kumar Jagarapu: Yeah. Yeshwanth Reddy Yerraguntla: escalation, which agent will trigger the notification user or UI agent because it is critical direct. Vara Kumar Jagarapu: Multiple things. Yeshwanth Reddy Yerraguntla: Oh no. I agree. Vara Kumar Jagarapu: Uh Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: Okay. One thing missing is Vara Kumar Jagarapu: last user aware. 00:35:02 Yeshwanth Reddy Yerraguntla: sorry. Vara Kumar Jagarapu: So what it knows compared to what isn't user roles information accessible places how diff Yeshwanth Reddy Yerraguntla: This is Mhm. separate. So this is only taking care of what is new information. How to update my existing knowledge bases. Training lessons organization snapshot probably user preferences. This on the other hand is it's it's taking newspaper. If the newspaper has five pages with 20 articles, it will decide uh for the organization of 100 employees. Each employee which of those 20 will read. So one employee might read only Vara Kumar Jagarapu: Uh perspective notific Yeshwanth Reddy Yerraguntla: five. Vara Kumar Jagarapu: 10. Yeshwanth Reddy Yerraguntla: This is missing the question of who to whom it should send right. Vara Kumar Jagarapu: Yes. Yeshwanth Reddy Yerraguntla: Um yeah technically critical messages this will go away. Rajashekar G: Critical message is nothing but Yeshwanth Reddy Yerraguntla: Oh no. Critical is escalations Rajashekar G: escalations. Yeshwanth Reddy Yerraguntla: which means uh yeah insights and briefing critical messages go separate uh line right in saying that. 00:37:14 Rajashekar G: User aware insight and alert distribution engine directly triggering the notifications. How do you answer agent? Yeshwanth Reddy Yerraguntla: Yes. Rajashekar G: All right. Yeshwanth Reddy Yerraguntla: Critical messages. Whatever. This is still accurate. Vara Kumar Jagarapu: Yeah, the different channel is not anywhere related to user the website Yeshwanth Reddy Yerraguntla: Yes. Vara Kumar Jagarapu: right responsib Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: Yes. Yeshwanth Reddy Yerraguntla: Cancerologist. I'm not sure. Vara Kumar Jagarapu: Uh I mean n but Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: yeah Yeshwanth Reddy Yerraguntla: Hey, the Vara Kumar Jagarapu: Uh how could you kind of Yeshwanth Reddy Yerraguntla: add. Vara Kumar Jagarapu: sled Exactly. Yeshwanth Reddy Yerraguntla: Yeah. Come on. Vara Kumar Jagarapu: The responsibility only is to communicate with the databases and get something and pushing information. over there. Yeshwanth Reddy Yerraguntla: Oh. Vara Kumar Jagarapu: Uh communication user problem. Yeshwanth Reddy Yerraguntla: Which one is more easy? The reason I wanted to have this is to distribute the news. 00:39:52 Vara Kumar Jagarapu: Nothing. Yeshwanth Reddy Yerraguntla: Yes. Okay. Vara Kumar Jagarapu: Uh responsibilities allowed. Yeshwanth Reddy Yerraguntla: Mhm. Yeah. Vara Kumar Jagarapu: Alert is into training into refresh and Yeshwanth Reddy Yerraguntla: Okay. Vara Kumar Jagarapu: responsibilation. it Yeshwanth Reddy Yerraguntla: Got it. Vara Kumar Jagarapu: will. Yeshwanth Reddy Yerraguntla: I'll let you know. Vara Kumar Jagarapu: Okay. Yeah, maybe. Yeah. That is fine. Yeshwanth Reddy Yerraguntla: So you can answer where to send alert to. Vara Kumar Jagarapu: Uh for Yeshwanth Reddy Yerraguntla: Let's confirm. Yeah. Vara Kumar Jagarapu: example, Yeshwanth Reddy Yerraguntla: Next escalation rules updation where to send alert to user. Vara Kumar Jagarapu: This is endless matches. Yeshwanth Reddy Yerraguntla: Okay, escalation rules updation uh will be handled by uh real time intelligence Vara Kumar Jagarapu: Uh Yeshwanth Reddy Yerraguntla: agent. Oh wait. Vara Kumar Jagarapu: okay. Yeshwanth Reddy Yerraguntla: Escalation rules Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: updation Vara Kumar Jagarapu: Uh data sources. Yeshwanth Reddy Yerraguntla: data source escalation rules 10. Vara Kumar Jagarapu: Okay. Rajashekar G: How configurable? 00:43:00 Yeshwanth Reddy Yerraguntla: H Rajashekar G: Configurable. Yeshwanth Reddy Yerraguntla: tomorrow I want to change concept. So I want to change world model everything I want to change right. So it is better to put all of them in the database. Rajashekar G: It's good. Yeshwanth Reddy Yerraguntla: come. All right. Vara Kumar Jagarapu: Okay. Related to data agent. es Yeshwanth Reddy Yerraguntla: into the Vara Kumar Jagarapu: types of information data isn't we'll be returning kind of information. Yeshwanth Reddy Yerraguntla: so Vara Kumar Jagarapu: Um Yeshwanth Reddy Yerraguntla: but When it gets information from multiple data agents, single coherent story, Vara Kumar Jagarapu: Uh okay. For example, Yeshwanth Reddy Yerraguntla: right? Vara Kumar Jagarapu: okay. Yeshwanth Reddy Yerraguntla: Bug fix two or two different sources Vara Kumar Jagarapu: Done. Yeshwanth Reddy Yerraguntla: customer. It is being handled by Rajer. Vara Kumar Jagarapu: Okay. Two things. First of all, Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: right Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: data source or independent dat First of all, something 00:45:55 Yeshwanth Reddy Yerraguntla: First email will be customer is angry after four after 4 hours because Jira gets updated. You are writing a follow-up email saying for this customer this bug got Vara Kumar Jagarapu: H. Yeah. Yeshwanth Reddy Yerraguntla: raised. Vara Kumar Jagarapu: As these are critical immediate ref. Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: Yeah. Yeshwanth Reddy Yerraguntla: Yeah. Yeah. Different. I Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: agree. Vara Kumar Jagarapu: So, Yeshwanth Reddy Yerraguntla: training data and training lessons. Vara Kumar Jagarapu: Sorry. Yeshwanth Reddy Yerraguntla: Huh? How to how to change or modify them data source tool? when user is talking about updating certain uh information, Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: it has to go to that um it has to go to that DB location, read that item um read JSA based on the training lesson it is updating that item and putting back in database. Vara Kumar Jagarapu: Uh with the version increment or something Yeshwanth Reddy Yerraguntla: Correct? Yeah. So all of these can change because end of the day all of these are text 00:47:16 Vara Kumar Jagarapu: okay Yeshwanth Reddy Yerraguntla: files. So Vara Kumar Jagarapu: existing data add information that will be sitting into the Yeshwanth Reddy Yerraguntla: correct. Vara Kumar Jagarapu: same rag. Okay, clear Rajashekar G: Conception World model. Concept is nothing but the schema of the database. Vara Kumar Jagarapu: then. Yeshwanth Reddy Yerraguntla: Oh no. Rajashekar G: World model is the terminology used in that particular model. Yeshwanth Reddy Yerraguntla: Technical Rajashekar G: This world model field check. Yeshwanth Reddy Yerraguntla: business to some Rajashekar G: It's like LLM already knows kind of got Yeshwanth Reddy Yerraguntla: extent it will already know. Correct. Rajashekar G: it. Yeshwanth Reddy Yerraguntla: Yeah. Rajashekar G: One point escalation whenever happens Yeshwanth Reddy Yerraguntla: Uh, email refresh from those 20 emails. Maybe one of them is an escalation trigger. I put Oh, Rajashekar G: system refresh. Yeshwanth Reddy Yerraguntla: no. No. Yeah. Vara Kumar Jagarapu: I see. Rajashekar G: It's Yeshwanth Reddy Yerraguntla: Unless this happens, Rajashekar G: not Yeshwanth Reddy Yerraguntla: Unless this happens, you can't uh uh you can't real time do it. 00:48:49 Rajashekar G: Got it. Vara Kumar Jagarapu: glass. Yeshwanth Reddy Yerraguntla: Yeah. Coming back. Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: Multiple trainers updating the runbooks. Vara Kumar Jagarapu: Multiple Yeshwanth Reddy Yerraguntla: Okay, got it. Vara Kumar Jagarapu: But cascading Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: trainer on top of it user is contradicting with his own rules. Yeshwanth Reddy Yerraguntla: So behavior ideally our trainer should be aligned if there are contradictions because it's a trainer mode. Um the UI can show those contradictions and make let Vara Kumar Jagarapu: Um, Yeshwanth Reddy Yerraguntla: the um show those contradictions if overrides can be done by higher people in the organization. Vara Kumar Jagarapu: trainer For example, always the trainer information will be ready. Yeshwanth Reddy Yerraguntla: Are the user preference? Vara Kumar Jagarapu: Okay. User preference will be Yeshwanth Reddy Yerraguntla: Huh? Vara Kumar Jagarapu: more. Yeshwanth Reddy Yerraguntla: Yeah. Yeah. Correct. Vara Kumar Jagarapu: Yeah. instructions user. So Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: call. Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: Okay. 00:51:11 Yeshwanth Reddy Yerraguntla: Second 2 minutes lost. Sorry, Vara Kumar Jagarapu: Oh, no problem. Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: sir. Whenever having multiple data associations, the related data should be stored in multiple DBs only. Multiple DBs on multiple huh multiple DBs are Rajashekar G: multiple DBs correct or single DB with multiple tables Yeshwanth Reddy Yerraguntla: multiple DBs are correct. Rajashekar G: correct. Okay. Yeshwanth Reddy Yerraguntla: data source it should be its own uh DB I mean uh tomorrow if someone says I don't want to use Salesforce agent I don't know how it should be gracefully switched off. So scaling key I feel multiple DS is Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: correct. Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: Next training and learning life cycle. Rajashekar G: So Salesforce or insurance we are not duplicating any Yeshwanth Reddy Yerraguntla: Correct. We will not duplicate any Rajashekar G: data you're directly quering on the Yeshwanth Reddy Yerraguntla: data. Rajashekar G: sales salesforce or insurance databases. Yeshwanth Reddy Yerraguntla: Correct. Rajashekar G: So databases Yeshwanth Reddy Yerraguntla: you are talking about the green part but we will need uh at 00:54:24 Rajashekar G: knowledge. Okay. Yeshwanth Reddy Yerraguntla: least training lessons see I'm not saying Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: this is a rag db this is rag this is a hybrid DB with rag rag is one part which is necessary Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: for training lessons and all those things but Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: There are too many things to handle. So every connector will have a database whatever dedicated location. Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: Oh, Rajashekar G: opt Yeshwanth Reddy Yerraguntla: that was a bad pattern. That was a bad pattern. Rajashekar G: for we will be editing and maintaining versions Yeshwanth Reddy Yerraguntla: Correct. Correct. Rajashekar G: of the JSON. Yeshwanth Reddy Yerraguntla: Correct. Rajashekar G: Okay. Okay. But database let's say too many characters Yeshwanth Reddy Yerraguntla: database too many characters. Uh you are saying this the MD files will be large to Rajashekar G: I mean large text Yeshwanth Reddy Yerraguntla: know right posgress Rajashekar G: large or we'll go with some other data Yeshwanth Reddy Yerraguntla: can do everything. 00:56:12 Yeshwanth Reddy Yerraguntla: Yeah. Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: Postgress. So many things people have done with Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: Postgress. Rajashekar G: Okay. Vara Kumar Jagarapu: Okay. Data source. Okay. point of catch like sometime that will be there or it can be Yeshwanth Reddy Yerraguntla: Okay, time to leave Vara Kumar Jagarapu: cleared Yeshwanth Reddy Yerraguntla: on Vara Kumar Jagarapu: how it is different from the kind of training Yeshwanth Reddy Yerraguntla: in memory. Am Vara Kumar Jagarapu: uh in memory catch present. Yeshwanth Reddy Yerraguntla: I? Vara Kumar Jagarapu: Okay. Okay. But that is storing in the database. Yeshwanth Reddy Yerraguntla: Yeah. Yeah, whether it is 20 days or 90 days or whatever business call ideally purpose when 10 people are asking the same question nine times out of 10 I should not recmp compute Vara Kumar Jagarapu: and information. Yeshwanth Reddy Yerraguntla: What I'm trying to say is exactly yes source. So you will always get fresh data. Vara Kumar Jagarapu: Okay. 00:58:17 Vara Kumar Jagarapu: Visual Yeshwanth Reddy Yerraguntla: Yeah, Vara Kumar Jagarapu: actually Yeshwanth Reddy Yerraguntla: I can take an example. Um highest run score 016 IPL is the uh select I don't from Bman agal solar please ignore this year equal to 2016 uh I don't know the coal Vara Kumar Jagarapu: Oh, that's okay. That's Yeshwanth Reddy Yerraguntla: Right. Next when I ask uh orange cap into 017 ideally this you are storing it as highest transcorer for the year xi. Vara Kumar Jagarapu: Hey, Yeshwanth Reddy Yerraguntla: So Vara Kumar Jagarapu: hey, hey. Yeshwanth Reddy Yerraguntla: Q1 as answer one Vara Kumar Jagarapu: again. Yeshwanth Reddy Yerraguntla: A1 but next when I'm asking in 2024 ideally this and this are very similar questions right so LLM should figure out okay I already asked a similar question let me get that value this is the value in Vara Kumar Jagarapu: Boom. Yeshwanth Reddy Yerraguntla: 2024 I'll get back a skill and I'll give back the Vara Kumar Jagarapu: Uh yeah. Yeah. I'm not that much sure. 01:00:31 Yeshwanth Reddy Yerraguntla: Okay. So query first of all step one it will first understand its Vara Kumar Jagarapu: Uh Yeshwanth Reddy Yerraguntla: own snapshot world model concepts and generate a SQL query based on world knowledge. Step two, actually sorry. Step two, step zero. See if a similar question was asked in cash Vara Kumar Jagarapu: Ask me can catch you. Yeshwanth Reddy Yerraguntla: miss. Step two is going to be not storing this string. It will re it will have to convert the string into something generic. Vara Kumar Jagarapu: H what are the other Yeshwanth Reddy Yerraguntla: So step two it is deciding the key it is deciding the value and storing Vara Kumar Jagarapu: things? Yeshwanth Reddy Yerraguntla: them. Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: Step three give the answer evaluate and Vara Kumar Jagarapu: Yes. Yeshwanth Reddy Yerraguntla: give. Vara Kumar Jagarapu: Okay. Inserting flow when it is checking from the catch that knows some Yeshwanth Reddy Yerraguntla: Yes. Vara Kumar Jagarapu: value. Yeshwanth Reddy Yerraguntla: question. Vara Kumar Jagarapu: kind of example or similar thing. 01:02:13 Vara Kumar Jagarapu: So uh at Yeshwanth Reddy Yerraguntla: So it should ask. Vara Kumar Jagarapu: least Yeshwanth Reddy Yerraguntla: Sorry. Vara Kumar Jagarapu: whatever the value will be getting to know updated query. Exactly. slightly Yeshwanth Reddy Yerraguntla: Are they actually Vara Kumar Jagarapu: change Yeshwanth Reddy Yerraguntla: question? Sorry. Vara Kumar Jagarapu: question. Yeshwanth Reddy Yerraguntla: Yes. Correct. Perfect. Vara Kumar Jagarapu: You can take it as an example. Yeshwanth Reddy Yerraguntla: Correct. Correct. Correct. Correct. Yeah. Vara Kumar Jagarapu: So previous so you can take it like and you can query and you can prepare a new Yeshwanth Reddy Yerraguntla: Yeah, Vara Kumar Jagarapu: query. Yeshwanth Reddy Yerraguntla: 100%. So, example one. Example two can be more verbal. Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: Select batsman from this table with the so and so column Vara Kumar Jagarapu: Uh so Yeshwanth Reddy Yerraguntla: need for the LM to tomorrow. Vara Kumar Jagarapu: that It will return something meaningful Yeshwanth Reddy Yerraguntla: Correct. Actually render value can be selected so and so with a query 01:03:55 Vara Kumar Jagarapu: expectation. Yeshwanth Reddy Yerraguntla: example or 2016. This is what I did. Vara Kumar Jagarapu: Yeah. Yeshwanth Reddy Yerraguntla: Yeah. So it need not really worry about it can lm will know how to replace Vara Kumar Jagarapu: Uh then for now like you can go with this approach. If you are okay then later we can Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: inter Yeshwanth Reddy Yerraguntla: Okay. Okay. Actually receive training. Vara Kumar Jagarapu: Yeah. Yeshwanth Reddy Yerraguntla: Oh multiple just data sources. Vara Kumar Jagarapu: Nice. Yeshwanth Reddy Yerraguntla: This is what we were discussing. update QA if Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: applicable. Vara Kumar Jagarapu: Okay. Present P. Yeshwanth Reddy Yerraguntla: Okay. I didn't realize it was not P. Vara Kumar Jagarapu: Okay. And Yeshwanth Reddy Yerraguntla: Right. Now let's back to realtime agent with status on next similar query. Check similar confusion P. Okay. Vara Kumar Jagarapu: governance. Yeshwanth Reddy Yerraguntla: Uh governance and cash. Vara Kumar Jagarapu: It is kind of example. 01:06:08 Vara Kumar Jagarapu: No problem. Then it won't matter. Yeshwanth Reddy Yerraguntla: governance. Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: Right. Vara Kumar Jagarapu: Uh I Yeshwanth Reddy Yerraguntla: Danger. Rajashekar G: And I can see something now. Vara Kumar Jagarapu: could Yeshwanth Reddy Yerraguntla: Right. And what you're saying is that low-level person should not have even allowed to get have the answer. Rajashekar G: Access to the Yeshwanth Reddy Yerraguntla: Yeah. Rajashekar G: data. Yeshwanth Reddy Yerraguntla: Finance question. Vara Kumar Jagarapu: All Yeshwanth Reddy Yerraguntla: What is the budget size of Vara Kumar Jagarapu: right. Yeshwanth Reddy Yerraguntla: Taty? Rajashekar G: Hey Then the Yeshwanth Reddy Yerraguntla: Um Rajashekar G: cash Yeshwanth Reddy Yerraguntla: yeah. Vara Kumar Jagarapu: DB Rajashekar G: point. Vara Kumar Jagarapu: level Yeshwanth Reddy Yerraguntla: Second, I want to understand Vara Kumar Jagarapu: Python database. kind of grapper or something. What it Yeshwanth Reddy Yerraguntla: Ideally empty Vara Kumar Jagarapu: access? Yeshwanth Reddy Yerraguntla: that is true. Um likemail Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: when we are storing uh almost uh for every email we are 01:08:27 Vara Kumar Jagarapu: Jason Yeshwanth Reddy Yerraguntla: storing fresh embedding or rather Vara Kumar Jagarapu: H. Yeshwanth Reddy Yerraguntla: embedding we are storing to email and from emails. So people Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: members access control. Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: Exactly. Vara Kumar Jagarapu: Forward Yeshwanth Reddy Yerraguntla: V Salce. Vara Kumar Jagarapu: table, columns, connections. Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: We are not sure. Now the chalit Yeshwanth Reddy Yerraguntla: Yeah. uh that too when we don't have control on the data. Vara Kumar Jagarapu: Maybe Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: should I Yeshwanth Reddy Yerraguntla: When user is asking they will happen mainly during ad hoc this thing but it will Vara Kumar Jagarapu: leave? Yeshwanth Reddy Yerraguntla: also is involved important in user aware agent both the cases slow uh when it is trying to figure out an answer uh guardils like we never discussed how the guardrails are going to Ideally for every uh question that user is asking based on who is asking and arbback and guardrails either it should immediately send back saying I can't answer that or uh it should continue with the 01:10:31 Vara Kumar Jagarapu: H. Yeshwanth Reddy Yerraguntla: normal so that is something yeah even I don't uh I don't Vara Kumar Jagarapu: Um, Yeshwanth Reddy Yerraguntla: a point. Vara Kumar Jagarapu: and Yeshwanth Reddy Yerraguntla: Yeah. We have to discuss. Sorry, let me think this through. Vara Kumar Jagarapu: Data sources. data sources. Uh then problem kind of okay multiple tables same related Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: kind of information. Yeah. Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: information. But Yeshwanth Reddy Yerraguntla: as much as possible. Vara Kumar Jagarapu: yeah, Yeshwanth Reddy Yerraguntla: Maximum some things which are costly to run or frequently run that will make life easy especially for heavy Vara Kumar Jagarapu: okay. Yeah. Okay. Independent. Yeah. Yeah. Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: Okay. Surrender. Yeah. Yeshwanth Reddy Yerraguntla: Uh yeah. Yeah. What else? Vara Kumar Jagarapu: Awesome. Last The 01:13:51 Yeshwanth Reddy Yerraguntla: The data source agent system Vara Kumar Jagarapu: book Yeshwanth Reddy Yerraguntla: launch content behavior when data source agent is launching. It is launching with these things on now. Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: I mean snapshot. Vara Kumar Jagarapu: Real time agent on boot like it should Yeshwanth Reddy Yerraguntla: Yeah, it should do those things. Yeah. Vara Kumar Jagarapu: launch Yeshwanth Reddy Yerraguntla: Yeah. Real time agent. Vara Kumar Jagarapu: information or Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: something. Yeshwanth Reddy Yerraguntla: Correct. I will write it here. World model concepts. Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: I think whenever there is an LLM. Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: Yeah. Rack DV model concepts. Vara Kumar Jagarapu: Okay. It's an actual organic. Yeshwanth Reddy Yerraguntla: Yeah. Validate schema integrity. Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: Attach context to every skill execution on reload request version context. Fall back to last table context if validation fails. Uh the any point in the agent behavior life cycle. 01:15:47 Yeshwanth Reddy Yerraguntla: Okay. Basic question answering the refresh life cycle life cycle training and learning refresh insights. Rajashekar G: Agent Cor. Yeshwanth Reddy Yerraguntla: H Ad question Vara Kumar Jagarapu: How's that? Manisha Gundapuneedi: for Yeshwanth Reddy Yerraguntla: request to revalidate hot I don't think this static Vara Kumar Jagarapu: I think I Yeshwanth Reddy Yerraguntla: content reload nothing specific Manisha Gundapuneedi: speech. Vara Kumar Jagarapu: the Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: Uh Yeshwanth Reddy Yerraguntla: Sure. Sure. Sure. Vara Kumar Jagarapu: chapter. Yeshwanth Reddy Yerraguntla: Not easy. Rajashekar G: Okay. Color. Yeshwanth Reddy Yerraguntla: Okay. Rajashekar G: Okay. Vara Kumar Jagarapu: Yeah. Then query action. Yeshwanth Reddy Yerraguntla: junior. Vara Kumar Jagarapu: people. People Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: believe Yeshwanth Reddy Yerraguntla: link. Basically, it suggested three different tracks. Every track should be parallel and every track should have a deadline for a week. Basically track A is front end, track B is core, track C is data agents and reason basically track one uh react project scaffold copilot kit integration socket streaming architecture. 01:18:15 Yeshwanth Reddy Yerraguntla: One person will take care of a flow. One person will take care of chat components. One person will take care of login screen but I felt it was okay. Vara Kumar Jagarapu: Yeah, just so Yeshwanth Reddy Yerraguntla: solve it uh with a private tool. Vara Kumar Jagarapu: Mhm. Nothing. Yeshwanth Reddy Yerraguntla: Uh but yeah link public anybody can come here and basically this thing can execute code and uh uh do chatting with a same time. Vara Kumar Jagarapu: D. Okay. Yeshwanth Reddy Yerraguntla: is okay. I think can Rajashekar G: I hope Yeshwanth Reddy Yerraguntla: change. Rajashekar G: you Vara Kumar Jagarapu: Nice. Rajashekar G: It has given the But Yeshwanth Reddy Yerraguntla: H Rajashekar G: working. Yeshwanth Reddy Yerraguntla: we are actually nu how to do all these things. Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: What I will instead recommend is u have a single uh parent class that can do all these things in one go. So the moment you initialize uh an agent configuration token set whatever and if I chat with it, it should have the ability to update its own concepts. 01:20:56 Rajashekar G: Right. Yeshwanth Reddy Yerraguntla: I think uh everyone else can take advantage of them. Rajashekar G: Right. Yeshwanth Reddy Yerraguntla: Definition people can handle them. Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: Um I want to touch them and see how are we doing the right things or not ejgress. Rajashekar G: Hi, we means like a column is a better Yeshwanth Reddy Yerraguntla: What I suggest is uh uh we'll sit on that architecture sorry columns tables Rajashekar G: Sure. Yeshwanth Reddy Yerraguntla: Uh yes I we discuss chess Anthony h I don't I I feel we can do it very quickly track on the other hand Rajashekar G: Connector Oracle Unifier. Yeshwanth Reddy Yerraguntla: yeah modify Just in there Rajashekar G: Salesforce track C. Yeshwanth Reddy Yerraguntla: taxi. It couldn't. Rajashekar G: Oh, Yeshwanth Reddy Yerraguntla: Okay. Vara Kumar Jagarapu: Goodbye. Rajashekar G: heat. Yeshwanth Reddy Yerraguntla: Choose another Rajashekar G: Just Yeshwanth Reddy Yerraguntla: way. Rajashekar G: try Vara Kumar Jagarapu: It's good. Yeshwanth Reddy Yerraguntla: Thank you. Boundary, sir. track. Rajashekar G: Oh no no no Second week. 01:25:22 Yeshwanth Reddy Yerraguntla: Yeah. Refresh mechanism. Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: communication on today's law I will have more clarity Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: um real time sorry user aware agent um I think you can figure it out. Tasks. Vara Kumar Jagarapu: Uh actually task databases set up tables and mock Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: data on top of it. operations rev. Yeshwanth Reddy Yerraguntla: Got it. Yeah, they Rajashekar G: And second Yeshwanth Reddy Yerraguntla: pro Vara Kumar Jagarapu: Another Rajashekar G: code Vara Kumar Jagarapu: speech. Yeshwanth Reddy Yerraguntla: Yeah. Rajashekar G: which code needs to Basis flow. Yeshwanth Reddy Yerraguntla: True. So text system. Rajashekar G: Oh Yeshwanth Reddy Yerraguntla: Okay, it's a it's a different Rajashekar G: no. Yeshwanth Reddy Yerraguntla: table instructions table uh trading lessons single table that table will have Um query plan query embedding the hard Rajashekar G: is Yeshwanth Reddy Yerraguntla: resources is also uh embedding database. So it tables each is one different table. 01:28:57 Rajashekar G: rack. Cash it in. Yeshwanth Reddy Yerraguntla: Yeah. Query plan query embedding page doc Rajashekar G: Which embeddings? Yeshwanth Reddy Yerraguntla: ID Rajashekar G: Let's say Gmail. Yeshwanth Reddy Yerraguntla: Custom indexes index you will Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: define per data source schema Gmail Um, email, email ID, Rajashekar G: link. Yeshwanth Reddy Yerraguntla: email URL, uh, to address from addresses, Rajashekar G: Yeah, Yeshwanth Reddy Yerraguntla: uh, email embedding sentiment Rajashekar G: right. Yeshwanth Reddy Yerraguntla: calling data source. Rajashekar G: Oh no. Yeshwanth Reddy Yerraguntla: They had a 2000 page PDF most of the time. Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: So data 10,000 chunks Rajashekar G: Oh no resources Yeshwanth Reddy Yerraguntla: static Rajashekar G: whatever static like Gmail Yeshwanth Reddy Yerraguntla: resources Rajashekar G: data we are pulling and saving in our database. Yeshwanth Reddy Yerraguntla: Mhm. Rajashekar G: Gmail. Gmail. Yeshwanth Reddy Yerraguntla: This is beyond the Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: data. Rajashekar G: It's like schema or something. Okay. example let's say Gmail Gmail Salesforce Yeshwanth Reddy Yerraguntla: Salesforce Salesforce optional they are very very dependent on 01:31:51 Rajashekar G: table Yeshwanth Reddy Yerraguntla: Salesforce. What they did is for they created a Salesforce handbook for all their employees. Rajashekar G: H Yeshwanth Reddy Yerraguntla: Nobody has the time to teach you all the tables. So they'll give you a 600page PDF or 60 page PDF. Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: If the instructions are so detailed, Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: you can't put it in concepts textile or model because it's too big. Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: So when you have a question and that question needs some referencing it will fetch from metadata resources. Oh okay. So it the based on the question I need to go to that table and fetch that column. Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: In IRM case you can think of this as the whole database schema or for every data for every table in the database what is the table meaning if it is too Rajashekar G: schema is something concepts if it is Yeshwanth Reddy Yerraguntla: big to know if there are so many schemas then you Rajashekar G: too big. 01:33:13 Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: will have a high level understanding of what it is followed by detailed understanding in metadata resources. Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: Yeah. Uh custom indexes cash query cash. Rajashekar G: Hi sir. Yeshwanth Reddy Yerraguntla: Fine now. Satyasri Prabhakar Mantripragada: Hi, good morning. Good evening. Rajashekar G: Good morning. Yeshwanth Reddy Yerraguntla: Good morning. Okay. 60% the question. Satyasri Prabhakar Mantripragada: Good. Can we start executing the plan? Yeshwanth Reddy Yerraguntla: We still have some open questions for Gopal sir and even on me there are couple of items where I don't have clarity. Um other than that uh lot of items I think we can give to the uh juniors and start working. Satyasri Prabhakar Mantripragada: Mhm. Everything that we do, we should have an a goal to be accomplished, a business functionality to be accomplished. Done around yesterday. Uh we should be able to close them. We can always come back to the goal of the previously completed feature to enhance 01:34:55 Yeshwanth Reddy Yerraguntla: Yeah. Satyasri Prabhakar Mantripragada: it. Yeshwanth Reddy Yerraguntla: Acceptance criteria. Yeah. Yeah. Satyasri Prabhakar Mantripragada: Yes. Yeshwanth Reddy Yerraguntla: That is we following that. Satyasri Prabhakar Mantripragada: And bro or some client ask I should be able to convince them that okay this scope of this functionality is done. The scope is in the future. Yeshwanth Reddy Yerraguntla: Got it. Satyasri Prabhakar Mantripragada: We invest. Yeshwanth Reddy Yerraguntla: Yeah. Rajashekar G: Okay. Like the main rule Yeshwanth Reddy Yerraguntla: Sorry. Rajashekar G: is every story needs to have single owner and also every story shouldn't exit 40 hours and every task and everything should have some outcome. Yeshwanth Reddy Yerraguntla: What else are justice with so many constraints? Come back to solve it and start cleaning it up. Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: Um Rajashekar G: Can you solve it? Yeshwanth Reddy Yerraguntla: Sol Rajashekar G: else Yeshwanth Reddy Yerraguntla: this environment is attached to enterprise brain what is my Rajashekar G: want Yeshwanth Reddy Yerraguntla: project I mean solve it by name design it will not know what is happening below it's always what is above the this thing and it it already knows I'm working with enterprise 01:37:05 Rajashekar G: sheet. point. Yeshwanth Reddy Yerraguntla: sheet Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: maybe some modifications I haven't put but um yeah Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: Okay. Vara Kumar Jagarapu: run. Yeshwanth Reddy Yerraguntla: You're right. They have to be outside. Rajashekar G: Oh, Vara Kumar Jagarapu: Hey Yeshwanth Reddy Yerraguntla: Okay. Tools books should be outside. Tools. Tool sets. So tools are like functions. Tool sets are collection of functions on the difference. And sometimes you if you have a tool set like update uh a query cache a read query cache this they can be reused across connectors. So what tool sets uh what else books resources system prompt sorry user. Vara Kumar Jagarapu: Um, Yeshwanth Reddy Yerraguntla: I'm sorry. Vara Kumar Jagarapu: press it. Press it. I'm sorry. Yeshwanth Reddy Yerraguntla: Yeah. I don't know visualization intelligence even though I created a table here. Rajashekar G: So we are having all these points in the database concepts world model battles 01:39:37 Yeshwanth Reddy Yerraguntla: Yeah, Rajashekar G: everything. Yeshwanth Reddy Yerraguntla: correct. Perent Rajashekar G: So when upper agent per agent every database having all these things. So we asking a Yeshwanth Reddy Yerraguntla: right. Rajashekar G: question we are directly attaching the question and sending as an input to the LLM Yeshwanth Reddy Yerraguntla: Got it. Rajashekar G: but we have to our agent have to run those queries and get those all information and then also put that question as in like uh it is passing as a system prompt to the LLM. Yeshwanth Reddy Yerraguntla: See if I ask a question and every time it has to fetch from t database it's going to be very slow. Now if I for every question that I'm asking if Rajashekar G: It can be. Yeshwanth Reddy Yerraguntla: it has to make a round trip to the database to just to get system instructions it will be very slow Rajashekar G: Oh no. Yeshwanth Reddy Yerraguntla: on when I use that word on boot right control on boot that is what I meant. So yeah when the when the Python class gets initialized 01:40:57 Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: then the interesting question will be if something gets updated world Rajashekar G: Right. Yeshwanth Reddy Yerraguntla: model data in the schema data whatever next Rajashekar G: That Yeshwanth Reddy Yerraguntla: time when it loads it should take up Rajashekar G: needs Yeshwanth Reddy Yerraguntla: but we can try something that you last updated. Rajashekar G: good. Yeshwanth Reddy Yerraguntla: All I'm saying is if it knows uh at the time of making a query that the table has not been updated, it'll continue with with its own instructions. Radishant just an example. Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: So radish case radish c is doing one thing which is whenever someone is updating any of these things any of these things any of these things someone will tell radius okay for this agent these things got updated updu when your agent is Rajashekar G: Right. Yeshwanth Reddy Yerraguntla: making a query it is about to uh launch the llm just before that it might check radius latest it will not do anything latest it might update it system instructions and then send to the LL that's a designation we can always make 01:42:33 Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: situation I think that's fine Yeah, Rajashekar G: Yeah. Yeshwanth Reddy Yerraguntla: but the main purpose of this one by is that single class should uh do all of these things in one go. Rajashekar G: You're right. Yeshwanth Reddy Yerraguntla: So what that means is that class should also have how to update query cache how to update all those things everything we sort of do 50 40 to 50% of heavy lifting connections how to make each agent talk to another agent maybe 50% Rajashekar G: Right. Yeshwanth Reddy Yerraguntla: is overkill but at least 30%. So that team can take care of these things um schema and schema. Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: So there has to be one more like when agent gets initialized right. How to get initializerally whatever tokens. This Python class has to read this config file. Then it has to have uh initial tools and Rajashekar G: And Yeshwanth Reddy Yerraguntla: tool set definitions. Uh Rajashekar G: uh okay tool set definitions can Yeshwanth Reddy Yerraguntla: up 01:44:47 Vara Kumar Jagarapu: You Yeshwanth Reddy Yerraguntla: front. Rajashekar G: tools Python tool set definitions will be somewhere Vara Kumar Jagarapu: need Yeshwanth Reddy Yerraguntla: Yeah. Yeah. Yeah. Rajashekar G: else. Vara Kumar Jagarapu: it. Yeshwanth Reddy Yerraguntla: Next. User preferences. basic basic like run view I don't know history these are all I'm just common methods Rajashekar G: Yes. Yeshwanth Reddy Yerraguntla: a method value. Specialized agents, specialized functions, data agent from source method, read update, right? Okay. Rajashekar G: H Yeshwanth Reddy Yerraguntla: like this. This is now suddenly low level and feeling. If I start defining all these Rajashekar G: right clarity. Yeshwanth Reddy Yerraguntla: things right in I think one critical thing is initialize schema initialize Rajashekar G: Take a look at that. Yeshwanth Reddy Yerraguntla: database automatic Rajashekar G: All Yeshwanth Reddy Yerraguntla: So instead of someone going and creating postgress tables and uh columns I don't know is this a common thing that you know from code people will initialize all these things. 01:47:33 Rajashekar G: right. Vara Kumar Jagarapu: Generally they initialize database automatically we can access it right Yeshwanth Reddy Yerraguntla: Create in Vara Kumar Jagarapu: database initialization. Yeshwanth Reddy Yerraguntla: method. Vara Kumar Jagarapu: Okay. Okay. kind of create tables. Create Yeshwanth Reddy Yerraguntla: Uh yeah. Vara Kumar Jagarapu: tables. Yeshwanth Reddy Yerraguntla: So create all these tables. Vara Kumar Jagarapu: Get Yeshwanth Reddy Yerraguntla: Ah get Vara Kumar Jagarapu: this information. We have to create the table. Yeshwanth Reddy Yerraguntla: correct. So the moment your agent gets initialized in you are saving a lot of time. So I don't Vara Kumar Jagarapu: Sure. Yeshwanth Reddy Yerraguntla: know Rajashekar G: Sure Yeshwanth Reddy Yerraguntla: user data on the other hand preferences are back Rajashekar G: enough. Yeshwanth Reddy Yerraguntla: hierarchy I don't Again, these are just rough ideas. I'm like 80% confident we are covering. I'm 60% confident. 30% Rajashekar G: So for every data source or any agent class should have all Vara Kumar Jagarapu: Thanks. Rajashekar G: this right. 01:49:41 Yeshwanth Reddy Yerraguntla: H. Yeah, exactly. agent blueprint Python class abstract bl you can also do connect to UI or file log or initialize pilot so that you can do testing very quickly. Vara Kumar Jagarapu: Yeah. Then low level design Rajashekar G: Mhm. Vara Kumar Jagarapu: make sure like it is extendable. uh task or Rajashekar G: Sure. Vara Kumar Jagarapu: something. Yeshwanth Reddy Yerraguntla: schema. Easy. Vara Kumar Jagarapu: I think Rajashekar G: Once done like we will Vara Kumar Jagarapu: yeah, sorry. Rajashekar G: validate. Vara Kumar Jagarapu: bits and pieces. Rajashekar G: Uh right. Got it. Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: Main guy open questions. You can ask. Rajashekar G: What's up? Vara Kumar Jagarapu: Manish actually Yeshwanth Reddy Yerraguntla: Sorry. Vara Kumar Jagarapu: Keep together. Manisha Gundapuneedi: Play dranker. Yeshwanth Reddy Yerraguntla: Travel Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: center. Rajashekar G: Complete design. Satyasri Prabhakar Mantripragada: What do we mean design? What do you mean by design? Rajashekar G: So simulator Satyasri Prabhakar Mantripragada: Okay. 01:52:44 Rajashekar G: similar. So the need to get and then Yeshwanth Reddy Yerraguntla: All right. Rajashekar G: discuss how are they planning. Satyasri Prabhakar Mantripragada: What is Rajashekar G: Okay. Satyasri Prabhakar Mantripragada: the system should be able to learn the new framework Rajashekar G: Okay. Satyasri Prabhakar Mantripragada: if changes later it should be able to adapt quickly One. Rajashekar G: Figma frame Satyasri Prabhakar Mantripragada: Hello. Yeshwanth Reddy Yerraguntla: UI Rajashekar G: design. Yeshwanth Reddy Yerraguntla: and soific. Okay. Satyasri Prabhakar Mantripragada: for landing page for interaction sir. Rajashekar G: Not like Thank Yeshwanth Reddy Yerraguntla: There are four pages. Four pages. First super admin page where you have a configurations and other things. Rajashekar G: you. Yeshwanth Reddy Yerraguntla: Second login page. Third main page. Main page dashboard I mean third page fourth page. I'm not sure. Satyasri Prabhakar Mantripragada: Yeah. Can you send it to Yeshwanth Reddy Yerraguntla: Sorry Satyasri Prabhakar Mantripragada: me? Yeshwanth Reddy Yerraguntla: features. Satyasri Prabhakar Mantripragada: Okay. Rajashekar G: I features. Satyasri Prabhakar Mantripragada: What I was looking for is if they can give us a common template of design if not I'll have a common question all of us 01:55:13 Rajashekar G: Sure. And both works like better. Satyasri Prabhakar Mantripragada: Correct. Ganesh and Rahul dynamic simulation. Rajashekar G: Simulator. Yeah. Satyasri Prabhakar Mantripragada: What was that? Rajashekar G: Yeah. Satyasri Prabhakar Mantripragada: has also seen and he said it's Rajashekar G: Okay. Satyasri Prabhakar Mantripragada: okay. Rajashekar G: H. Satyasri Prabhakar Mantripragada: So that's where the country is already if you are able to do Rajashekar G: Oh. Yeshwanth Reddy Yerraguntla: Come Satyasri Prabhakar Mantripragada: everything. But I wanted to ensure that the moment comes back Rajashekar G: Okay. Satyasri Prabhakar Mantripragada: with hopefully one project at least we should have everything ready. Yeshwanth Reddy Yerraguntla: on. Satyasri Prabhakar Mantripragada: So within three weeks we have any get started on Rajashekar G: s***. Satyasri Prabhakar Mantripragada: our design. Rajashekar G: My voice last me voice and Satyasri Prabhakar Mantripragada: Hello. Rajashekar G: last. Can you repeat that statement Satyasri Prabhakar Mantripragada: Okay. Rajashekar G: again? Satyasri Prabhakar Mantripragada: Uh, Rajashekar G: Oh no. Oh. Satyasri Prabhakar Mantripragada: so if you can list down those For examp what I would suggest is a meeting and you and connect with Rajes and explain them How we plan to render the 01:58:08 Rajashekar G: Okay. Satyasri Prabhakar Mantripragada: UI? If you're interested, we'll also elaborate on the other aspects but I believe then they can also think of Rajashekar G: Okay. Satyasri Prabhakar Mantripragada: it and so if they wanted to play with they can play with Yeshwanth Reddy Yerraguntla: All right. Satyasri Prabhakar Mantripragada: But Rajashekar G: Okay. Okay. Satyasri Prabhakar Mantripragada: that's the second part that I will look at. Rajashekar G: Okay. Satyasri Prabhakar Mantripragada: Okay. Rajashekar G: Okay. 12 1210 12:30 12:31 and Satyasri Prabhakar Mantripragada: Okay. Rajashekar G: one more Satyasri Prabhakar Mantripragada: Okay. Rajashekar G: thing Satyasri Prabhakar Mantripragada: Okay. Huh. 40. Rajashekar G: $43 as of now. So it is and it continuously increases Satyasri Prabhakar Mantripragada: Okay. Rajashekar G: Max Yeshwanth Reddy Yerraguntla: Okay. Rajashekar G: $55. Satyasri Prabhakar Mantripragada: I would suggest Rajashekar G: Right. Right. Satyasri Prabhakar Mantripragada: were asking. So he needs to have an understanding on how the costies Rajashekar G: Okay. Satyasri Prabhakar Mantripragada: typical on an average inqu. So if we have the weekly breakdown, 02:00:40 Rajashekar G: Okay. Satyasri Prabhakar Mantripragada: let us give some weekly breakdown and the total as of now. Let us try to find Rajashekar G: Okay. Satyasri Prabhakar Mantripragada: out application. If we can segregate that will be great. Rajashekar G: I'm Yeshwanth Reddy Yerraguntla: application I will suggest at a user level also split Rajashekar G: application. Yeshwanth Reddy Yerraguntla: it and I don't think it's too much Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: effort Rajashekar G: Uh I know Yeshwanth Reddy Yerraguntla: Okay. Rajashekar G: we create groups. Enterprise Yeshwanth Reddy Yerraguntla: Okay. One second. Exactly. Rajashekar G: building Yeshwanth Reddy Yerraguntla: Yeah. Rajashekar G: environment and my Yeshwanth Reddy Yerraguntla: Okay. Rajashekar G: local Yeshwanth Reddy Yerraguntla: Oh no. Okay. Correct. Rajashekar G: user. Yeshwanth Reddy Yerraguntla: I know that. Rajashekar G: Okay. Oh no. Okay. Yeshwanth Reddy Yerraguntla: H1 devot. Rajashekar G: Okay everyone while working. Yeshwanth Reddy Yerraguntla: Yeah. Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: Okay. Satyasri Prabhakar Mantripragada: Yeah, fine. Uh whatever Yeshwanth Reddy Yerraguntla: My only concern is if it takes too much effort. 02:03:35 Satyasri Prabhakar Mantripragada: capability Yeshwanth Reddy Yerraguntla: Sorry. Satyasri Prabhakar Mantripragada: basic layer on top of it if they want something Yeshwanth Reddy Yerraguntla: Yeah. Satyasri Prabhakar Mantripragada: else then we'll see. Yeshwanth Reddy Yerraguntla: Yeah. Rajashekar G: Okay. concerned Yeshwanth Reddy Yerraguntla: Okay. Rajashekar G: max has happened Yeshwanth Reddy Yerraguntla: Okay. Rajashekar G: somewhere everyone. Yeshwanth Reddy Yerraguntla: Single person accountability. Rajashekar G: Oh no. Yeshwanth Reddy Yerraguntla: Uh I can come to this dashboard and see how much I am spending so that I can raise a request saying I use too Rajashekar G: Got Yeshwanth Reddy Yerraguntla: many tokens. Rajashekar G: it. Yeshwanth Reddy Yerraguntla: This is the right thing to do. Let's do this. Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: When you're sharing environment these things, don't share your Rajashekar G: Got it. Yeshwanth Reddy Yerraguntla: key. Rajashekar G: Okay. Vara Kumar Jagarapu: Minimum Yeshwanth Reddy Yerraguntla: Minimum Rajashekar G: Minimum maximum Vara Kumar Jagarapu: building Rajashekar G: budget. Yeshwanth Reddy Yerraguntla: $1. They will not accept billing in cents. Vara Kumar Jagarapu: for example $55 group how many people Rajashekar G: particular key Yeshwanth Reddy Yerraguntla: As many people are using those many people make you can continue to use 02:05:24 Vara Kumar Jagarapu: okay that is man What? Rajashekar G: max. Yeshwanth Reddy Yerraguntla: it. It will show in that same Vara Kumar Jagarapu: H. Yeshwanth Reddy Yerraguntla: row. Satyasri Prabhakar Mantripragada: uh what I was thinking is let us have one feature that we would have one admin interface for monitoring the cost and user access. Yeshwanth Reddy Yerraguntla: Adi Satyasri Prabhakar Mantripragada: So let us convert this into a feature deliverable. Yeshwanth Reddy Yerraguntla: in enterprise brand. Satyasri Prabhakar Mantripragada: So customers in enterprise brain we say we have an admin interface as we have been Yeshwanth Reddy Yerraguntla: Okay. Satyasri Prabhakar Mantripragada: monitoring offline like product saying that okay there is one feature for monitoring. Okay. Yeshwanth Reddy Yerraguntla: Yeah. Satyasri Prabhakar Mantripragada: As of now, we'll say we are able to capture at the application level user level monitoring of the cost will come in the future. Yeshwanth Reddy Yerraguntla: I don't know. I'm just writing it down. Satyasri Prabhakar Mantripragada: Uh-huh. Yeshwanth Reddy Yerraguntla: Yeah, Satyasri Prabhakar Mantripragada: If you're not here, please ask. I'll try Yeshwanth Reddy Yerraguntla: I'm following it. Actually, what you're suggesting is um we need to have our own light LLM interface inside the 02:06:49 Satyasri Prabhakar Mantripragada: to Yeshwanth Reddy Yerraguntla: one enterprise brain. So as super admin can provide more tokens to every user and uh the organization will have track of which user is using enterprise brain more and uh for what kind of questions. Satyasri Prabhakar Mantripragada: Correct. They may also be able to define the cap for every user Yeshwanth Reddy Yerraguntla: Yeah. Satyasri Prabhakar Mantripragada: sorry that we'll evalate group. Department Yeshwanth Reddy Yerraguntla: Got it. Yeah. Yeah. Satyasri Prabhakar Mantripragada: you'll consume it from group. We have to come up with those features. Yeshwanth Reddy Yerraguntla: Got it. Not Satyasri Prabhakar Mantripragada: So these will track our feature whatever is done so far will update the Yeshwanth Reddy Yerraguntla: it. Satyasri Prabhakar Mantripragada: task against that feature only. Yeshwanth Reddy Yerraguntla: Yeah. Satyasri Prabhakar Mantripragada: Let us efforts against the teachers not just Yeshwanth Reddy Yerraguntla: Yeah. Satyasri Prabhakar Mantripragada: only Yeshwanth Reddy Yerraguntla: Mhm. Is it Rajashekar G: And I'll be back in 15 minutes. Satyasri Prabhakar Mantripragada: I can't look at Yeshwanth Reddy Yerraguntla: I'm just noting down what you just said. 02:09:45 Yeshwanth Reddy Yerraguntla: We can always clean it up later. Satyasri Prabhakar Mantripragada: Yeah, back. Yeshwanth Reddy Yerraguntla: Where is heat? actually I'm thinking Vara Kumar Jagarapu: level. Maybe you are Yeshwanth Reddy Yerraguntla: much and call it Vara Kumar Jagarapu: connect Yeshwanth Reddy Yerraguntla: just curve. Satyasri Prabhakar Mantripragada: Sorry. Manisha Gundapuneedi: answer. Satyasri Prabhakar Mantripragada: Explain how we wanted to present the UI Manisha Gundapuneedi: Oh, Satyasri Prabhakar Mantripragada: here. Manisha Gundapuneedi: okay. Oh, Satyasri Prabhakar Mantripragada: Prime Manisha Gundapuneedi: focus. Satyasri Prabhakar Mantripragada: Time Gopal Gottumukkala: Hello. Vara Kumar Jagarapu: I Gopal Gottumukkala: Yeah. Satyasri Prabhakar Mantripragada: Good Vara Kumar Jagarapu: sat. Satyasri Prabhakar Mantripragada: morning. Yeshwanth Reddy Yerraguntla: s. Gopal Gottumukkala: Yeah. Yeah. Sure. Yeshwanth Reddy Yerraguntla: Okay. Um screen. Gopal Gottumukkala: Now we Yeshwanth Reddy Yerraguntla: Okay. Gopal Gottumukkala: can Yeshwanth Reddy Yerraguntla: So, couple of questions guidance architecture law. Um first is uh when we are dealing with uh Gopal Gottumukkala: check. Yeshwanth Reddy Yerraguntla: uh individual agents right for data sources the question is uh Gopal Gottumukkala: Yeah. Yeshwanth Reddy Yerraguntla: should we have a single database for every data source agent or every data source agent will have its own uh DB uh another question like how do we organize the information 02:13:55 Gopal Gottumukkala: Um, Yeshwanth Reddy Yerraguntla: graphus. Yeah. Gopal Gottumukkala: see if if we can go by the schema philosophy so that when the time comes it is easy to migrate. Yeshwanth Reddy Yerraguntla: Yeah. Gopal Gottumukkala: What I'm trying to say is anyway Same engine schema is different. Initially costs are less. So this is not enough. Yeshwanth Reddy Yerraguntla: H. Gopal Gottumukkala: So then that can be independently scaled and uh object isolation by default Yeshwanth Reddy Yerraguntla: Hat. Gopal Gottumukkala: we don't need to worry about you know refactoring tomorrow it will be a straightforward simple to autoscale I mean whatever we want to do we'll be able to do and we still retain that advancing database flexibility at the beginning. Yeah, I'm making sense. Yeshwanth Reddy Yerraguntla: Okay, Vara Kumar Jagarapu: Initial Yeshwanth Reddy Yerraguntla: if I understood it correctly, Vara Kumar Jagarapu: pressure Yeshwanth Reddy Yerraguntla: what you're saying is have a single connector, single resource I don't Vara Kumar Jagarapu: single single DB multiple Yeshwanth Reddy Yerraguntla: know. Vara Kumar Jagarapu: tables schemas are multiple initi Yeshwanth Reddy Yerraguntla: Oh, Gopal Gottumukkala: schemas multip 02:15:56 Satyasri Prabhakar Mantripragada: Come Yeshwanth Reddy Yerraguntla: sorry. Gopal Gottumukkala: connection. Vara Kumar Jagarapu: Can Satyasri Prabhakar Mantripragada: on. Gopal Gottumukkala: Different schema Vara Kumar Jagarapu: clear Yeshwanth Reddy Yerraguntla: Okay. So if I have to think of it, visualize it. Vara Kumar Jagarapu: specific counter? Yes. Yes. Yes. This and Yeshwanth Reddy Yerraguntla: Okay. Why? Because this is more cost effective on Got Gopal Gottumukkala: uh initial and yeah and later on you can actually Vara Kumar Jagarapu: initial Yeshwanth Reddy Yerraguntla: it. Gopal Gottumukkala: individually scale up and down of uh at an agent Yeshwanth Reddy Yerraguntla: Some will be heavy, some will be lightweight by nature. Gopal Gottumukkala: Yeah. Yeshwanth Reddy Yerraguntla: Oh no. Gopal Gottumukkala: So accordingly we will be able to scale up and Yeshwanth Reddy Yerraguntla: Got it. Gopal Gottumukkala: down. Vara Kumar Jagarapu: Clear. Yeshwanth Reddy Yerraguntla: How are we scaling up and down? Gopal Gottumukkala: Uh Yeshwanth Reddy Yerraguntla: Yeah. Yeah. Yeah. Gopal Gottumukkala: shore. Yeshwanth Reddy Yerraguntla: Oh no. Gopal Gottumukkala: So usual problems scaling issues. 02:18:06 Gopal Gottumukkala: Right. Yeshwanth Reddy Yerraguntla: Cut Gopal Gottumukkala: As long as you you keep these two things scalable on their Yeshwanth Reddy Yerraguntla: it. Gopal Gottumukkala: own. Uh agent A is and light DB. Yeshwanth Reddy Yerraguntla: H. Gopal Gottumukkala: VM light uh light. She could be heavy on Yeshwanth Reddy Yerraguntla: Yeah. Gopal Gottumukkala: both. So Yeshwanth Reddy Yerraguntla: Right. Gopal Gottumukkala: first Auto scaling service autocaling anyway it is just a configuration if my CPU reaches 80% for 2 minutes uh one more pod like Yeshwanth Reddy Yerraguntla: Yeah. Gopal Gottumukkala: that you go up to three and then stop there anytime it it falls below 60 kill that pod and then uh make sure only one part is available so similarly memory we can write different rules and then many other uh ways we can actually scale up and Same Yeshwanth Reddy Yerraguntla: Okay. Gopal Gottumukkala: story the database is you can configure database global or not global from a processing point of views what we Yeshwanth Reddy Yerraguntla: Okay. Gopal Gottumukkala: do Yeshwanth Reddy Yerraguntla: Okay. Gopal Gottumukkala: enable Yeshwanth Reddy Yerraguntla: Okay. Gopal Gottumukkala: Master. So as long as your agent and your database have a certain 02:20:24 Yeshwanth Reddy Yerraguntla: H. Gopal Gottumukkala: boundary, you can scale database independently. You scale your runtime independently. As long as you have this flexibility or you can safely say my app is autoscalable. It is up to us how do we orchestrate. Yeshwanth Reddy Yerraguntla: H.B. Gopal Gottumukkala: Now we just have choices of orchestration. Now what exact orchestration is required for what exact agent is our choice then key just to make sure that we have that flexibility but we don't want to put up independent database engines of agent at the beginning we are taking only one engine that means runtime is same but we put agent tables into Yeshwanth Reddy Yerraguntla: after. Gopal Gottumukkala: schema so agent A will have its own schema. B will have its own schema. Yeshwanth Reddy Yerraguntla: You got Gopal Gottumukkala: Uh but the runtime is same. Yeshwanth Reddy Yerraguntla: it. Gopal Gottumukkala: Ultimately if one of the agent is taking the hit, all the agents will take the hit. among A B C D E uh D is taking a hit up then what we'll do is D schema we will move it to another engine an independent engine again that we have to do 02:21:56 Yeshwanth Reddy Yerraguntla: Okay. Gopal Gottumukkala: manually because because we are going with the cost of Yeshwanth Reddy Yerraguntla: Question. Gopal Gottumukkala: in the mind but ideally the design should have been every agent should have its own Yeshwanth Reddy Yerraguntla: Okay. Gopal Gottumukkala: So that is a theoretical uh it's a theoretical good state but we don't want to have that Yeshwanth Reddy Yerraguntla: Okay. Gopal Gottumukkala: theoretical good state because of the cost and from an infra point Yeshwanth Reddy Yerraguntla: Schemas. Sorry. Gopal Gottumukkala: of yeah scheas are just put together into one engine Yeshwanth Reddy Yerraguntla: Yeah. Gopal Gottumukkala: and Yeshwanth Reddy Yerraguntla: Clarity of I can summarize. Schemas are mainly for logical separation while maintaining the simplicity of Gopal Gottumukkala: yeah exactly Yeshwanth Reddy Yerraguntla: database uh uh logistics. Gopal Gottumukkala: run time. Yeshwanth Reddy Yerraguntla: Yeah. While you want to scale, Gopal Gottumukkala: Yeah. Yeshwanth Reddy Yerraguntla: you have to manually pull the schema, put it in a different uh connector and scale it up. Gopal Gottumukkala: Yes. Ideally, Yeshwanth Reddy Yerraguntla: Okay. Gopal Gottumukkala: if as a as a DevOps engineer, if you give me a chance, I would never allow you to add multiple schemas into the same database unless and until all the schemas are related to the same application. 02:23:18 Gopal Gottumukkala: It has to be in the same schema Yeshwanth Reddy Yerraguntla: H. Gopal Gottumukkala: and I know you are going to come always at the peak of load and you don't have a choice. I don't have a choice. Right? That's the only glitch in this entire theory that we put in together. But that's a hit we are going to take by saving some money at the initial Yeshwanth Reddy Yerraguntla: Got Gopal Gottumukkala: stages. Yeshwanth Reddy Yerraguntla: it. Gopal Gottumukkala: Yeah. Anything else? Yeshwanth Reddy Yerraguntla: Second question. No. Um so uh I'll give you a hypothetical scenario that we have um we have created enterprise brain for Diwami. One of the connector is Salesforce which contains the um monitory information of Gopal Gottumukkala: Okay, Yeshwanth Reddy Yerraguntla: projects. Gopal Gottumukkala: please Yeshwanth Reddy Yerraguntla: money related information. Gopal Gottumukkala: Okay. Yeah, I Yeshwanth Reddy Yerraguntla: I want to have that info accessible for Navin or Pratma madam or leaders but Gopal Gottumukkala: understand. Yeshwanth Reddy Yerraguntla: not to juniors or anyone else. So we were able to handle this problem in Gmail where we were able to 02:24:54 Gopal Gottumukkala: Okay. Yeshwanth Reddy Yerraguntla: control the um things we were indexing right. It could um sorry if I actually come to this part email whenever I was storing those custom indexes I was storing from address to address based on which we had that role level access. Monaco based on which we are able to guarantee the uh whatever uh rback but in Salesforce we don't have that control Salesforce is a different uh external system so uh we are sort of confused on how to ensure that um bad Gopal Gottumukkala: Couple Yeshwanth Reddy Yerraguntla: actors cannot access or cannot make any request to the data source. Gopal Gottumukkala: of things are they should be able to see leads and all those things, right? Yeshwanth Reddy Yerraguntla: Yes. Gopal Gottumukkala: Only certain part of that information has to be suppressed, Yeshwanth Reddy Yerraguntla: Got Gopal Gottumukkala: right? Yeshwanth Reddy Yerraguntla: it. Gopal Gottumukkala: At an agent level it is pretty simple because we have uh which agents to invoke and not to invoke. That is pretty straightforward. Yeshwanth Reddy Yerraguntla: Got it. Gopal Gottumukkala: Next one is we have to use that facility but somehow we have to communicate to that agent saying that when such a person comes bring this out. 02:26:26 Yeshwanth Reddy Yerraguntla: Oh no. Gopal Gottumukkala: Is it an API call driven the communication to SDFC is Yeshwanth Reddy Yerraguntla: Correct. Currently it's API call. Gopal Gottumukkala: So the the I mean in my mind uh Ashwan whether it is an API database doesn't make any real difference for me except in the way that I access. What I'm trying to say is Yeshwanth Reddy Yerraguntla: Correct. Gopal Gottumukkala: uh Yeshwanth Reddy Yerraguntla: 100%. Gopal Gottumukkala: um sorry um in in both ways right it is a data model so what kind of request object I'm sending what kind of response object I am getting and where I am reaching so if I have to translate this rest philosophy into database which table and what is my filter condition what are my selects it is that simple of course once go Yeshwanth Reddy Yerraguntla: cut. Gopal Gottumukkala: in things will get tangled up you know you'll get lot of mess we need to clean up that is there in SQL as well as in rest it doesn't make much difference to me Yeshwanth Reddy Yerraguntla: Yeah. Right. Gopal Gottumukkala: right so it is still a data model so I have what is my er is there with me in the database as well as the rest 02:27:46 Yeshwanth Reddy Yerraguntla: Yeah. Gopal Gottumukkala: APIs. Again, I'm too simplifying it. But conceptually, that is how I think I always look at the system. It is still a data whether I'm getting the raw data then I'll go to the database. When I don't have raw data access, I'll still get the raw data. I'll assume that there is a raw data and I'll look for the schema. Whenever the people explain me the schema definition, I'll write my logic on top of it. Yeshwanth Reddy Yerraguntla: Oh Gopal Gottumukkala: pretty uh uh pretty similar in my mind. Yeshwanth Reddy Yerraguntla: no. Gopal Gottumukkala: If we assume that it doesn't matter whether it's a database connection or rest right that is taken care of. Now if if I am saying I know the DOTM data model I know what amount field is it could be M but I can identify what is an amount field right first level problem is trim off amount fields by Yeshwanth Reddy Yerraguntla: H. Gopal Gottumukkala: default don't bring amount fields unless and until I say so I Yeshwanth Reddy Yerraguntla: H. 02:28:58 Gopal Gottumukkala: say rest Yeshwanth Reddy Yerraguntla: Correct. Gopal Gottumukkala: only when it is uh don't trim off. Let the object be object otherwise trim off. simple if if the user has a certain role or by some condition don't bring in those two into the projections right select or selection memory one of Yeshwanth Reddy Yerraguntla: Yeah, Gopal Gottumukkala: the Yeshwanth Reddy Yerraguntla: either don't make the query or if when you get back uh remove it. Gopal Gottumukkala: yeah right in the DB in the DB case I have luxury of doing both in a rest call you only have one you you cannot decide what are you Yeshwanth Reddy Yerraguntla: Yeah. Gopal Gottumukkala: going to get because it's more or less fixed again SQL kind of operation we can do it in graphql but rest usually don't provide and I have seen people writing rest APIs in the way of graphql only those cases we can do but otherwise it is like you know you get it and then shut off what you don't want. Yeshwanth Reddy Yerraguntla: H. Gopal Gottumukkala: But Yeshwanth Reddy Yerraguntla: Yeah. Gopal Gottumukkala: control. 02:30:52 Gopal Gottumukkala: Reliable solution Yeshwanth Reddy Yerraguntla: Yeah. Yeah. Gopal Gottumukkala: relationship other side story doesn't make much difference for Yeshwanth Reddy Yerraguntla: Got it. Gopal Gottumukkala: us Yeshwanth Reddy Yerraguntla: Yeah. Gopal Gottumukkala: be it rest API be it graphql doesn't matter you're getting data you need to know the model otherwise I mean what I'm saying is data model and then diagram of that data model that's 80% of information for my Yeshwanth Reddy Yerraguntla: Correct. Gopal Gottumukkala: credit Yeshwanth Reddy Yerraguntla: Yeah, Gopal Gottumukkala: knowledge of the Yeshwanth Reddy Yerraguntla: true. Agreed. Anna, yeah, Gopal Gottumukkala: make it clear for Yeshwanth Reddy Yerraguntla: we will control these things. I wrote something as arbback controller, Gopal Gottumukkala: other Yeshwanth Reddy Yerraguntla: but you can suggest a better phrase. Gopal Gottumukkala: that is that's what it Then we will map it. That's what you guys did in Gmail case. Ideally, Gmail agent database. It's a hybrid database. Yeshwanth Reddy Yerraguntla: Got it. Gopal Gottumukkala: that is Gmail. Yeshwanth Reddy Yerraguntla: Yeah. Gopal Gottumukkala: But logically speaking, it is exactly the same problem there 02:33:02 Yeshwanth Reddy Yerraguntla: on. Gopal Gottumukkala: also. Yeshwanth Reddy Yerraguntla: At every data controller uh sorry data source agent we will have to have a complete uh universe of what I can request what I can expect from the data source and I have to have a mapping of which roles can have access to which uh columns or entities structured respon Gopal Gottumukkala: Yeah. Yeshwanth Reddy Yerraguntla: response then sanitize Gopal Gottumukkala: Okay. Yeshwanth Reddy Yerraguntla: chit I have compare it with my users and then filter out all those things which I don't need. Gopal Gottumukkala: Yeah. Yeshwanth Reddy Yerraguntla: That is the actually brute force solution where we are saying uh I can't control what I'm asking you. I will only control what I get back. Gopal Gottumukkala: Yeah. Yes. This is one. Yeah. Yeshwanth Reddy Yerraguntla: That is inefficient in its own way because we are making one round trip and wasting some uh Gopal Gottumukkala: On the second part. Yeshwanth Reddy Yerraguntla: data. Gopal Gottumukkala: Yes. It is inefficient but control that's what we we get. Yeshwanth Reddy Yerraguntla: Yeah. Uh to some extent that is what that is where our intelligence should show 02:34:19 Gopal Gottumukkala: Yes. Yeshwanth Reddy Yerraguntla: up. Gopal Gottumukkala: Yeah. If if I am asking only finance numbers then the query should not go. But if I asking something along with finance numbers then you still have to ask shut off the finance and give me the remaining piece. Yeshwanth Reddy Yerraguntla: Right. Gopal Gottumukkala: So query should not be fired is very contextual is what I'm trying to Yeshwanth Reddy Yerraguntla: Got it. Gopal Gottumukkala: say. Yeshwanth Reddy Yerraguntla: Got it. These were the two questions I had. Vara Kumar Jagarapu: Uh yeah, good. But everything we need to handle it very properly otherwise I feel like there is a lot of risks in the Yeshwanth Reddy Yerraguntla: LLM inherent I mean Vara Kumar Jagarapu: end. Yeshwanth Reddy Yerraguntla: if we are going out there and selling that we have something we have to show these guarantees otherwise there's no point in uh claiming we have something of value right so This is a in some terminology this is a P 0 only. We have to crack Vara Kumar Jagarapu: Yeah. Yeah. 02:35:55 Yeshwanth Reddy Yerraguntla: it. Vara Kumar Jagarapu: Yeah. Yeshwanth Reddy Yerraguntla: U everything else is clear sir. Vara Kumar Jagarapu: Thank you so much Gopal Gottumukkala: Okay. Yeshwanth Reddy Yerraguntla: coals are last point at some point we Vara Kumar Jagarapu: sir. Gopal Gottumukkala: Chip. Yeshwanth Reddy Yerraguntla: have to walk you through the low-level diagrams also right um like I don't want to take any major steps uh too late into the process so I just want to let you know um at least next week uh Monday uh what are the things we are Gopal Gottumukkala: Sure. Yeshwanth Reddy Yerraguntla: about to start ani uh I want to have that discussion with you sir Gopal Gottumukkala: Yes. Um I missed the part when when are you proposing when do we Yeshwanth Reddy Yerraguntla: next Gopal Gottumukkala: connect? Yeshwanth Reddy Yerraguntla: Monday Gopal Gottumukkala: Yeah. Um actually yeah go Yeshwanth Reddy Yerraguntla: two things Yeah. Yeah. Just two things. Second even bigger uh point I want to have Gopal Gottumukkala: ahead. Yeshwanth Reddy Yerraguntla: your comments on is are we following the right format? 02:37:38 Yeshwanth Reddy Yerraguntla: Are we following the right process is one more thing I want to um know from you because um next time whatever we are doing I want to correct them. Gopal Gottumukkala: Uh, sure. That's sure. Yeshwanth Reddy Yerraguntla: Yeah. Yeah. Gopal Gottumukkala: Yeah. Yeshwanth Reddy Yerraguntla: That's what I wanted to talk to you about. Sorry sir m Gopal Gottumukkala: Huh? Sure. Yeshwanth Reddy Yerraguntla: sorry sari I think we can we'll continue Gopal Gottumukkala: Okay. Yeshwanth Reddy Yerraguntla: here. Gopal Gottumukkala: Yeah. Yeshwanth Reddy Yerraguntla: Yeah. Yeah. Arback Gopal Gottumukkala: better. Yeshwanth Reddy Yerraguntla: components. Yeah, definitely. It's Um interesting uh thing. Gopal Gottumukkala: See though it feels like a hack for us and I mean database does it in both ways and when it has control it actually avoids pulling it but when it doesn't have control it actually take a hit of pulling it up and then cleaning it up. So the the call is a little dynamic. There is there are sophisticated algorithms but database engines use both the techniques. 02:39:47 Gopal Gottumukkala: It all depends on under what circumstances what makes more Yeshwanth Reddy Yerraguntla: H. Gopal Gottumukkala: uh either towards the speed or towards the acid acid properties. Retain princip both ways Yeshwanth Reddy Yerraguntla: Oh no. Oh no. Gopal Gottumukkala: request. Yeshwanth Reddy Yerraguntla: Got it. Gopal Gottumukkala: regular queries and then there are policies defined that this something that should not be there then you not have a choice I'm just trying to Yeshwanth Reddy Yerraguntla: Yeah. Gopal Gottumukkala: say that whatever we thought is not a hack it is it is a solution in a certain under Yeshwanth Reddy Yerraguntla: Correct. Gopal Gottumukkala: a certain context. Yeshwanth Reddy Yerraguntla: You can't avoid Gopal Gottumukkala: Yeah. Yeshwanth Reddy Yerraguntla: obviously control. They wouldn't have written their applications with our use cases in mind. Right. Gopal Gottumukkala: Yeah. Yeshwanth Reddy Yerraguntla: Obviously, how do we accomplish this concept? Vara Kumar Jagarapu: Whatever the Yeshwanth Reddy Yerraguntla: I understood what you what we should be doing Vara Kumar Jagarapu: tool Yeshwanth Reddy Yerraguntla: theoretical practical we have to solidify Gopal Gottumukkala: Okay. Pay me the last Tuesday then we'll get clapped here. 02:41:54 Gopal Gottumukkala: We just make an attempt Yeshwanth Reddy Yerraguntla: yeah Gopal Gottumukkala: somewhere. Yeshwanth Reddy Yerraguntla: one more uh I like I wrote it here I don't know if you have time. This this agent is going to broadcast news to everyone in the organization. It's almost like our agent because we are saying it's proactive certain things should be Gopal Gottumukkala: That's right. Yeah. Yeshwanth Reddy Yerraguntla: showing up on the on my dashboard by like automatically uh we have to ensure I I am not seeing financial info or things like that but the control we have is this organization snapshot is in our Gopal Gottumukkala: Yeah. Yeshwanth Reddy Yerraguntla: hands so we'll have more control in both directions. So this can be more uh Gopal Gottumukkala: Yeah, you're right. Yeah, it comes in multiple places. Let's figure out a good name. Yeshwanth Reddy Yerraguntla: yeah. Gopal Gottumukkala: People have a pre conceived understanding a hardback unnecessarily they take us into the wrong direction with wrong questions we'll figure out another another name for it but as Yeshwanth Reddy Yerraguntla: Yeah. Gopal Gottumukkala: of now it is a placeholder name for us so basically what we are trying to say just an extension of the same conception what we are saying is based on context and the user intent and everything that we know you will get exactly what you need to in that what you need to Security is also part of it. 02:43:31 Yeshwanth Reddy Yerraguntla: Yeah. Gopal Gottumukkala: As long as we can define that you will get what you need to it is already applied with securities what we are trying to say that Arabback is ensuring that right just know what you Yeshwanth Reddy Yerraguntla: Got it. Gopal Gottumukkala: are in other places it is a global call that you know based on a certain philosophy this should never come out there it is perfectly arbback but in an earlier scenario what you explained it it is not exactly arbback but Yeshwanth Reddy Yerraguntla: Yeah. Gopal Gottumukkala: it Little bit little bit contextual. When we are saying contextual still you don't get what you should not get. Yeshwanth Reddy Yerraguntla: Yeah. Gopal Gottumukkala: We'll figure out the name. Yeshwanth Reddy Yerraguntla: Least privilege authorization. Gopal Gottumukkala: Yeah. And Yeshwanth Reddy Yerraguntla: something. Gopal Gottumukkala: the Yeshwanth Reddy Yerraguntla: Oh, okay. Gopal Gottumukkala: So it all depends on how we defulit you can look at me then you can always look at me but they have to work on the opposite side that's like you know least privileged If I'm an office boy in any sense, I should be an office boy. 02:45:30 Yeshwanth Reddy Yerraguntla: Yeah. Gopal Gottumukkala: Even though somebody else is saying I am somebody like an architect, we should not treat him as an architect. It all depends on what kind of application and within the application where are we applying these rules. Yeah. the measurement and we'll put a note that this ARback controls this Yeshwanth Reddy Yerraguntla: Yeah. Gopal Gottumukkala: aspect that makes sense Yeshwanth Reddy Yerraguntla: March. Vara Kumar Jagarapu: Sorry. Yeah. Yeshwanth Reddy Yerraguntla: All right. Vara Kumar Jagarapu: Just Yeshwanth Reddy Yerraguntla: Right. Correct. You know, I have a feeling this is what should Vara Kumar Jagarapu: Yeah, Yeshwanth Reddy Yerraguntla: happen. Vara Kumar Jagarapu: but communications and also different questions. security. I need them in front of Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: you. Yeshwanth Reddy Yerraguntla: And see if the question is uh um is one agent doing too many things that is why it's might be better to have too many or multiple agents. One thing we can always control is when when you have an ad hoc query, 02:47:28 Vara Kumar Jagarapu: H. Yeshwanth Reddy Yerraguntla: you'll always have context of who is asking in what conversation ID or session ID they are asking how that that packet is always associated. So whenever uh um you make a query to your data source or uh question answering query that you'll get back the packet always saying I'm answering this query for the question you have asked which is having so and so Vara Kumar Jagarapu: H. Yeshwanth Reddy Yerraguntla: ID. So as long as you maintain that packet you you'll always know what kind of a packet it is and where to route it. So process flow control shadow with limited agents it's it's doable and what I'm trying to say is we can handle arbitrarily complex flows with few agents uh right so ad hoc flow training lessons flow broadcast Vara Kumar Jagarapu: Mhm. Yeshwanth Reddy Yerraguntla: is every time you maintain that uh metadata saying what is what is this uh where is it in the life cycle of information transfer. So we can always code it Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: saying so that should not be a problem only like still 02:49:11 Vara Kumar Jagarapu: Okay. Yeshwanth Reddy Yerraguntla: I'm not saying what your your idea is bad in any way because um yeah maybe like the only place where having uh say saying that these two are not sufficient, we need more is when the the number of responsibilities on these two agents is increasing. Vara Kumar Jagarapu: Yeah, Yeshwanth Reddy Yerraguntla: All right. Vara Kumar Jagarapu: maybe initially we can go with this two but later if we feel like adding more then we can Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: think of them. Yeah. I'm fine with Yeshwanth Reddy Yerraguntla: Yeah. Yeah. Yeah. Vara Kumar Jagarapu: that. Yeshwanth Reddy Yerraguntla: If we go with this kind of a class uh replicate shadow, merge shadow, duplicate shadow, whatever it is. So we'll not spend too much time writing code. Yeah. Rajada. Vara Kumar Jagarapu: Yeah, he's Rajashekar G: and Vara Kumar Jagarapu: here. Yeshwanth Reddy Yerraguntla: Yeah. Rajashekar G: out. Yeshwanth Reddy Yerraguntla: So the um I mean next action steps. Rajashekar G: Yeah. Yeshwanth Reddy Yerraguntla: Yeah, 02:50:34 Rajashekar G: De exper Vara Kumar Jagarapu: We are Yeshwanth Reddy Yerraguntla: correct. Rajashekar G: No, Vara Kumar Jagarapu: level. Yeshwanth Reddy Yerraguntla: Once you get these two Rajashekar G: right. Okay. Solve it low. Shall I take another instance and try or Yeshwanth Reddy Yerraguntla: Duplicate copy. Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: You can continue here itself. Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: Okay. Rajashekar G: Sure. Yeshwanth Reddy Yerraguntla: Yeah, if you want to uh like you can always uh access the whole uh dashboard. Rajashekar G: Yeah. Yeshwanth Reddy Yerraguntla: Yeah, you can always correct correct correct and Rajashekar G: Direct. Yeshwanth Reddy Yerraguntla: e folder whatever notebook you create uh that will always have the context of enterprise brain uh project. Yeah. Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: So they have this feature where if if this file is existing in the folder Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: whatever you want to converse you will converse I Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: will continue working on this guy. Rajashekar G: Orchestration Yeshwanth Reddy Yerraguntla: Uh h Rajashekar G: that is the orchestration article, Yeshwanth Reddy Yerraguntla: orchestration 02:52:28 Rajashekar G: right? Okay. Yeshwanth Reddy Yerraguntla: yeah goal yeah yeah I think all of us will drop off. Rajashekar G: Thank you sir. Vara Kumar Jagarapu: Thank you. Manisha Gundapuneedi: Practice Vara Kumar Jagarapu: Okay. Rajashekar G: Okay. Vara Kumar Jagarapu: Thank you. Afternoon. Maybe your call Manisha Gundapuneedi: Connect. Vara Kumar Jagarapu: just okay. Okay. Rajashekar G: point. Manisha Gundapuneedi: Same problem with Inhale. Rajashekar G: name Manisha Gundapuneedi: Oh. Rajashekar G: Okay. Back test. and Manisha Gundapuneedi: Thanks. Rajashekar G: carped. Satyasri Prabhakar Mantripragada: mainly and management is Rajashekar G: Okay. Satyasri Prabhakar Mantripragada: expecting that we are making progress on it. Rajashekar G: on this on this new Satyasri Prabhakar Mantripragada: So we should make progress Rajashekar G: version. Satyasri Prabhakar Mantripragada: the Rajashekar G: I mean, Satyasri Prabhakar Mantripragada: Oracle unifi is one implementation. Rajashekar G: one Satyasri Prabhakar Mantripragada: Uh Rajashekar G: implementation Satyasri Prabhakar Mantripragada: next uh three phases. Three phases. Enterprise interface design Rajashekar G: Yeah. Satyasri Prabhakar Mantripragada: system. Uh next thing uh Kaggle data 02:55:17 Rajashekar G: Oh no. Satyasri Prabhakar Mantripragada: manufacturing enterprise brain for manufacturing. Rajashekar G: M Oh Satyasri Prabhakar Mantripragada: So third one is unifier Rajashekar G: no. Satyasri Prabhakar Mantripragada: integration. Got Rajashekar G: So, enterprise brain and enterprise brain for manufacturing. These are like already implemented and demos ready. Satyasri Prabhakar Mantripragada: it. Rajashekar G: We are working on the like complete platform level bigger picture is the first VP. Satyasri Prabhakar Mantripragada: Seeure architecture is a bigger picture of enterprise brain. Unifier is one part of it. Rajashekar G: Oh no. Satyasri Prabhakar Mantripragada: thought process. Rajashekar G: Oh no. Satyasri Prabhakar Mantripragada: Now we are actually trying to retrofit or redesign or rethink of the existing solution. Rajashekar G: Oh Satyasri Prabhakar Mantripragada: Okay. What do we want to Rajashekar G: no. Satyasri Prabhakar Mantripragada: achieve? So this will be retrofitted into the Rajashekar G: Oh no. Satyasri Prabhakar Mantripragada: architecture. Rajashekar G: Right. Retrofitted ante. Satyasri Prabhakar Mantripragada: So they're not developing something retrofitted existing applices Rajashekar G: Oh no. Satyasri Prabhakar Mantripragada: or processing UI whatever we may have thought of say five six agents to work together but as of now we went with a single 02:57:12 Rajashekar G: Complete Satyasri Prabhakar Mantripragada: agent mode. So approve we need to fit retrofit where you need to differentiate that which agent takes care of which part of the application. Rajashekar G: News and Oracle MVP. Satyasri Prabhakar Mantripragada: See you are working on platform. Rajashekar G: Oh no. Satyasri Prabhakar Mantripragada: Manisha's team is working on unifier. Rajashekar G: Yes. Satyasri Prabhakar Mantripragada: If you discuss on unifier then I'm confused. Rajashekar G: I'm saying Oracle Satyasri Prabhakar Mantripragada: Oh no. And there can be such any number of integrations coming into picture later. Rajashekar G: interfaces agent data source agent. data. Our end goal should be a new architecture at certain points. Oracle and how things are falling and Satyasri Prabhakar Mantripragada: Sorry, sorry. Rajashekar G: interface. Satyasri Prabhakar Mantripragada: Then last Rajashekar G: Okay. Satyasri Prabhakar Mantripragada: You mentioning Rajashekar G: Oh no. Satyasri Prabhakar Mantripragada: AC Rajashekar G: weeks. First thing Satyasri Prabhakar Mantripragada: no please understand Oracle unifier is priority priority by this time you would have completed core platform Oracle unifier is an add-on Rajashekar G: Oh, no. 02:59:36 Satyasri Prabhakar Mantripragada: Priority is also Rajashekar G: Her minimum Satyasri Prabhakar Mantripragada: priority. Rajashekar G: individual data complete new archives. Satyasri Prabhakar Mantripragada: uh see for now because we don't have that we are going with some dummy UI for now but it is not the final okay so for that we'll have a discussion today so Rajashekar G: Yes. Satyasri Prabhakar Mantripragada: drop meeting should schedule the meeting and explain and on how We wanted to present the UI. Rajashekar G: Okay. Okay. Satyasri Prabhakar Mantripragada: Okay. Rajashekar G: Sure. Satyasri Prabhakar Mantripragada: Okay. This we have a discussion with them. Rajashekar G: Sh. Satyasri Prabhakar Mantripragada: Should also work on their aspects. Rajashekar G: Okay. Satyasri Prabhakar Mantripragada: Let us get started on that part also. Rajashekar G: Okay, sir. Satyasri Prabhakar Mantripragada: So meanwhile core features which do not have dependency on design that you your team and Manisha's team will prioritize. Rajashekar G: Okay, got Satyasri Prabhakar Mantripragada: Yeah. Rajashekar G: it. Vara Kumar Jagarapu: Yes. H. Rajashekar G: Right. Vara Kumar Jagarapu: Um, Rajashekar G: Exact. Vara Kumar Jagarapu: low level design. Yes. 03:01:42 Rajashekar G: Got it. Vara Kumar Jagarapu: meaningful tasks with acceptance criteria which can be given to them directly and we can close that. Okay. Rajashekar G: Okay, got it. Vara Kumar Jagarapu: UX meeting right? Rajashekar G: meeting Manisha Gundapuneedi: This is Rajashekar G: schedule. It couldn't look slaughter 330 to 4. Huh? Manisha Gundapuneedi: 3:30 to 4 Thursday. Rajashekar G: Sir 3:30 to 4:15 BC Satyasri Prabhakar Mantripragada: 3:30 to 4:15 leads me Manisha Gundapuneedi: the leads. Satyasri Prabhakar Mantripragada: actually discuss how are we doing Rajashekar G: So shall I picture 2 to 230 230 Okay. Design enterprise brand design strategy Satyasri Prabhakar Mantripragada: 230. Good. Rajashekar G: and a design discussion. Vara Kumar Jagarapu: 2230 final Satyasri Prabhakar Mantripragada: Veterans Vara Kumar Jagarapu: time. Satyasri Prabhakar Mantripragada: three. Two to Rajashekar G: Uh, cadence is on the Rakkesh Satyasri Prabhakar Mantripragada: three. Rajashekar G: guys. Vara Kumar Jagarapu: And Rajashekar G: 23 guidance brainstorming Vara Kumar Jagarapu: then block Good Rajashekar G: block. Vara Kumar Jagarapu: afternoon. Satyasri Prabhakar Mantripragada: 330. That should be fine. Rajashekar G: Okay. Satyasri Prabhakar Mantripragada: foreign. Rajashekar G: 3:30 to 4:30 bet. Satyasri Prabhakar Mantripragada: Fine. So let us start working on entering them into Jira and then start uh okay timelines map Vara Kumar Jagarapu: Yeah. Low level Satyasri Prabhakar Mantripragada: J. Okay. Vara Kumar Jagarapu: communications we can write it in there. So mostly Rosie afternoon session learning we'll discuss with Rajes as Satyasri Prabhakar Mantripragada: Okay. Vara Kumar Jagarapu: Rash about this reason and maybe yeah we can keep them Satyasri Prabhakar Mantripragada: We may have a different guideline. Transcription ended after 03:06:24 This editable transcript was computer generated and might contain errors. People can also change the text after it was created.