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

# Overview

User documentation and knowledge base for uLiquid Desk.

Welcome to the uLiquid Desk documentation. This knowledge base explains the core workflows for the dashboard, exchange accounts, manual trading, predictions, bots, grid bots, wallet, funding, vaults, admin operations, and support.

{% hint style="warning" %}
uLiquid Desk is a trading and automation tool. Always review every order, funding action, and bot configuration yourself. This documentation is not financial advice.
{% endhint %}

## Quick Start

1. Create an account or sign in.
2. Check your workspace and role.
3. Connect an exchange account or wallet.
4. Test first in paper or demo mode.
5. Move to small live canaries only after the test flow is clear.

## Main Areas

<table data-view="cards"><thead><tr><th>Area</th><th>What it is for</th></tr></thead><tbody><tr><td><a href="/uliquid-docs/getting-started/quickstart.md">Getting Started</a></td><td>Setup order, login, roles, and security basics.</td></tr><tr><td><a href="/uliquid-docs/user-guide/dashboard-and-accounts.md">Dashboard &#x26; Accounts</a></td><td>Account status, open positions, price alerts, journal, daily metrics, notes, and exchange accounts.</td></tr><tr><td><a href="/uliquid-docs/user-guide/trading-desk-and-risk.md">Trading Desk &#x26; Risk</a></td><td>Manual orders, positions, guardrails, and emergency behavior.</td></tr><tr><td><a href="/uliquid-docs/user-guide/signals-and-automation.md">Signals &#x26; Automation</a></td><td>Predictions, strategies, standard bots, and grid bots.</td></tr><tr><td><a href="/uliquid-docs/user-guide/market-intelligence.md">Market Intelligence &#x26; AI</a></td><td>Source-backed market context, saved analyses, Agent Chat, and Position Copilot boundaries.</td></tr><tr><td><a href="/uliquid-docs/user-guide/wallet-funding-and-vaults.md">Wallet, Funding &#x26; Vaults</a></td><td>Connect wallets, move assets, fund vaults, and run BotVault flows.</td></tr><tr><td><a href="/uliquid-docs/support/troubleshooting-and-faq.md">Support &#x26; FAQ</a></td><td>Common issues, diagnostics, and frequent questions.</td></tr></tbody></table>

## Plans and Feature Access

Feature access depends on your plan, workspace role, and the current environment. See [Plans and Feature Access](/uliquid-docs/plans-and-access/plans-and-feature-access.md) for the current in-product source of truth and safe upgrade guidance.

## Good Operating Habits

* Use paper or canary flows for every new setup.
* Change only one critical setting at a time.
* Keep screenshots, timestamps, workspace names, account labels, and bot or grid IDs for support cases.
* Start live bots only when account data, margin, funding, and permissions are clearly shown as ready.
* Do not grant withdrawal permissions to exchange API keys used by uLiquid Desk.

## GitBook and GitHub

This documentation is prepared for GitBook Git Sync. GitBook uses `docs/README.md` as the homepage, `docs/SUMMARY.md` as the navigation, and `.gitbook.yaml` in the repository root as the sync configuration.

## Engineering and Operations

* [Admin payments overview implementation and acceptance](https://github.com/Mario1480/uLiquid-Desk/tree/main/docs/plans/active/billing/admin-payments-overview.md)
* [Admin payments production deployment evidence](https://github.com/Mario1480/uLiquid-Desk/tree/main/docs/archive/tasks/2026-09-12-admin-payments-production-deploy.md)
* [Beta access applications, invitations and activation gates](https://github.com/Mario1480/uLiquid-Desk/tree/main/docs/auth/beta-access.md)
* [ULIQ Mainnet locking rollout](https://github.com/Mario1480/uLiquid-Desk/tree/main/packages/contracts/ULIQ_MAINNET_LOCKING_ROLLOUT.md)
* [ULIQ Mainnet locker deployment evidence](https://github.com/Mario1480/uLiquid-Desk/tree/main/docs/archive/tasks/2026-09-08-uliq-mainnet-locker-deployment.md)
* [ULIQ Mainnet locking application rollout](https://github.com/Mario1480/uLiquid-Desk/tree/main/docs/archive/tasks/2026-09-08-uliq-mainnet-locking-app-rollout.md)
* [ULIQ locking RPC query adaptation](https://github.com/Mario1480/uLiquid-Desk/tree/main/docs/archive/tasks/2026-09-08-uliq-locking-rpc-chunks.md)
* [ULIQ locking frontend activation](https://github.com/Mario1480/uLiquid-Desk/tree/main/docs/archive/tasks/2026-09-08-uliq-locking-frontend-activation.md)
* [Ein UI integration and acceptance](https://github.com/Mario1480/uLiquid-Desk/tree/main/docs/ui/einui-integration.md)
* [Ein UI route migration inventory](https://github.com/Mario1480/uLiquid-Desk/tree/main/docs/ui/einui-route-inventory.md)
* [Ein UI validation, screenshots and release gates](https://github.com/Mario1480/uLiquid-Desk/tree/main/docs/ui/einui-validation.md)
* [Phase 2 — Shared Data and Existing AI Upgrade — COMPLETE](https://github.com/Mario1480/uLiquid-Desk/tree/main/docs/plans/active/hummingbot-integration/implementation/PHASE_2_IMPLEMENTATION_PLAN.md) — owner acceptance, 2026-09-07
* [Phase 2 owner acceptance record](https://github.com/Mario1480/uLiquid-Desk/tree/main/docs/archive/tasks/2026-09-07-phase2-owner-acceptance.md)
* [Phase 3 — Cross-Market Arbitrage and XEMM Scanners — COMPLETE](https://github.com/Mario1480/uLiquid-Desk/tree/main/docs/plans/active/hummingbot-integration/implementation/PHASE_3_IMPLEMENTATION_PLAN.md) — production acceptance completed 2026-09-09
* [Phase 3 production acceptance record](https://github.com/Mario1480/uLiquid-Desk/tree/main/docs/archive/tasks/2026-09-09-phase3-production-acceptance.md)
* [Phase 4 — Exchange Gateway and isolated Bitget POC — COMPLETE/PARTIAL](https://github.com/Mario1480/uLiquid-Desk/tree/main/docs/plans/active/hummingbot-integration/implementation/PHASE_4_IMPLEMENTATION_PLAN.md) — Decision Gate closed 2026-09-08; Phase 5 remains gated
* [Phase 4 Hummingbot Bitget decision record](https://github.com/Mario1480/uLiquid-Desk/tree/main/docs/archive/tasks/2026-09-08-phase4-hummingbot-bitget-decision.md)
* [Phase 4 private Bitget certification deferral](https://github.com/Mario1480/uLiquid-Desk/tree/main/docs/archive/tasks/2026-09-10-phase4-private-certification-deferred.md) — demo certification deferred; live account excluded from Hummingbot execution tests
* [Phase 5 preparation plan](https://github.com/Mario1480/uLiquid-Desk/tree/main/docs/plans/active/hummingbot-integration/implementation/PHASE_5_PREPARATION_PLAN.md) — architecture and certification preparation complete; implementation remains gated
* [Active and backlog plans](https://github.com/Mario1480/uLiquid-Desk/tree/main/docs/plans/README.md)
* [Active program closeout register](https://github.com/Mario1480/uLiquid-Desk/tree/main/docs/status/active-program-closeout.md)
* [Current status and readiness](https://github.com/Mario1480/uLiquid-Desk/tree/main/docs/status/README.md)
* [Architecture and technical design](https://github.com/Mario1480/uLiquid-Desk/tree/main/docs/architecture/README.md)
* [Runbooks and operations](https://github.com/Mario1480/uLiquid-Desk/tree/main/docs/runbooks/README.md)
* [Quality, security, and acceptance](https://github.com/Mario1480/uLiquid-Desk/tree/main/docs/quality/README.md)
* [Go-live master plan](https://github.com/Mario1480/uLiquid-Desk/tree/main/docs/status/go-live-master-plan.md)
* [Go-live readiness follow-ups](https://github.com/Mario1480/uLiquid-Desk/tree/main/docs/status/go-live-readiness-followups.md)
* [Release evidence matrix](https://github.com/Mario1480/uLiquid-Desk/tree/main/docs/status/release-evidence-matrix.md)
* [Go-live and smoke tests](/uliquid-docs/admin-and-operations/go-live-and-smoke-tests.md)
* [Runtime and deployment reference](/uliquid-docs/reference/runtime-and-deployment.md)
* [Internal documentation index](/uliquid-docs/reference/internal-docs-index.md)

## Archive

Completed dated work records, superseded plans, point-in-time reports, and historical package snapshots live under [`archive`](https://github.com/Mario1480/uLiquid-Desk/tree/main/docs/archive/README.md). Archived evidence is retained for traceability and is not a statement of current runtime, deployment, or go-live status.

* [Trading and dashboard UI fixes, 2026-09-08](https://github.com/Mario1480/uLiquid-Desk/tree/main/docs/archive/tasks/2026-09-08-trading-ui-fixes.md)

Implementation plans remain in their feature area while any rollout, migration, deployment, legal, security, or production gate is open. They move to the archive only after the plan's completion status has been verified and its active conclusions have been transferred to the relevant reference or status document.

## Documentation maintenance policy

* Write repository documentation and READMEs in English.
* Keep active operational truth in the relevant status, runbook, ADR, or reference document.
* Use `docs/archive/tasks/YYYY-MM-DD-*.md` for completed task evidence and the dedicated archive subdirectories for plans, reports, and package snapshots.
* Update inbound links and this index whenever documentation moves.
* Preserve exact commands, identifiers, output, and quoted UI text in historical evidence.
* Treat code/test, deployment/runtime, browser, transaction/finality, indexer, and reconciliation evidence as separate layers.


---

# 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://uliquid-1.gitbook.io/uliquid-docs/getting-started/readme.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.