GMT20260507-123228_Recording_1440x900
Summary
The transcript discusses the logic behind emergency banking and the complexities involved in real-time mapping of customer account values. The speaker explains that each domain carries different sets of values and that the system becomes increasingly complex as more domains are added. The speaker also mentions that the system is not mapping tiers directly but rather runtime conditions, consequences model, execution context, and dependencies relationship.
Chapters
-
0:58
on the zoom call now okay great great great we are here okay so the content that you provided yes okay emergency banking so the logic that uh that is behind this like means a view customer account you have mapped at 233 t3 executive payment…
-
5:09
contractor, AI agent, emergency override, dedicated authority, licensing jurisdiction, MFA complete, on -call, lastly suspended account. You got that part so far? The patient conditions, ICU patient, is it an ICU patient, right? Is it a cel…
-
6:47Chapter 3: it's got some clarity. 129s · Speaker 3
it's got some clarity. But we need to make some clarity, right? Perfect. Then the harm tier emerges. Just hold tight. Then the harm tier emerges. It's not hard code, as you already know. For example, doctors open ICU medication record durin…
-
8:56Chapter 4: And the consequence classification can make the harm tier different from what you started with. 62s · Speaker 4
And the consequence classification can make the harm tier different from what you started with. Correct. So you can have, you assume a... tier one for a health record but if it is um for a health environment but if it is a simple uh gdpr is…
-
9:58Chapter 5: well And here I've mentioned all of that. 301s · Speaker 1
well And here I've mentioned all of that. Let me show you some designs so that you can align with that also. These are the test design machines. So we could be making a beautiful design. Yeah, no, I got you. It's a test design. Go ahead. Ye…
-
15:00Chapter 6: action that you provided on the basis that I have tried to done the mapping. 299s · Speaker 2
action that you provided on the basis that I have tried to done the mapping. And no, as long as you use the generic terms, you're fine. Right. And that's okay. Okay. So basically action would be remain constant as it is, but you can add any…
-
20:00Chapter 7: to be tied to the runtime. 80s · Speaker 2
to be tied to the runtime. But only if assigned patient, emergency, active. How I'm going to get these values? Valid, no synonyms by no actor. Eventually, I shouldn't themselves need. Oh, you
-
21:20Chapter 8: got to give them canonical IDs. 63s · Speaker 1
got to give them canonical IDs. So, add read patient record, export live resort, execute payment, add AI tool call. Does that make sense? I'm not able to map, actually. So, basically, you are trying to say there would be further mapping wit…
-
22:24Chapter 9: Hey, Thomas. 301s · Speaker 4
Hey, Thomas. Hey, Karen. Sir, I think, Akash, I think you did cover that part in the data classification part. I think because the runtime. Because you need these values. Even if you're giving like a parental permission, I think you had cov…
-
27:25Chapter 10: created by default. 155s · Speaker 2
created by default. It won't act as the same. And third is the AI agent. So if... uh there is an api would be uh hitting us right so we can give separate case of permission to that uh ai actor so that there's no deny in that case and uh tho…
-
30:01Chapter 11: Okay. So let me take a look at this. 250s · Speaker 5
Okay. So let me take a look at this. So you said edge cases, again, it came from the base camp stuff and some documents I've shared. So no actor outside of matrix can act. So then the meaning is on register actor equal deny. No action outsi…
-
34:11
question on this like i think to understand this is more technically uh akash can you show that so what i'm assuming is because i've already selected my industry right like it's it's belonging to the healthcare. Now, when I'm classifying it…
-
37:14Chapter 13: Yeah, so I think Akash is looking for like the flags list, which we, but industry -wise. 304s · Speaker 5
Yeah, so I think Akash is looking for like the flags list, which we, but industry -wise. I think that's what you're looking for, right, Akash? Yes, yes, yes. All the flags which will be available for specifically healthcare. All the flags? …
-
42:18Chapter 14: these values showing this is clear, right? 77s · Speaker 4
these values showing this is clear, right? We would be getting from APA only. And another step, which is step five, step three, step four, step five. Okay. So this is basically the enforcement contact layer, right? I think this is what you …
-
43:36
right? So we'll verify on the basis of the tier we are getting. And if the tier is 3, we are getting from the request. Then there's another key, different type of keys that we want to verify. On the basis of that, we would be giving deny, a…
-
46:17Chapter 16: Okay. Because it's being treated as permission -based instead of wrong -time thematic. 132s · Speaker 6
Okay. Because it's being treated as permission -based instead of wrong -time thematic. Does that make sense? So the role that you get set up with, Akash, so if you get set up as a doctor, does it mean you can always read a patient record? I…
-
48:29Chapter 17: it makes sense. 89s · Speaker 4
it makes sense. But we are not mapping. But that's runtime. I want to constrain you to runtime. If you leave that context, you're not building Aurelium as a whole. Okay. So caring from your point of view, what I'm doing wrong. It's not the …
-
50:00Chapter 18: 14, 15 domain, how the nesting hierarchy works and what are the default values that we need to consider while doing the mapping? 164s · Speaker 5
14, 15 domain, how the nesting hierarchy works and what are the default values that we need to consider while doing the mapping? The default values, I already sent it to you in an email, Akash. That's the overlay. That's the default values,…
-
52:46Chapter 19: Let me understand this, Akash. 137s · Speaker 4
Let me understand this, Akash. In this step, you are assigning all the actions to a tier, right? Yeah. That's what you're showing, right? Yes. Okay. So all these actions are being assigned to your tier. So from my understanding, this screen…
-
55:03Chapter 20: That's a question for you, Chavez. 205s · Speaker 5
That's a question for you, Chavez. Oh, sorry, Thomas. I thought you were asking. How are you, how were you able to get the concept of this like this? Because you, every call, I think Karen and I have been noticing you have been knowing the …
-
58:31Chapter 21: But then too, Thomas means once the industry is being set up or selected, the values won't be changed or system cannot be reverted back. 300s · Speaker 4
But then too, Thomas means once the industry is being set up or selected, the values won't be changed or system cannot be reverted back. So the, the Shabik, what Shabik is saying makes sense, right? Means whatever industry used like at the …
-
1:03:32Chapter 22: into runtime enforcement philosophy. 117s · Speaker 3
into runtime enforcement philosophy. And for me, this screen is telling me that certain execution conditions are unsafe regardless of customer preference. Right Akash? Yes. Right, because unknown classification equals hope. That's essential…
-
1:05:29
is part of the runtime threshold you're going to be setting. These levels would be mapped. The sensitivity level, right? These all values are mapped with the data classification. So if the combination of these values comes, right? and accor…
-
1:07:16Chapter 24: right? So the amount is not a random value, for example, in terms of the institution. 300s · Speaker 5
right? So the amount is not a random value, for example, in terms of the institution. It is a runtime financial risk threshold, right? So to plain English, $50 office reimbursement is probably allowed. okay large transfer five million wire …
-
1:12:17Chapter 25: greater than 10K, 100K evaluated, and so forth. 64s · Speaker 2
greater than 10K, 100K evaluated, and so forth. Policy Studio is different, guys. It's how exactly should a core evaluator enforce this at runtime? Now we're moving to deterministic logic, runtime conditions, evaluation, ordering, policy ve…
-
1:13:21Chapter 26: I got it. 308s · Speaker 4
I got it. How about you, Akash? Yeah, I got some of the information here. I'll try to. I know Akash. Akash will want to go back to go through requirements and then confirm that. Go ahead, Akash. Ask the question. Don't hold it. Maybe you'll…
-
1:18:29
is one question the contract is still being done in the cds floor right so just to interpret the enforcement contract is what you're asking right right right oh you're saying is it being done in the um CDS flow? CDS flow. Yes. The enforceme…
-
1:19:48Chapter 28: let's discuss Shovek internally. 301s · Speaker 3
let's discuss Shovek internally. Yeah. Then also we have an email, right? Yeah, you have the emails. You also got a policy studio. emails too that Denner J has. Remember when we had the auto call? Denner J. Yeah. So all of that should help …
-
1:24:49Chapter 29: right? Because that's. 302s · Speaker 1
right? Because that's... Yeah, this is all coming from Basecamp, yeah. Yeah, because that's essentially what I just pulled. And Basecamp has step three as customer -defined business meeting. okay let me check this check the check the docume…
-
1:29:52
back to your permission mapping and keep herping on that because i don't we we cannot go the traditional route you gotta treat it as a Condition context, wrong times came out, right? You got to treat it as that. Everything else looks to be …
-
1:34:50Chapter 31: I just got it. 136s · Speaker 4
I just got it. I haven't got it yet. Oh, got it. No, just got it. As you were seeing that documentation, Akash, it's just things that you should live by. If you start seeing yourself going to traditional rap, it's probably wrong. No. Okay. …