Taylor Mullen

And then it checks it off once it's done.

And it keeps going back and forth.

And one of the really cool things is it makes sure like when it validates that things are working as expected, that those validations are actually at a level that is coherent.

So there's a thing called code coverage, which we have.

And code coverage is something that in software engineering says, have you validated every piece of code you've written to do the right thing?

And it says, hey, it must be 80% or higher.

And if it's not 80% or higher, it goes back and writes some more validation.

It has this really nice reinforcement loop to make sure that it's building exactly what you want and doing it in the best way possible.

So when it does something that I haven't given, so it doesn't know what it can and can't do, but when it ends up doing something that it can't do, then it asks me if it's allowed to do that is the intention.

So we kind of, because basically every single action that it takes, we kind of run through this pipeline that says, hey, is this allowed or is this not?

And the is this allowed or is this not is tied to whatever this policy is that you've written.

Okay.

Right.

And the policy might say, for those who are familiar, there's a command called LS.

And the intention is, it's like saying, imagine like saying open your folder, like a folder on your computer.

Okay.

What files are in?

That's effectively what it does.

well, I don't want it to ask me just to look at my folder.

Feel free to look at stuff.