> 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/reference.md). # Reference Use this section when implementing or operating rawctx after completing a task-oriented guide. ## Quick lookup * CLI command map: authentication, evidence, reconciliation, trust, and CI recipes * Configuration and authentication: registry precedence, token types, application scopes, and tenant policy fields * Production readiness checklist: controls to review before the first production write * Errors and troubleshooting: typed exceptions, HTTP status handling, and retry decisions * Glossary: evidence, commitment, reconciliation, and trust terms ## Endpoint rule Use the tenant registry saved by `rawctx login` for answer evidence, reconciliation, evidence assets, policy, and other workspace operations. Never use the Hub browser BFF as a CLI or SDK registry. ## Version rule The installed CLI and SDK define the version-specific options and signatures. Check `rawctx --version`, `rawctx COMMAND --help`, and the dependency version recorded in your build before you automate a documented example. --- # 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/reference.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.