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

# Introduction

This documentation is the canonical reference for **KPK Funds**: actively managed, tokenised funds that run DeFi strategies onchain, with non-custodial settlement and onchain accounting.

**Who this is for:** depositors, integrators, and risk reviewers who need precise, up-to-date information about KPK Funds.

Funds run on KPK's onchain fund infrastructure, previously called the Onchain Investment Vehicle (OIV). They are issued by KPK and build on KPK's track record of managing more than $2bn in onchain treasury assets for DAOs over five years.

### Approach

{% columns %}
{% column %}
**Non-custodial**\
Assets sit in a Safe with no human signers and can only move through the Fund's onchain policies.
{% endcolumn %}

{% column %}
**Onchain policies**\
Every action the Fund can take is whitelisted onchain, down to the contract, function and parameters, in line with its investment framework.
{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column %}
**Onchain accounting**\
NAV is computed onchain from the Fund's positions and independent price feeds, so share prices can be verified by anyone.
{% endcolumn %}

{% column %}
**Composable**\
Fund shares are ERC-20 tokens that can be held, transferred and integrated with other DeFi protocols.
{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column %}
**Active management**\
KPK's team and automation agents manage each strategy within its limits, adjusting to market conditions.
{% endcolumn %}

{% column %}
**Multichain `beta`**\
A Fund can hold positions across EVM chains, with consistent accounting and controls on each.
{% endcolumn %}
{% endcolumns %}

### Explore

Each Fund has its own page covering its strategy, key information, risks and governance. The Infrastructure section explains how Funds work, how KPK decides what they can hold, and, under Architecture, every contract in detail. The Integration section is for builders. All Fund configuration changes are recorded in the [Changelog](https://docs.kpk.io/changelog).

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Mechanics</strong></td><td>The building blocks, subscriptions and redemptions, pricing, fees and governance.</td><td><a href="https://docs.kpk.io/funds/infrastructure/mechanics.md">Mechanics</a></td></tr><tr><td><strong>Investment framework</strong></td><td>How KPK decides what a Fund can hold and how much.</td><td><a href="https://docs.kpk.io/funds/infrastructure/investment-framework.md">Investment framework</a></td></tr><tr><td><strong>Architecture</strong></td><td>Contracts, deployment and onchain accounting in detail.</td><td><a href="https://docs.kpk.io/funds/infrastructure/architecture.md">Architecture</a></td></tr><tr><td><strong>Integration</strong></td><td>Create, monitor and cancel requests, and read share prices.</td><td><a href="https://docs.kpk.io/funds/kpk-fund-integration/subscription-request.md">Subscription request</a></td></tr></tbody></table>


---

# 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.kpk.io/funds/introduction.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.
