> For the complete documentation index, see [llms.txt](https://docs.baltex.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.baltex.io/whitepaper/2.-design-goals-and-non-goals.md).

# 2. Design Goals and Non‑Goals

### 2.1 Goals

* Reachability: enable swaps across disconnected liquidity islands (isolated DEX tokens → native L1 assets).
* Deterministic lifecycle: stable exchange states and structured progress metadata for partner UX and support.
* Operational resilience: durable queues, retries, rate limiting, and graceful degradation under upstream failures.
* Minimal integration surface: partners call the same quote/create/status methods across flows.
* Privacy‑forward: no mandatory KYC/account flow; private mode provides a relay that breaks direct on‑chain linkage.

### 2.2 Non‑Goals

* Trustless atomic cross‑chain swaps (e.g., HTLC-based) are not assumed.
* Cryptographic proof of best execution is not assumed.
* Censorship resistance guarantees are not assumed.
* Base-layer privacy is not implied unless explicitly using private relay modes.


---

# 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.baltex.io/whitepaper/2.-design-goals-and-non-goals.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.