> For the complete documentation index, see [llms.txt](https://ura-labs-1.gitbook.io/ura-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ura-labs-1.gitbook.io/ura-documentation/capacity-protocol/accounting-and-reconciliation.md).

# Accounting & Reconciliation

The Capacity Protocol targets verifiable pool accounting rather than per-coin DUST attribution.

## Evidence chain

1. An identifiable sponsorship request is accepted.
2. Capacity is reserved under an application policy and budget.
3. The operator signs an execution receipt.
4. On-chain inclusion is observed.
5. Receiver capacity is measured across an observation window.
6. The result is appended to reconciliation.

## Core fields

The accounting model can bind provider, partner, campaign, registration reference, receiver, operator, application, sponsorship request, execution receipt, chain evidence, settlement period and revenue allocation.

## Invariant

The target invariant is pool-level conservation: observed capacity supplied and spent must reconcile across the same bounded accounting period.

Canonical request identifiers, public verification and final commercial settlement mechanics are still being hardened.


---

# 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://ura-labs-1.gitbook.io/ura-documentation/capacity-protocol/accounting-and-reconciliation.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.