> For the complete documentation index, see [llms.txt](https://guardian.hedera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guardian.hedera.com/docs/develop/community-and-contributing/community-standards/documentation-standards/page-templates/concept-template.md).

# Concept Template

How to contribute a concept page to the Guardian docs

{% hint style="info" %}
**Concept Template**

Use for: feature overviews, explanations of platform constructs, background on how something works. A concept page should never contain steps — those belong in a task page. The concept page is typically the parent container in GitBook, with task pages as children beneath it.

**Concept Page Title:** *Name the thing, not the action — e.g. "Policy Integrity Tests", "TrustChain", "Verifiable Credentials"*
{% endhint %}

One to two sentences. Plain language definition of what this is.

#### The problem it solves

What would happen without this feature or capability. Why it exists.

#### How it works

The mental model. How to think about this conceptually. Not steps — those belong in the task page.

#### Key distinctions

How this differs from something it might be confused with. Remove this section if there is nothing to distinguish.

#### Related

* Task: how to use this
* Reference: full specification
* Concept: related concept


---

# 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://guardian.hedera.com/docs/develop/community-and-contributing/community-standards/documentation-standards/page-templates/concept-template.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.
