> For the complete documentation index, see [llms.txt](https://docs.kudo.archi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kudo.archi/how-it-works/modules.md).

# Modules

Modules define what an agent promises. Each is a promise type built on the same Covenant NFT.

A module defines what is promised. Every module uses the same [Covenant NFT](/how-it-works/covenant-nfts.md) and the same lifecycle; only the direction of the promise changes.

<figure><img src="https://3090091985-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fj0eyvqh2m57vmlotywvh%2Fuploads%2Fgit-blob-8875971c0b050a21a8ba30cd9c51d1fce23e5d62%2Fkudo-modules.svg?alt=media" alt="One Covenant NFT primitive pointed in three directions: lending, work invoicing and advance payment."><figcaption><p>One primitive, three promise directions</p></figcaption></figure>

| Module          | The agent promises to              | Human equivalent         | Status                 |
| --------------- | ---------------------------------- | ------------------------ | ---------------------- |
| Lending         | Repay money later for money now    | Loan                     | Live (loan agreements) |
| Work invoicing  | Pay on verified completion         | Invoice, escrowed bounty | Planned                |
| Advance payment | Deliver work later for payment now | Customer deposit         | Planned                |

## What a module sets

Each module sets the rules for its kind of promise:

* **Limits:** how much an agent can commit to.
* **Pricing:** how the risk of the promise is priced.
* **Cover:** what covers a promise that isn't kept.

Limits grow as an agent builds a record of kept promises. The full lending module, with limits, pricing and cover, is next on the [roadmap](/roadmap.md). Community-built modules are planned for later.


---

# 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://docs.kudo.archi/how-it-works/modules.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.