Is that, is that correct?

A- absolutely.

Absolutely.

And, and, you know, I guess I, I might see it maybe, uh, a little bit differently.

We're not starting with a, you know, token max everything.

That's not the, the mindset, um, we have.

For that, that focused, um, you know, AI development work where we're really trying to optimize and improve a particular process or, or an experience, we're always focused that that's the outcome.

Is Mythos and, and more specifically Project Glasswing something that's helping you in that way? Like, even if you're not testing out the model, are, are they sort of advising you on how to think about these things?

And I'm curious, how has this movement enabled your teams to think differently, um, not only about the kind of projects that they're able to pursue, but, um, just what it means to kinda start fresh?

Yeah.

Um, I-- well, well, first of all, it's great, great, great to see everybody, uh, today.

As, as we started our, our rollout, um, similar to it, to it sounds like what, um, what Shekhar did, did at The Hartford, um, brought in, um, agentic tools, um, and really focused on modernizing the way in which we, we build our systems and, and write our code.

Um, we've got a pretty specific methodology for, for how we evaluate, um, tho-those kinds of things and, and measure value.

Long story short, went through all of that, and much like I'm sure everybody found in the room, um, found really meaningful, robust measures of improvement in terms of how companies like ours can create, um, software of the future.

Um, and at the same time, um, as, as our folks were, were working on that, um, there was certainly an undertone and a little bit of, "What does this mean for me? Um, am I still gonna have a role here?" And, and things of that nature.

Again, everyone has a different approach now, and I don't know that we've landed on a right answer, but curious how you're, you're thinking through this.