> For the complete documentation index, see [llms.txt](https://docs.trustlesswork.com/trustless-work/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trustlesswork.com/trustless-work/v1-pt/introducao/developer-resources/arquitetura.md).

# Arquitetura

Instruções passo a passo para ajudar você a conectar seu produto à Trustless Work de forma fluida e eficiente.

## Visão geral

O objetivo deste documento é fornecer um guia abrangente sobre a implementação de melhores práticas dentro da equipe de desenvolvimento. Ele cobre metodologias, ferramentas e estratégias essenciais que podem aumentar a produtividade e garantir resultados de alta qualidade.

### Fluxo Básico

Fluxo mais comum nas dApps.

<figure><img src="https://1629090519-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDg2e2YCRmNlhCnxxmEb6%2Fuploads%2FEqcj3IWrEpEb32mgjVTs%2Fimage.png?alt=media&amp;token=8b73706c-2d39-410d-ba8e-f606b5e523d9" alt=""><figcaption></figcaption></figure>

***

### Serviços - Endpoints

Fluxo que deve ser sempre executado em cada Endpoint **exceto** `Obter Saldo & Obter Escrow`

<figure><img src="https://1629090519-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDg2e2YCRmNlhCnxxmEb6%2Fuploads%2FjuwFylEtQOzPhdIsHO8Z%2Fimage.png?alt=media&amp;token=55d704ae-54e6-47e1-9da2-add91cdd0e8b" alt=""><figcaption></figcaption></figure>

O documento descreve o fluxo de execução essencial para os endpoints de serviço, com exceções para `Obter Saldos` e `Obter Escrow`, garantindo uniformidade na implementação.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.trustlesswork.com/trustless-work/v1-pt/introducao/developer-resources/arquitetura.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.