> For the complete documentation index, see [llms.txt](https://docs.tachyo.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tachyo.ai/under-the-hood/what-we-dont-do.md).

# What we refuse to do

Some of these are ethical lines, some are methodological ones. All of them are load- bearing: the value of everything else here depends on them holding.

## We do not publish anyone's private wallet

Thousands of anonymous wallets are mapped to the people behind them, and that mapping powers real signal: a known wallet receiving an allocation days before anything is said publicly.

**The mapping is never published as an address next to a name.** The product is the signal and the quality read, not burning a person for reach. The moment you start doxxing people for engagement is the moment trust is gone, and trust is the only real moat in this market.

No wallet is pinned to an identity on a guess, either: two people confirm it independently before it counts for anything.

## We do not give financial advice

Tachyo reports what wallets did and what our models make of it. There is no buy call, no target, no stop, no position size. **Past performance is not a promise about the next trade**, including our own backtest numbers.

What you do with the information is yours, and so is the outcome.

## We do not invent numbers

* A failed measurement renders as **unknown**, never as a zero.
* A wallet with no trade history shows **no PnL**, not `$0`.
* A position that was received rather than bought has **no return**, not a 0% return.
* A scarcity counter that cannot be computed **hides itself** rather than showing an invented number.

This costs us: empty cells look worse than confident numbers. They are the honest rendering, and the alternative quietly corrupts every decision downstream.

## We do not rate what we cannot measure

A wallet without enough closed-trade history stays **unrated**, however tempting a flattering letter would be. Thin evidence is capped below the top tier by design. See [How wallets are scored](/under-the-hood/scoring.md).

## We do not present our population as the market

Anywhere the product shows tracked-wallet volume or activity, it is labelled as ours. A token with no activity in our feed may be trading perfectly well on the open market, and the product says which one it is measuring.

## We do not promise dates

Features ship when they work. The platform is explicit about what is live versus what is being built, and rounding "building" up to "live" would make the rest of the documentation worthless.

## What we will do

Tell you when something is broken, when a number is stale, and when we do not know. If you catch us doing otherwise, [say so](/platform/feedback.md). That is exactly what the feedback loop is for.


---

# 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://docs.tachyo.ai/under-the-hood/what-we-dont-do.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.
