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

# Deliverables & Ownership

| Deliverable                | Included                           |
| -------------------------- | ---------------------------------- |
| Smart contracts / programs | Source code and deployment scripts |
| Frontend                   | Source code, branded to you        |
| Backend                    | Services and configuration         |
| Admin dashboard            | Where in scope                     |
| Documentation              | Setup, admin guide, handover notes |
| Deployment                 | Mainnet launch support             |

{% hint style="warning" %}
**TODO (team):** state your code ownership and licensing terms (e.g. full IP transfer on final payment), and key handover procedure.
{% endhint %}

## Key custody

You should own and control admin and treasury keys. We will never ask for your seed phrase.


---

# 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.solhuger.com/working-with-us/deliverables.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.
