> For the complete documentation index, see [llms.txt](https://kkone.gitbook.io/kkone-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kkone.gitbook.io/kkone-docs/auto-launch/narrative-and-deployment-rules.md).

# Narrative and deployment rules

These settings decide which future X content is eligible and how many token concepts or deployments KK.one may attempt.

## Monitored X accounts

Select at least one supported public X account. Search and selected-account chips help you review the set before applying it. Monitoring an account does not imply that the account owner is affiliated with or endorses KK.one or any token.

## Narrative types

Choose one or more narrative categories:

* AI
* Tech
* Entertainment
* Crypto
* Meme
* News
* Politics
* Sports

Category detection is automated and can be inaccurate, incomplete, or delayed.

## Post types

Choose which source-post types are eligible:

* Post
* Reply
* Repost
* Quote

The default is **Post + Reply**.

## Filter keywords

Filter keywords are negative filters. If an eligible post contains one of the configured terms, KK.one skips it. Keyword matching is case-insensitive, and duplicate entries are normalized.

## Duplicate keyword rule

The default rule skips a detected narrative keyword if the same normalized keyword has already been used by the task within the previous 24 hours. This rule reduces repeated concepts; it does not guarantee that two independently generated tokens will never resemble one another.

## Ignore leading `$`

When enabled, a leading `$` is ignored during concept extraction. This affects symbol interpretation only; it does not remove or rewrite the original source post.

## Maximum concepts per post

Choose 1, 2, or 3. This setting counts distinct **token concepts from one post**, not network deployments.

Example: a post produces two qualifying concepts and the task selects Base and Robinhood Chain. KK.one may attempt up to four deployments: two independent concepts × two networks.

## Deployment limits

Deployment limits control launch frequency:

* per-hour maximum;
* per-day maximum;
* optional cooldown between launch groups.

The daily limit must be at least the hourly limit. These limits apply to qualifying launch concepts/events at task level; one event may still produce a separate deployment on each selected live network. A submitted or pending attempt may temporarily reserve capacity so the same action is not launched twice.

## Task launch cap

The task cap limits the total number of token concepts the task may launch over its lifetime. Choose Unlimited, a preset, or a positive custom number. It is distinct from the time-window deployment limits and does not multiply when one concept is deployed on both live networks.

## Network fee settings

### Base

Choose **Default**, **Default + 10%** (recommended), **Fast**, or a validated **Custom buffer**. Estimates are dynamic and the final network charge can differ.

### Robinhood Chain

V2 uses **Automatic** fee handling. KK.one does not expose Base-style speed or buffer controls for Robinhood Chain.

### Solana

Solana fee settings are not available in V2. Any Automatic/Manual Solana fee design is future-facing and does not enable a current Solana action.


---

# 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://kkone.gitbook.io/kkone-docs/auto-launch/narrative-and-deployment-rules.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.