> For the complete documentation index, see [llms.txt](https://kusuconsult-1.gitbook.io/doerdapp-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kusuconsult-1.gitbook.io/doerdapp-docs/copyright/codebase-and-licensing-structure.md).

# Codebase & Licensing Structure

DOER DAPP may consist of:

* Proprietary infrastructure components
* Open-source libraries
* Third-party SDK integrations
* Blockchain protocol dependencies

Open-source components remain governed by their respective licenses.

Proprietary components remain the exclusive property of DOER DAPP unless explicitly released under an open-source license.

Nothing in this notice grants rights to:

* Copy proprietary backend logic
* Fork protected UI architecture
* Reproduce brand identity
* Repackage the platform for commercial redistribution

unless expressly authorized in writing.

### Smart Contracts & On-Chain Deployment

Smart contracts deployed by DOER DAPP are:

* Immutable once deployed
* Publicly verifiable on-chain
* Transparent by design

However:

Public visibility does not equal public ownership.

While the contract bytecode may be publicly accessible on-chain, intellectual ownership of:

* Contract architecture
* Protocol design
* Tokenomics structures
* Execution frameworks

remains with DOER DAPP unless explicitly open-sourced.


---

# 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://kusuconsult-1.gitbook.io/doerdapp-docs/copyright/codebase-and-licensing-structure.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.