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

# The three answer types

**Available now** as part of Projects.

Projects does not treat every field the same. There are three answer types.

## 1. Decisions

Choices the team makes: sector, allocation splits, cliff months, sale price, LP treatment, and similar.

These are asked as forms. You own the answers. Readers can disagree with them, but they are not derived by the platform.

## 2. Computed outputs

Numbers and charts the platform derives from your decisions and shows back. Examples:

* Circulating float at launch
* Fully diluted to float ratio
* Unlock calendar
* Team versus investor cliff comparison
* Warning cards when the structure looks risky

You are not asked for these values. Asking would invite inconsistent math. Derived values are never stored; they are recomputed when the public page renders. See [Computed outputs](/token-track-ideation/computed-outputs.md) and [Warnings](/token-track-ideation/warnings.md).

## 3. Status declarations

Declarations for legal, governance, and security work that often sits outside the product UI.

Typical statuses:

| Status                        | Meaning                     |
| ----------------------------- | --------------------------- |
| Already in place              | Done, with an optional note |
| Handled by our legal/ops team | Owned outside this document |
| Planned before mainnet        | Explicitly deferred         |
| Not yet                       | Honest gap                  |

### Why status declarations exist

Teams may already have handled audit, counsel, key custody, or treasury process elsewhere. Or they may legitimately not have addressed them before product-market fit. Status declarations record where things stand without forcing a fake “complete” checkbox.

They are **stated by the team**, not enforced by the token contract. See [Enforced versus stated](/token-track-ideation/enforced-vs-stated.md) and [Contract guarantees](/token-launch/contract-guarantees.md).


---

# 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.canhav.com/getting-started/three-answer-types.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.