> For the complete documentation index, see [llms.txt](https://taskflow-1.gitbook.io/taskflow-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://taskflow-1.gitbook.io/taskflow-docs/architecture-decisions/0002-cursor-pagination.md).

# ADR-0002: Cursor pagination

Status: accepted.

## Context

The board is the product's hot path, and it is a moving target: while a client pages through a column, other users create, complete, and reorder tasks. Offset pagination skips or repeats rows under exactly that concurrent-write pattern, which users experience as tasks vanishing or appearing twice.

## Decision

All list endpoints use keyset (cursor) pagination: an opaque cursor, a default page size of 50, a maximum of 200, and `next_cursor` set to `null` at the end of a list. The full contract is in `taskflow-api-docs`, `api-conventions.md`.

Board queries are backed by a `(project_id, status, id)` index so a page is an index range scan, not a sort.

## Consequences

* Clients cannot jump to "page N". Accepted: boards are streams, not documents, and no client has needed random access.
* Cursors are opaque and forgiving — out-of-range values are clamped, never an error, so a paging client cannot wedge itself.
* New list endpoints inherit the rule; an offset-paginated endpoint is a review finding.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://taskflow-1.gitbook.io/taskflow-docs/architecture-decisions/0002-cursor-pagination.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
