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

# Choose a reading path

> Start with the question you need to answer, not an internal document number.

You can read this guide as a short introduction, follow one request in detail or jump to a specific reliability question. Each route below stays inside the guide; none requires access to an internal source archive.

## I want to understand the idea

Begin with [Why Gateway exists](/public/gateway/start/why-gateway), then [How Gateway works](/public/gateway/architecture/how-it-works). Finish with [Who owns what](/public/gateway/architecture/responsibilities).

After these pages, you should be able to explain why one shared execution core is useful, where model execution ends and where application responsibility begins.

## I am building an application around Gateway

Read [Your first request](/public/gateway/journeys/first-call), [Planning a compatible request](/public/gateway/supply/planning-a-request) and [Restarting without repeating the work](/public/gateway/journeys/restart-and-replay).

For live output, add [Following a live stream](/public/gateway/journeys/live-stream). For machine-consumed output, read [When the answer must follow a schema](/public/gateway/supply/structured-answers).

These are design explanations, not an invented SDK quickstart. Before implementing an integration, use the exact engineering contract and current interface for your deployment. The [engineering reading map](/public/gateway/reference/engineering-map) explains which topics need that deeper source.

## I need to understand a failure

Start with [When a confirmation is lost](/public/gateway/journeys/lost-confirmation). Then read [Attempts and retries](/public/gateway/reliability/attempts-and-retries) and [The point where an answer cannot be replaced](/public/gateway/reliability/output-boundary).

The key question is not just “which error occurred?” It is “what is known about the original operation, who still owns it and what action is still permitted?”

## I operate or review the system

Read [Ready to serve is more than running](/public/gateway/operations/startup), [Investigating a request](/public/gateway/operations/monitoring) and [Recovery after a storage failure](/public/gateway/operations/restore).

Compare those intended controls with [What has actually been demonstrated](/public/gateway/design/implementation-status). A healthy process, a local test and a production recovery guarantee are different claims.

## I am interested in cost or business work

Use [Usage, provider cost and customer payment](/public/gateway/records/usage-cost-and-payment), [The owners of a payment](/public/gateway/relationships/money-owners) and [A model call inside a larger task](/public/gateway/relationships/business-work).

These pages explain why a successful model answer cannot stand in for accepted work or a settled financial operation.

The [glossary](/public/gateway/reference/glossary) defines terms in plain English. The [FAQ](/public/gateway/reference/faq) answers the questions that most often cross several chapters.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.