> For the complete documentation index, see [llms.txt](https://hypercerts.gitbook.io/hypercerts-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hypercerts.gitbook.io/hypercerts-docs/getting-started/introduction-to-impact-claims.md).
# Introduction to Impact Claims
### Introduction to Claims
Everything in the Hypercerts ecosystem consists of claims records.
The primary "activity" claim—commonly referred to as the hypercert—serves as the central record that tracks impact work. On the diagram below, it's referred to as the green box.
Additional claims can then be attached to this core activity, including measurement claims, evidence claims, contribution claims, evaluation claims, and other supporting claims that substantiate or provide context for the claimed impact.
### Standalone
Claims are standalone. They do not necessarily have to be linked to each other. You can create a measurement claim first, and then later attach it to a specific activity claim, if required.
Hypercerts can exist as a standalone activity claim, or it can be tokenized to then be listed up for sale in a marketplace.
---
# 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://hypercerts.gitbook.io/hypercerts-docs/getting-started/introduction-to-impact-claims.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.
