> For the complete documentation index, see [llms.txt](https://docs.lleverage.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lleverage.ai/reference/technical-and-support/runtime-and-security.md). # Runtime & security Technical reference for execution visibility and security-related runtime questions that do not belong in the everyday builder or operator path. This section is a technical reference, not a second administration area. For day-to-day configuration such as Connections, Members, Secrets, API Tokens and model-provider settings, use [Control](/administer-and-govern/control.md). For ownership, rollout and security review, use [Administer and govern → Security and assurance](/administer-and-govern/security-and-assurance.md). ## Execution visibility The customer-facing execution record lives in [Monitoring](/build-and-improve/monitoring.md). It is the place to inspect runs, traces, inputs, outputs and execution activity when debugging or reviewing operational behaviour. A successful technical execution is not by itself proof that the business outcome was correct. Operational review still needs the relevant source data, configured rules and human decision boundaries. ## Security reference Security questions should be tied to the actual deployment: identities, Projects, Connections, credentials, data sources, external actions and the people who can change them. Do not infer certification status, data-processing terms, retention commitments or other formal assurance facts from generic product documentation. Those require current assurance material supplied for the relevant review. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.lleverage.ai/reference/technical-and-support/runtime-and-security.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.