> ## Documentation Index
> Fetch the complete documentation index at: https://peak-docs.birdeye.so/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Cross-references & Workflows

> How Peak links related views into research workflows.

Analyzing an Object rarely means looking at one view. A token analysis might start with the description, move to tokenomics, then to ownership, then to live trades — each step prompted by something the analyst just saw.

Peak is designed around this reality. Every Command is connected to the other Commands you might want next, so research moves forward without breaking flow.

## Cross-references

A **cross-reference** is an inline link from one Command to another. Cross-references appear throughout the content area in the format:

```text theme={null}
Command Name (CMD) ↗
```

The arrow signals that clicking the link will navigate to a new Command, typically within the same Object.

### Example

On a Token Description (`TKD`) page, the supply section might reference:

> Total supply: 580.2M SOL. See **Tokenomics (TKE) ↗** for emission schedule and distribution.

Clicking the link opens `SOL TKE` — the Tokenomics view for the same token. The Object stays constant; the Command changes.

### When cross-references appear

Cross-references show up wherever one analytical view naturally leads to another. Common patterns include:

* A summary metric linking to its detailed view (e.g. holder count → Ownership Command)
* A reference to a related Object (e.g. a protocol mentioned on a token page → that protocol's view)
* A methodology note linking to the underlying data view

The goal is to make the next step obvious without forcing the user to search for it.

## Suggested Commands footer

At the bottom of every Command, the **Suggested Commands footer** lists Commands that are contextually relevant to what you are currently viewing.

The footer is curated per Command — the suggestions shown on `TKD` are different from the suggestions shown on `DEP`, because the next logical step is different in each case.

Suggested Commands appear as pills with the Command's full name and its three-letter abbreviation. Clicking opens the suggested Command for the current Object.

## Building research workflows

Cross-references and Suggested Commands turn individual Commands into chained workflows. A typical token research flow might look like:

<Steps>
  <Step title="Start with Token Description (TKD)">
    Get the high-level overview — supply, market data, key attributes.
  </Step>

  <Step title="Move to Tokenomics (TKE)">
    Examine emission schedule, vesting, and distribution.
  </Step>

  <Step title="Open Ownership (OWN)">
    Analyze holder concentration and large-wallet activity.
  </Step>

  <Step title="Check Live Trades (LTD)">
    Monitor real-time trading activity.
  </Step>
</Steps>

Each step is one click from the previous one, either through a cross-reference in the content or through the Suggested Commands footer. The Object remains constant throughout; only the Command changes.

## Workflows across Objects

Cross-references also link between Objects when relevant. For example:

* A Token page might link to the **Network** it runs on.
* A Protocol page might link to the tokens trading on it.
* A Wallet page might link to the protocols it interacts with.

When you click a cross-reference that changes the Object, the new view opens with a sensible default Command. You can then change the Command from the header pill.

## Designing your own workflow

Peak's cross-references are starting points, not constraints. As you develop your own analytical patterns, you will likely move through Commands in sequences that match your specific questions.

A few practical suggestions:

* **Bookmark recurring workflows.** If you run the same sequence of Commands repeatedly, pin the entry point as part of your workspace.
* **Use watchlists for repeated analysis.** A watchlist of tokens or protocols lets you apply the same Command sequence across multiple entities efficiently.
* **Combine with alerts.** When an alert fires, the alert details typically link directly to the relevant Command, putting you one click away from investigation.

## Next steps

<CardGroup cols={2}>
  <Card title="Objects" icon="shapes" href="/docs/core-concepts/objects/overview">
    Browse the full taxonomy of Objects in Peak.
  </Card>

  <Card title="Commands" icon="terminal" href="/docs/core-concepts/commands/overview">
    See the complete catalog of Commands organized by Object.
  </Card>
</CardGroup>