> For the complete documentation index, see [llms.txt](https://novusedge0.gitbook.io/docket-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://novusedge0.gitbook.io/docket-docs/everyday-use/reading.md).

# Reading your ledger

Use `list` to find a record, `show` to read it in full, and `graph` to browse its connections. Use `context` when you want a briefing for a task.

Examples with IDs use the ledger from [Recording decisions](/docket-docs/everyday-use/recording.md). Substitute your own record IDs when using these commands in another project.

## Find a record

```sh
docket list
```

The list shows each current record's ID, state, and text. A decision also shows its choice. A `<- c1` marker points to a supporting record.

You can narrow the list by what you need:

| To find…                                | Run                                        |
| --------------------------------------- | ------------------------------------------ |
| Open questions                          | `docket list --kind question --state open` |
| Decisions                               | `docket list --kind decision`              |
| Records mentioning Postgres             | `docket list --find postgres`              |
| A compact list                          | `docket list --oneline`                    |
| Earlier records as well as current ones | `docket list --superseded`                 |

Use `docket list --json` when you want to read the result from a script.

## Read one record

```sh
docket show d2
```

This shows the choice, its rationale, and any links to other records. Use `docket show d2 --json` for every field, including scope and evidence.

Replaced records remain readable by ID. To see a record as it stood earlier in the ledger, add `--at`:

```sh
docket show q3 --at d4
```

In the recording guide's example, this shows the question when `d4` answered it. Later changes do not affect that view.

## Browse connected records

```sh
docket graph
```

When the native viewer is installed, this opens a tree and a detail pane in your terminal. Select a record in the tree to read its details.

| Key                       | Action                              |
| ------------------------- | ----------------------------------- |
| Arrow keys or `j` and `k` | Move through records                |
| `space` or `enter`        | Collapse or expand a branch         |
| `tab`                     | Switch between the tree and details |
| `/`                       | Search                              |
| `q`                       | Quit                                |

See the [viewer reference](/docket-docs/technical-reference/installer-reference.md#browse-the-decision-graph) for detail scrolling, search controls, and output options.

If the viewer is missing, Docket prints a text graph and setup guidance. Piped output also stays as text:

```sh
docket graph | less -R
```

Use `--no-interactive` to request text output directly.

## Read the briefing for a task

```sh
docket context --query "billing database" --file billing/db.py
```

A **briefing** is a selection of records for you or your agent to read before working. Records that match the task receive more space. Other records may appear in a short index, and the footer tells you how much was included.

The briefing is a starting point. Use `docket show ID --json` to retrieve a record mentioned in the index, or `docket list` to browse beyond it.

With no query or file arguments, `docket context` uses changed and untracked files in your Git checkout as a guide. In a clean checkout, it uses the files from the latest commit. Pass `--no-auto-scope` to turn this off.

## Adjust what you see

To set a firm size limit:

```sh
docket context --query "billing" --max-chars 4000
```

The limit is measured in characters. The default minimum is 512. Without an explicit limit, Docket aims for 8,000 characters and can use more space for matching records.

To ask for the whole ledger within a budget:

```sh
docket context --all --max-chars 12000
```

To see changes since a record:

```sh
docket context --since d4
```

The [ledger reference](/docket-docs/technical-reference/ledger.md#bounded-context) covers selection rules, budgets, and coverage in depth. For help with missing context, see [Working with your agent](/docket-docs/everyday-use/agents.md#when-a-decision-is-missing).


---

# 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://novusedge0.gitbook.io/docket-docs/everyday-use/reading.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.