which typically look like a file system. Wow. Context engine. What this needs to do is basically have all that static content, of course, but also be able to at runtime, when a query comes through from the software engineer, typically, how do I implement this feature? At runtime, it's able to pull all that static source across your entire corporate knowledge corpus, essentially, whether it's any many SaaS apps, different systems of records, and pull in the runtime singles in order to analyze, reason across all those surfaces, all those different data stores, and then run exhaustively to actually find all of the things that are important, and then send a token optimized, aka small, response to the agent with all the details it needs to then execute its next steps. So, you'll see through this, but typically that means getting the best context up front makes all agent choices and actions after that even better. So, if you give it, for example, a key research packet of like, "Hey, I want to do a new integration." And it you drop a packet so that it creates a good plan, and that information says, "Here's our patterns. We use factory pattern. We do these things." Like, all the things about your organization, it's then able to trigger its background agent jobs to go grep your code base to do the things it needs to with higher accuracy, which means it's more token efficient, and it gets the job done faster.