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

# 15. Roadmap

## Roadmap

KIZUNA is being built step by step.

The roadmap begins with the core AI community manager, expands through project knowledge and Telegram, and gradually develops the broader KIZUNA ecosystem.

Each phase builds on the foundation of the previous one.

***

### 01

#### Foundation

**Q3 2026**

The first phase focuses on establishing the core KIZUNA product and its technical foundation.

* Build the core KIZUNA AI community manager
* Establish project identity and context
* Create the initial knowledge layer
* Connect project websites, GitBooks, documentation, and FAQs
* Establish the core Telegram experience
* Develop the initial backend infrastructure
* Prepare the first project deployment flow

**Focus:** Build the core.

***

### 02

#### Connection

**Q4 2026**

The second phase focuses on making it easier for projects to connect their knowledge and deploy KIZUNA.

* Improve KIZUNA agent creation
* Refine project identity and configuration
* Improve knowledge source connection
* Expand website, GitBook, documentation, and FAQ support
* Improve knowledge processing
* Refine Telegram deployment
* Improve the overall setup experience for project teams

**Focus:** Connect knowledge to community.

***

### 03

#### Intelligence

**Q1 2027**

The third phase focuses on improving how KIZUNA understands and works with project knowledge.

* Improve project-specific responses
* Strengthen context handling
* Improve knowledge retrieval
* Improve response relevance
* Expand knowledge processing capabilities
* Improve conversation experience
* Introduce deeper project context

Advanced retrieval architecture and AI infrastructure will evolve alongside the product.

**Focus:** Make KIZUNA understand more.

***

### 04

#### Expansion

**Q2 2027**

The fourth phase expands KIZUNA beyond its initial product experience.

* Expand supported knowledge sources
* Introduce additional project integrations
* Expand community interaction capabilities
* Improve project administration
* Add additional ways for communities to access project knowledge
* Expand KIZUNA's community-support capabilities

Additional platforms and integrations will be introduced based on product requirements.

**Focus:** Expand where KIZUNA can operate.

***

### 05

#### Ecosystem

**Q3 2027**

The fifth phase focuses on building the broader KIZUNA ecosystem.

* Expand the $KZN utility layer
* Develop ecosystem programs
* Introduce additional ecosystem functionality
* Support broader project participation
* Expand community initiatives
* Build new experiences around KIZUNA and $KZN
* Strengthen the connection between the product and token ecosystem

**Focus:** Build the KIZUNA ecosystem.

***

### 06

#### Intelligence Layer

**Q4 2027 →**

The long-term phase focuses on KIZUNA becoming a broader intelligence layer for project communities.

* Expand KIZUNA's knowledge capabilities
* Support more advanced project-specific agents
* Enable deeper project context
* Expand integrations and community environments
* Support a broader range of project ecosystems
* Continue developing the KIZUNA agent framework
* Grow the KIZUNA builder and project ecosystem
* Explore new ways for communities to interact with project intelligence

**Focus:** Make project knowledge an active intelligence layer.

***

## The KIZUNA Path

The roadmap can be summarized as:

**Q3 2026**

FOUNDATION

Build the core.

↓

**Q4 2026**

CONNECTION

Connect projects and knowledge.

↓

**Q1 2027**

INTELLIGENCE

Make KIZUNA understand more.

↓

**Q2 2027**

EXPANSION

Bring KIZUNA to more environments.

↓

**Q3 2027**

ECOSYSTEM

Build around the product.

↓

**Q4 2027 →**

INTELLIGENCE LAYER

Turn project knowledge into an active layer for communities.

***

### Roadmap Principle

KIZUNA follows a product-first approach.

The priority is to build a useful AI community manager, establish the knowledge layer, connect it to Telegram, and create a strong foundation before expanding the broader ecosystem.

Each phase builds on the previous one.

As KIZUNA develops, individual milestones and timelines may evolve based on product development, technical requirements, and ecosystem priorities.

**BUILD THE AGENT.**

**CONNECT THE KNOWLEDGE.**

**SERVE THE COMMUNITY.**

**GROW THE ECOSYSTEM.**


---

# 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://kizunai.gitbook.io/kizuna-docs/15.-roadmap.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.
