> For the complete documentation index, see [llms.txt](https://docs.dynamichooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dynamichooks.com/templates.md).

# Templates

A template is a saved program with blanks. Launching from a template fills the blanks and installs the rules in one transaction. The first templates:

## Person

A market about a person with a handle. Fee 3%. Routing as in [Who gets paid](/who-gets-paid.md).

* `when Verified(ownership) then RouteToCreator` — once
* `when State(days_since_launch ≥ 90) and not claimed then SweepEscrowToHolders` — once

## Creator

A market launched by its own creator, verified at launch.

* `when State(liquidity ≥ L) then SetFee(150)` — once
* `when State(volume ≥ V) then ActivateRewards` — once

## Milestone

A team market with rewards off until something real happens.

* `when Verified(milestone) then ActivateRewards` — once
* `when Verified(milestone) then ReleaseIncentive(A, holders)` — once, after the rule above

## Stock-quoted

Any of the above with a Robinhood Stock Token as the quote asset. See [Quote in a stock](/quote-in-a-stock.md).

Templates are added by the protocol and, later, by $DHOOKS governance. Every template is published with its rules in full before any market can use it.


---

# 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.dynamichooks.com/templates.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.
