> For the complete documentation index, see [llms.txt](https://rawctx.gitbook.io/rawctx-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rawctx.gitbook.io/rawctx-docs/documentation/integrations.md). # Integrations rawctx connects to other systems through evidence boundaries. It does not replace the runtime system that generates answers, the trace backend that records agent execution, or the business system used for independent reconciliation. ## OpenTelemetry Use OpenTelemetry trace references when an application already emits OTLP logs or spans. rawctx maps submitted trace IDs, message attributes, source references, and optional inference commitments into answer evidence. The mapping keeps records joinable but does not prove that the upstream trace is true. ## Evidence assets Use Media and file evidence for controlled audio, video, text, and file objects. Runtime retrieval creates a purpose-bound access event that can be attached to the answer record. ## Independent systems of record Use Independent reconciliation to compare rawctx logs with a bounded export from a business or provider system. Keep the reference source operationally separate enough that both records cannot be rewritten in lockstep. ## Integration checklist * Stable `application_key` and idempotency key * Exact workspace registry and least-privilege credential * External trace/message IDs that are safe to retain * Explicit text-storage, retention, and keyed-hash policy * Stable source identifiers and commitments when available * Bounded retry behavior that preserves idempotency --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://rawctx.gitbook.io/rawctx-docs/documentation/integrations.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.