> 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/cli-command-map.md).

# CLI command map

Use `rawctx COMMAND --help` for the exact options installed in your environment.

```bash
rawctx --version
rawctx --help
rawctx COMMAND --help
```

## Authentication

* `rawctx login`: authenticate and store a local API token and tenant registry.
* `rawctx logout`: revoke or remove the local token.

## Evidence and trust

* `rawctx reconcile run|get|findings|proof`: run and inspect independent reconciliation.
* `rawctx trust status|policy`: inspect trust state and policy.
* `rawctx trust proof answer`: download an answer proof bundle.
* `rawctx trust verify`: verify a proof locally or with supported online checks.
* `rawctx trust anchor run`: workspace or platform administration operation; do not put it in a normal application write path.

## Automation conventions

* Prefer `--json` for machine-readable output.
* Pin the rawctx dependency version in CI.
* Treat documented non-zero exit codes as policy gates.
* Do not parse human-readable error messages when the Python SDK's typed errors fit the workflow.

## Evidence verification recipe

```bash
rawctx trust proof answer ANSWER_LOG_ID --output answer-proof.json
rawctx trust verify answer-proof.json --json
rawctx trust verify answer-proof.json --online --json

rawctx reconcile run reconciliation.json --json
rawctx reconcile findings RUN_ID --json
rawctx reconcile proof RUN_ID --output reconciliation-proof.json
rawctx trust verify reconciliation-proof.json --online --json
```

Creating an answer does not fetch or verify its proof. New leaves can remain pending until a signed checkpoint and required external receipts are available.

## Exit-code discipline

* `trust verify` exits non-zero when verification fails.
* Usage, authentication, registry, and validation failures also exit non-zero.

In CI, label a policy gate separately from an infrastructure failure. Check the installed command's help because output formats and options are versioned with the CLI.


---

# 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/cli-command-map.md?ask=<question>&goal=<endgoal>
```

`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.
