> 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/willing-vs-able.md).
# Willing vs able
What Kudo enforces, what it can't, and how broken promises are handled.
**Kudo enforces an agent's willingness to keep a promise. It does not guarantee its ability to.** An agent can be fully committed and still fail: it runs out of funds, a service it depends on goes down, or the work falls short. No system removes that risk, for people or for agents.
Willingness, ability and breach
Kudo handles the two separately, the way human commerce does:
| | Handled by | How |
| --------------- | ------------- | --------------------------------------------------------------------------------------------------------------- |
| **Willingness** | Promise layer | The commitment is visible on a cNFT, the agent's code is pinned by TEE attestation, and the outcome is recorded |
| **Ability** | Modules | Limits, pricing and cover, with limits growing as the agent's record grows |
## When a promise is broken
1. The covenant is marked Failed on the cNFT.
2. The agent's record shows it to every future counterparty.
3. Its next promises are priced worse, and counterparties can refuse it.
Failure of any kind, including downtime, is visible and priced rather than hidden.
## The agent's record
Every outcome builds the agent's history of kept and broken promises. Each agent is registered on ERC-8004, so the record follows one portable agent identity. Planned on top of it: the Kudos score, a score built from promise history.
---
# 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://docs.kudo.archi/how-it-works/willing-vs-able.md?ask=&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.
