# Audita LLM Runtime `llm.NewRuntime` assembles one captured PromptKit engine using its default catalog, Audita's embedded prompts and schemas, and optional operator sources anchored to the recorded application main context. Captured host sources and message files are passed to output collision checks. An embedded-only diagnostic construction distinguishes shipped asset failures from operator-source failures; it never replaces the requested engine. Each resolved pipeline entry receives role-bound clients with its selected profiles and effective budgets. Clients share engine-local backend admission. The adapter uses `PrepareExecution` and `RunPrepared` on the same handle, passes Audita's per-call schema and repair budget, and decodes only validated results. PromptKit owns backend and credential selection. The adapter uses captured credential source names for artifact redaction without inspecting unrelated environment values. See the [integration contract](../integrations/openai-compatible-llm.md) for failure behavior and the [configuration reference](../config.md) for sources. When correction repair is enabled, the proposal call retains its prompt, effective variables, prepared messages, and full final response for section-local replay. The adapter renders the repair definition with the selected profile, appends only that branch’s history, and checks the original prepared prefix before execution. The complete conversation is sent to the selected provider; provider rejection ends that branch as unavailable. The requested repair definition is retained in call attribution alongside native base-prompt metadata. The runner supplements each repair instruction with its current proposal preview as described in the [module guide](modules.md#failure-and-outcome-behavior). The bundled prompts separate durable system principles from the initial user assignment so later repair instructions can allow acceptable minor cleanup; see [prompt instruction ownership](prompts.md). The observation collector tracks logical calls and execution events. Ordinary reports use compact safe outcomes; request and response evidence is optional debug material. The runner preserves ordered pipeline traversal and deterministic section collection while canceling and joining peers on fatal errors.