> 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/readme.md).
# Docket
Docket tracks the decisions a project makes across sessions, and checks what breaks when one of them changes.
A record is one of three kinds. A **claim** is a statement the work depends on. A **decision** is a choice, with the reason for it. A **question** is something still open.
Records are only ever added. Nothing is changed or deleted. A later record can replace an earlier one, and the earlier one stays in the file, so you can read back how a choice changed.
Records link to each other. A record lists the ones it rests on, and a decision lists the ones it depends on. Mark a claim rejected, and every decision that depends on it is flagged as blocked.
A coding agent reads the current records before it works, so what you already settled is there from the start.
The records are one file in your project, shared through Git.
## Start here
Set up Docket
Paste a prompt and let your agent do it, or install it yourself.
You can use Docket from a terminal or ask your agent to record things for you. Once it is set up:
| I want to… | Read |
| ------------------------------------------- | --------------------------------------------------------------------------- |
| Save a choice or leave a question for later | [Recording decisions](/docket-docs/everyday-use/recording.md) |
| Find an earlier decision | [Reading your ledger](/docket-docs/everyday-use/reading.md) |
| Use Docket in an agent session | [Working with your agent](/docket-docs/everyday-use/agents.md) |
| Start from years of existing design notes | [Constructing on existing projects](/docket-docs/everyday-use/construct.md) |
| Share a ledger with my team | [Sharing and maintenance](/docket-docs/everyday-use/maintenance.md) |
## What goes in a ledger?
The file holding the records is called a **ledger**. The rest of this documentation uses that name. It holds three kinds of record:
| Record | What it keeps | Example |
| ------------ | ----------------------------------------- | --------------------------------------------------------- |
| **Claim** | A statement you want to assess or rely on | “The service already runs Postgres.” |
| **Decision** | A choice and the reason for it | “Use Postgres for billing because we already operate it.” |
| **Question** | Something you still need to find out | “Which database driver should we use?” |
You can connect a decision to the claims behind it or to a question it answers. When your choice changes, add a replacement. The earlier record remains available so you can follow how the decision changed.
## Pick up where you left off
Configured agent integrations load a **briefing** from the ledger. It gives the agent relevant records and instructions for finding more.
You can also ask for context about a particular task:
```sh
docket context --query "billing database"
```
Docket supplies the recorded context. You and your agent still need to check whether the evidence is current and whether a choice fits the work in front of you.
## When you want more detail
The [ledger reference](/docket-docs/technical-reference/ledger.md) explains states, relationships, and how Docket chooses records for a briefing.
The **Design and research** section explores the ideas behind Docket and proposals for future work. You can use the everyday guides without reading it.
[Source code](https://github.com/NovusEdge/docket) · [Releases](https://github.com/NovusEdge/docket/releases)
---
# 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/readme.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.